Advanced Setting

1. Parallel requests

1.1 What are serial/parallel requests

For example, the order of the ad sources in waterfall is A B C D E F. In serial mode, TopOn requests them in sequence. When A is not filled or the request times out, it requests B, and so on, until all ad sources in waterfall are polled. When the number of parallel requests is set to 2, TopOn simultaneously initiates requests to A and B. If neither A nor B is filled or the request times out, it simultaneously initiates requests to C and D, and so on.

TopOn supports two ways to initiate parallel requests. Fixed request number will be initiated according to the specified number, and Parallel request by price will be initiated in parallel strictly according to the price priority. For example, the same waterfall contains 2 ad sources with a price of $9 and 3 ad sources with a price of $7. When the fixed number is 5, TopOn will request all 5 layers of ad sources at the same time; when set to parallel requests with the same price, TopOn will first request 2 $9 ad sources at the same time, and then request 3 $7 ad sources at the same time the next time.

 

1.2 How to set parallel requests

Path: TopOn Dashboard →[Mediation] →[Setting] →Request Type

① The default is a Fixed request number, and the default value is “1”, that is, serial requests.

② The maximum number of parallel requests is 10.

③ In addition, you can select parallel requests at the same price. After selecting this setting, all ad sources at the same price will initiate parallel requests, and you do not need to set the number of parallel requests.

④ The difference between fixed number requests and parallel requests at the same price: For example, the same waterfall flow contains 2 ad sources at a price of $9 and 3 ad sources at a price of $7. When the fixed number is 5, TopOn will request all 5 layers of ad sources at the same time; when set to parallel requests at the same price, TopOn will first request 2 $9 ad sources at the same time, and then request 3 $7 ad sources at the same time the next time.

 

1.3 Suggested usage scenarios

(1) When there are multiple ad sources and a floor price is configured. For example: Admob is configured with ad source A/B, and the floor price is 10USD/5USD respectively; Meta is configured with ad source C/D, and the floor price is also 10USD/5USD respectively. At this time, the ad priority can be sorted as A (10USD) > C (10USD) > B (5USD) > D (5USD), and the parallel request is set to 2. Request AC in parallel, and if there is no fill, request BD in parallel.

(2) When the ad scene impression frequently, that is, the interval between two impressions is short, you can set multiple parallel requests to further improve the impression rate. For example, request A and B at the same time, and both return success. When A is displayed, B can be display immediately.

(3) Parallel requests can improve loading efficiency. When there are many layers of ads (such as more than 15 layers), you can consider setting parallel requests.

 

1.4 Notes

(1) Parallel requests only target request behaviors and do not affect the impression order. For example, if the priorities of two ad sources A and B are 1 and 2 respectively, after setting parallel request 2, requests are sent to A and B at the same time and both successfully return ads. When displaying, TopOn will strictly display them according to the waterfall order, that is, A will be displayed first, and B's ads will be cached.

(2) Parallel requests will occupy more network bandwidth resources; in addition, if too many requests are made but not show, the network may think that the resource utilization is too low and then reduce the code bit weight. Therefore, it is recommended to set the number of parallel requests to 2-3, and no more than 5.

(3) TopOn has implemented caching logic for the ad sources that were not show at the time, which can reduce the chances of being demoted by the network due to frequent requests but not being show. This can be done by using the parallel request function properly.

 

2. Auto Request

2.1 What is auto request

Auto request means automatically requesting the next AD when the previous AD show starts. After the auto request function is turned on, in scenarios where the user stays for a short time, it can avoid missing the AD impression opportunity due to untimely caching. When the user's device network is poor, it can improve the problem of long loading time. This can improve the utilization rate of the overall impression opportunities of the application, shorten the time spent on AD filled, and improve monetization revenue and user experience.

 

2.2 How to enable auto request

Path: [Mediation]→[Setting]→Auto Request

 

2.3 Common ad loading logic

(1) Start ad loading when starting the game;

(2) After each ad is played, the ad is loaded after receiving the close callback (there is no need to determine the isReady state);

(3) Each time the isReady state of the ad is determined to be true, if it is false, the ad is loaded, otherwise it is not executed;

(4) Each time an ad is consumed, the next ad is loaded.

 

2.4 Notes

(1) The auto request function is only available for rewarded videos, interstitial ads, and splash ads.

(2) If the client has already preloaded the next ad after the previous video is played as recommended in the integration document, there is no need to turn this switch on.

(3) It is recommended that the logic for loading the next ad should be handled by the client. This function is mainly used for products that do not preload the ad on the client.

(4) The ads automatically requested to be loaded will not return the AdLoaded callback. The isready interface needs to be used to determine whether the ad has been returned.

 

3. Display frequency control

The mediation page supports two display frequency control functions: placement dimension and ad source dimension.

3.1 Traffic grouping dimension

Path: [Mediation] → [Setting] → Capping/Pacing

This function can limit the display frequency of a single user under the placement dimension. Unlimited by default.

① Capping (Hour): the maximum number of times a single user can view an ad in this placement within an hour;

② Capping (Day): the maximum number of times a single user can view an ad in this placement within a day;

③ Pacing (Sec.): the time interval between the current display of this placement and the next request for this placement by a single user.

 

3.2 Ad source dimension

Path: [Mediation]→Select Ad Source→[Edit]→[More Config]→Capping/Pacing

This function can limit the display frequency of a single user under the ad source dimension. Unlimited by default.

① Capping (Hour): The maximum number of times a single user can view ads from this ad source within an hour;

② Capping (Day): The maximum number of times a single user can view ads from this ad source within a day;

③ Pacing (sec.): The time interval between the current display of this ad source and the next request for this ad source by a single user.

Note: Display frequency control is a local setting. If uninstalled and reinstalled, the limit will be recalculated; the video display interval is the time interval between the start of video playback and the next request.

 

3.3 Application|Network|Ad Format dimension

If you need to set the display cap at the application,network,ad format dimensions, refer to the document: Display & Request Cap Settings.

 

3.4 Common Scenarios

Developers can set display frequency limits based on operational needs. The following are common usage scenarios:

(1) Advertisement stratification

The advertising platform cannot set a floor price for the time being. You can test the effect of ad stratification by setting a display cap or display interval.

(2) Avoiding policy risks

The policies of Facebook and admob are relatively strict. When an application is just launched and the volume is small, it is easy to be affected by individual abnormal devices. FB and admob will consider the traffic abnormal, and the network account will be blocked or the application will be blocked. Once blocked, it will take a long time to appeal or it will be impossible to appeal. Therefore, in order to avoid risks, it is generally recommended to set a display cap for the ad sources of these two platforms when the application is just launched.

The recommended setting value for the display limit is about 10 times. If the average display rate of this placement is high, set it to this average display rate.

(3) Do not want to see the same ad frequently

Sometimes the same device may frequently display the same ad. If the user frequently sees the same ad, the conversion effect may deteriorate. Therefore, the diversity of ad content can be indirectly adjusted by display interval. For example, for two layers of ad sources, platform A and platform B, set the display interval to 60 seconds respectively. This means that after platform A has been show, the ad of platform A will not be requested again within 60 seconds.

 

4. Control the number of ad loads

Note: This function only supports native ad settings.You need to select "Native" in [Placement] first, and then enter the advanced settings. 

Starting from version v5.7.6 (v5.7.06), TopOn SDK supports setting the number of ad requests for ad source dimensions.

If you set the number of ad loads = 2, it will take effect on all ad sources in the native waterfall flow: 1 request, 2 ad creatives returned.

Networks that support returning multiple ads at a time: Tencent Ad, Kuaishou Ad, CSJ, Mintegral

Path: [Mediation] → [Setting]

 

5. Banner Auto Refresh 

Note: You need to select "banner" in [Placement] first, and then enter the advanced settings.

Configuration path: [Mediation]→Select banner placement→[Setting]→Auto refresh

Note: It is recommended to turn off the automatic rotation function of mediation network and control it uniformly by this switch of TopOn.

 

6. AD Format Mixed

6.1 What is AD Format Mixed?

The AD Format Mixed function is a personalized rendering capability provided by TopOn, expanding the scenarios in which the same AD Source can be used in different AD Formats. For example, using the Native AD Source of the Network in the Splash placement of TopOn is recorded as Native mixed Splash.

More detailed instructions are as follows:

① AD Format Mixed Type: Ad Source Type A, mixed with Placement Type B, recorded as A mixed with B;

② Configuration Process: Create the corresponding Ad Source on the Network according to the instructions below, and then configure the Ad Source on the corresponding Placement of TopOn.

 

6.2 AD Format Mixed supported Networks and Configurations

● Native mixed Splash

Used for TopOn Splash placement

 

● Interstitial mixed Splash

For TopOn Splash placement

 

● Native mixed Interstitial

Used for TopOn interstitial ads

 

● Native mixed Banner

For TopOn banner placement

 

● Interstitial mixed Rewarded

For TopOn rewarded placement

AD Format Mixed Type	Network	Support Bidding	Supported TopOn SDK version	Open permissions or not	Type that needs to be created on the advertising platform	Description
Interstitial mixed Rewarded	Pangle，Mintegral	Yes	v6.3.80 and above	No	Pangle：Interstitial  Mintegral：New Interstitial	When using this function, you need to rely on the incentive callback provided by TopOn.

 

● Splash mixed Interstitial 

For TopOn interstitial placement

AD Format Mixed Type	Network	Support Bidding	Supported TopOn SDK version	Open permissions or not	Type that needs to be created on the advertising platform	Description
Splash mixed Interstitial	CSJ,Baidu Union Ads, Kuaishou Ads,Youlianghui,Gromore	Yes	v6.3.65and above:CSJ, Baidu Union Ads, Kuaishou Ads,Youlianghui v6.3.80and above:Gromore	No	Splash

 

● Banner mixed Splash

For TopOn splash placement

AD Format Mixed Type	Network	Support Bidding	Supported TopOn SDK version	Open permissions or not	Type that needs to be created on the advertising platform	Description
Banner mixed Splash	Admob	Yes	v6.2.65 and above	No	Banner

Note: If you have additional style mixing business scenarios, please contact TopOn for business communication