1. Header Bidding
1.1 What is Header Bidding
In-app Header Bidding is a real-time programmatic ad bidding technology that allows all demand parties to bid for the same ad display at the same time. The highest bidder gets the display opportunity, which ensures that publishers can get higher returns for each display.
1.2 The principle of TopOn header bidding
(1) Each time an ad is requested, the header bidding ad source will be queried for a price, and the returned price will be sorted with the price filled in when the regular ad source is created. Ad requests are made according to the sorted waterfall priority.
(2) The biggest difference between header bidding and regular ad sources is that each request will first query a price, rather than being fixed to the price filled in when the regular ad source was created.
Note: The process labels in the following figure represent the corresponding data metrics of the TopOn background mediation. Each label identifies the data corresponding to the above process. You can view the funnel data of the bidding ad source in the mediation by combining the labels.
2.TopOn supported header bidding networks
Currently, TopOn platform has supported in-app header bidding of multiple networks. The specific ad types are as follows:
Network | Ad Type | Bidding Method | Bid Floor | Remarks |
---|---|---|---|---|
Mintegral | Rewarded Video, Interstitial, Native, Banner, Splash | S2S Bidding | Support | - |
Meta | Rewarded Video, Interstitial, Native, Banner | S2S Bidding | Support | - |
Admob | Rewarded Video, Interstitial, Native, Banner, Splash | S2S Bidding | Support | - |
Ironsource | Rewarded Video, Interstitial, Banner | S2S Bidding | Support | TopOn SDK Android v6.5.06/iOS v6.4.88 and above support |
Tencent Advertising (Youlianghui) | Rewarded Video, Interstitial, Native, Banner, Splash | S2S bidding Client-side bidding |
Support | TopOn SDK v6.2.60 and above support client-side bid floor. |
Pangle | Rewarded Video, Interstitial, Native, Banner | S2S Bidding | Support | - |
Vungle | Rewarded Video, Interstitial, Banner, Splash | S2S Bidding | Supported | Please contact Vungle business personnel to enable Header BIdding permissions for Vungle ad placements |
Helium | Rewarded video, Interstitial video | Client-side bidding | Not supported | Helium is Chartboost's header bidding network. If you can't find the Helium entrance under your Chartboost account, please contact Chartboost business personnel to activate it |
Baidu | Rewarded video, Interstitial, native, Splash | Client bidding | Support | TopOn SDK v5.9.60 and above support client bid floor. |
Inmobi | Rewarded video, Interstitial video, Banner, Native | Client bidding | Support | TopOn SDK v6.2.60 and above support client bid floor. |
Mytarget | Rewarded Video, Interstitial Video, Banner, Native | S2S Bidding | Support | - |
Sigmob | Rewarded Video, Interstitial Video, Native, Splash | S2S Bidding Client-side Bidding |
Support | Rewarded video and Interstitial ads: TopOn SDK v5.9.50 and above support Sigmob header bidding; Native and splash ads: TopOn SDK v5.9.95 and above support Sigmob header bidding TopOn SDK v6.2.60 and above support client bid floor. |
Kuaishou | Rewarded Video, Interstitial, Native, Splash | S2S bidding Client-side bidding |
Support | TopOn SDK v5.9.96 and above support Kuaishou client-side real-time bidding (C2S) and server-side real-time bidding (S2S). TopOn SDK v6.2.60 and above support client-side bid floor. |
Yandex | Rewarded Video, Interstitial, Banner, Native | S2S bidding | Supported | TopOn SDK v6.1.20 and above |
Bigo | Rewarded Video, Interstitial, Banner, Native, Splash | S2S bidding | Supported | TopOn SDK v6.1.52 and above |
Verve(PubNative) | Rewarded Video, Interstitial, Banner, Native | Client Bidding | Not supported | TopOn Android SDK v6.1.40, TopOn iOS SDK v6.1.53 and above |
TapTap | Rewarded video, Interstitial, Banner, Splash, native | Client-side bidding | Not supported | TopOn Android SDK v6.2.32 and above support |
Bidmachine | Rewarded video, Interstitial, Banner, native | S2S bidding | Not supported | TopOn SDK Android v6.4.56 and above support |
Xiaomi Columbus | Rewarded video, Interstitial, Banner, native | S2S bidding | Not supported | TopOn SDK Android v6.3.73 and above support |
TaurusX(Webeye) | Rewarded video, Interstitial, Banner, Splash, native | S2S bidding | Supported | TopOn SDK Android v6.4.18 and above support |
Smaato | Rewarded video, Interstitial, Banner, Splash, native | S2S bidding | Not supported | TopOn SDK Android v6.4.50 and above support |
3. How to use header bidding
3.1 Configure header bidding through TopOn background
TopOn already supports the network of header bidding. After creating the header bidding code position ID on the corresponding network, directly configure it in the TopOn ad source and check "header bidding". If the network supports client bidding and server bidding, select the corresponding bidding type.
Path 1: TopOn Backstage → [Mediation] → [Add Ad Source] → Header Bidding
Path 2: TopOn Backstage → [Network] →[Monetization]→ [AD Source Setting ]→ Add Ad Source → Header Bidding
3.2 Configure header bidding through various mediation networks
Please refer to Mediation Network Guide
3.3 View header bidding through TopOn background
You can view the bidding type of the current ad source in the mediation.
4. Header Bidding Bid Floor Filtering Settings
(1) When the bidding price of the network is lower than the bid floor, TopOn will filter the bidding result. At this time, no request will be made to the bidding ad source.
For example: Set the bid floor to 10. When the bidding ad source A returns a price query result of 9, no ad request will be made to A
(2) If the bid floor is set in both the segment and the ad source, the bid floor of the ad source will be used first.
(3) Setting the bid floor will reduce the fill and revenue of the bidding ad source, please set it with caution (the minimum bid floor is RMB ¥ 0.1 and USD $ 0.01)
(4) Setting path:
① Setting the bid floor of the ad source:TopOn Backstage → [Mediation] → [Add/Edit Ad Source] → Modify the bid floor
② Segment bid floor setting path: TopOn background → [Mediation] → [Setting] → Modify bid floor
5. How to configure TopOn SDK
Note: The header bidding function only needs to complete the import of TopOn SDK and the corresponding Network SDK, and no code modification is required.
(1) How to obtain TopOn SDK and Network SDK
① When using the Header Bidding function, it is recommended to use the latest version of TopOn and the supported Header Bidding Network SDK.
② TopOn SDK and Network SDK can be downloaded from TopOn developer backend
6. How to view header bidding related data in the report
You can choose one of the following paths
(1) Mediation path:
[Mediation] →Custom Metrics→Check “Bid Request”, “Bid Response Rate”, “Bid Fill eCPM”
Or select the “bidding data” metric template
(2) Full report path:
① Bidding Type = Header Bidding
② Report → Full Report → Custom Metrics → Check “Bid Request”, “Bid Response Rate”, “Bid Fill eCPM”
7. FAQ
(1) Why the number of Bidding requests is less than the number of layered requests
Please refer to the header bidding principle of TopOn (see the figure below). Generally speaking, after initiating a request, TopOn SDK will initiate a price bid request to the header bidding ad source.
Among them, the number of [Bid Request] of the header bidding ad source is close to the number of [Ad Requests] of the header layering.
Remarks:
The reason why the number of Vungle Bidding Bid Request and the number of header layer requests are so different is that Vungle Bidding will cache the ads for half an hour after a query. It will not send out another query until the ads are displayed or there is no cache for half an hour.
(2) Why is the eCPM so high but the exposure is so low/the eCPM is so low?
First, distinguish the following metrics:
① Bid Fill eCPM: The average eCPM returned by the network when the header bidding ad source responds to the bid request. For example, if the platform returns an eCPM of 1000 and an eCPM of 1, the bid request response eCPM=500.5.
② eCPM API: TopOn calculates the eCPM API by obtaining the actual revenue and display API from the network through the report API. The calculation formula is: (revenue/display API)*1000.
③ eCPM: TopOn calculates eCPM based on the actual revenue obtained from the network through the report API and the display statistics of TopOn. The calculation formula is: (revenue/display statistics of TopOn)*1000. It can be understood as the eCPM of the advertisement that has been exposed.
Description:
① TopOn will only display the header bidding advertisement when the eCPM returned by the header bidding advertisement source is at the highest position in the waterfall flow. For example, if the header bidding advertisement source returns an advertisement with an eCPM of 200 and is at the highest position in the waterfall flow, TopOn will display the advertisement with an eCPM of 200. At this time, the bid request response eCPM is 200, and eCPM=200.
② When the header bidding advertisement source returns an advertisement with an eCPM of 200 and an advertisement with a price of 10, and the advertisement with an eCPM of 200 is at the highest position in the waterfall flow, TopOn will display the advertisement with a price of 200. However, since the ad with a price of 10 is not competitive, the ad with a price of 10 is not displayed. At this time, the bid request response eCPM is 105, and eCPM=200 (because only the eCPM of the displayed ad is calculated).
Summary:
When checking the eCPM of Bidding, the bid request eCPM is more valuable for reference. The bid request eCPM can be used to understand the price ranking position of the header bidding ad source in the waterfall flow.
(3) Why is the number of Bid Request less after adding A Bidding placement than B Bidding placement?
For example:After adding the bidding of Youlianghui, it is found that the number of Bid Request of Youlianghui is only 180,000, while the number of Bid Request of Baidu is 500,000.
Explanation:Generally speaking, when entering the client, the previously cached strategy will be requested first. Therefore, it is possible that after a period of time after configuring Bidding, the requested strategy is a strategy that has not yet been configured for Bidding. It is recommended to observe whether the number of Bid Request is normal two to three days after configuring Bidding.
(4) Why is the bidding winning rate of a certain platform so high, and the display rate of the ad source so low?
① Assume that the configured bidding is platform A, and the same applies to other aggregation platforms or multiple bidding platforms.
② First, refer to the bidding logic of TopOn and refer to the following figure.
③ The bidding logic of TopOn is this: waterfall starts requesting and inquiring about bidding at the same time.
④ Assuming that the price returned by bidding is 20 at this time, it will participate in the sorting in the waterfall.
- At this time, TopOn SDK starts to request from the top layer of the waterfall head downwards. For example, if the top layer of the waterfall is 25, then if the top layer 25 is returned, then TopOn will request the ad source of 25. At this time, the bidding platform is considered to have lost the competition.
- If the previous waterfall has not returned, and the bidding of platform A with a price of 20 is requested, we will initiate a request for the bidding of platform A and request the 20 ad of platform A. However, if the price of platform A is 16, the previous high-priced ad 25 is returned, such as the ad of 25 yuan, or any ad higher than 16 yuan in the waterfall.
⑤ At this time, platform A is considered to have won the competition, but TopOn SDK will choose to display the higher-priced ad of 25 yuan in the cache.
Brief summary:
In fact, it is best to compare the display rate with the ad sources in the regular waterfall flow with the same platform price close to the bid request eCPM (that is, approximately equal to the bid request eCPM). For example, the bid request eCPM of Bidding on platform A is 20, and the display rate is 20%. If the display rate of the 20th layer of the regular waterfall flow on platform A is also 20%. Then, it can be considered that the display rate is reasonable. (Note that this should not be compared with the display rate of platform B or platform C, and it is also recommended not to compare with ad sources with too much difference in price)
Note:
TopOn will optimize the statistical caliber in version v5.9.71 and above, and will send a winning notification only when the request is actually initiated in the future, which is expected to increase the display rate of the Bidding platform after the winning.