cold start strategy

Ad request time has a great impact on the exposure of open-screen ads, especially in application cold start scenarios. To this end, TopOn SDK has been optimized for cold start and supports configuring independent ad request strategies for cold start scenarios to further improve ad exposure effects.

Term explanation: Cold start: refers to the scenario where the APP restarts the APP from a completely closed state. Generally, when the APP has never been started, or the APP stays in the background for too long and is recycled by the system, or the APP is actively killed by the user, the APP will be considered to be completely closed. The difference between cold start and warm start: cold start requires creating and initializing the application, and then loading the page; hot start means returning to the desktop or switching to other programs when the application has been opened, but the return key, home key, etc. are pressed. When the time comes, reopen the APP scene. Hot start does not require creating and initializing the application, and the page can be loaded directly.

This document describes how to configure the cold start traffic grouping of TopOn SDK to optimize the exposure effect of cold start open screen ads.

1. Introduction

TopOn supports developers to add cold start request rule as the cold start policy under this ad. When the application is cold-started, TopOn will read cold-start policy to request ads to improve cold-start ad impression rate.

If the APP needs to support cold start strategy< /span>, no additional code development is required, just update TopOn SDK v6.1.78 and above

2. Create traffic grouping for cold start policy

To use the cold start policy, you need to add cold start rules under traffic grouping. The specific process is as follows:

1. In Aggregation management page, add traffic grouping rules, select Cold start request
2. Cold start request rules in the traffic group can be compared with other Rules are used at the same time, but it also means that in a cold start scenario, other set rules need to be met at the same time for the policy to take effect.

3. FAQ

1. What are the connections and differences between the cold start strategy and the SDK pre-made strategy?

answer：

What they have in common: Cold start strategies and SDK pre-made strategies both use client-side pre-set strategies to reduce network request time, and support the configuration of independent advertising Waterfall request strategies to optimize the efficiency of screen opening scenarios.

Differences: SDK preset strategies are exported from the TopOn backend and preset to the application when TopOn SDK is integrated. The SDK preset strategies are released with the application and are only used when the application is launched for the first time after installation or update. Online advertising spaces are obtained from TopOn SDK. Once the strategy is successful it will no longer be used. The cold start strategy is obtained online and is used during a cold start after the application is installed but not when it is opened for the first time.

For a more intuitive explanation, please refer to the schematic diagram:

​

1. How to improve the loading efficiency of open-screen ads?
2. ​

• v6.1.78 and above, you can refer to the following optimization suggestions:
• ​

1. For the first opening scenario after installation, set the SDK preset policy and import it during version integration. For specific settings and usage instructions of preset policies, please refer to SDK pre-made policy documentation
2. For cold start scenarios that are not opened for the first time, set a cold start strategy. It is recommended to reduce the number of Waterfall high-price tiers and open it. TopOn ADX In order to speed up the speed of opening the screen to get ads, you can also consider increasing the number of parallel requests.