Who is this guide for?
This guide is for developers and system administrators who want to understand A2’s technical architecture. It explains how A2 serves ads and processes data.System overview
The A2 platform is designed around core components for reliable ad operations and data processing.Unified Auction
A2’s key differentiator is its Unified Auction approach. Instead of the traditional waterfall, all ad sources compete simultaneously in a single RTB auction.Problems with the waterfall approach
- Sequential calls: Ad sources are called one by one in priority order
- Missed opportunities: Lower-priority sources that could bid higher miss out
- Inefficient revenue: The first ad to respond wins, not the highest bid
Benefits of Unified Auction
- Simultaneous competition: Direct Sales, Ad Networks, and DSPs bid at the same time
- Yield optimization: Real-time highest-bid wins raise eCPM
- Header Bidding support: Maximizes ad revenue using the industry-standard approach
Core components
A2 Manager (management console)
A2 Manager is a web-based management tool that handles all settings for your ad business. Retailers, advertisers, and admins use it to configure and manage ads.
Key features:
- Create and manage campaigns
- Configure and manage placements
- Upload and approve creatives
- Request and approve allocations
- View and analyze performance data
- Manage user accounts and permissions
A2 Edge (ad serving engine)
A2 Edge is a high-performance engine that finds and returns the best ad for a user’s request within 0.01 seconds (10ms).
Key features:
- Receive and process ad requests
- Select ads that match targeting conditions
- Run bidding logic (CPM, CPC, CPA)
- Return ad responses
- Collect impression/click events
A2 Datahub (data pipeline)
A2 Datahub is the system that collects and processes every event that occurs, such as ad impressions, clicks, and conversions.
Key features:
- Collect ad event logs (impressions, clicks, conversions)
- Collect user behavior logs (purchases, searches, cart, etc.)
- Cleanse and store data
- Prepare data for analysis
- Detect and filter click fraud
Data flow
Ad serving flow
- A user visits the retailer’s service.
- The SDK or API installed on the page requests an ad from Edge.
- Edge selects the best ad based on placement information, user information, and active campaigns.
- Edge returns the selected ad information (image URL, click URL, etc.).
- The ad is displayed on the user’s screen.
- The impression event is sent to Datahub and recorded.
Configuration data flow
- Admins, retailers, and advertisers configure campaigns, placements, and allocations in Admin.
- The configured data is saved to the database.
- Edge servers sync the latest settings.
- Ad serving starts with the new settings applied.
Integration methods
There are two ways to integrate a retailer’s service with A2.- Web SDK
- Direct API calls
Web SDK integration
This is the simplest integration method. After creating a placement, insert the provided script tag into your web page. The SDK automatically handles ad requests, impression tracking, and click tracking.- Easy installation
- Automatic event tracking
- Responsive support
