{"data":{"id":"844706","string_id":"cMIhuDNP","status":"1","parent_id":"76196","slug":"cMIhuDNP","order":"0","name":"Advanced Features","type":"1","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","author":"Welch","published_time":"0","add_time":"1782799876","update_time":"1782884289","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"1","tags":[],"parent_name":"SDK Access Guide","parent_type":"1","parent_slug":"cUkkAX","child":[{"id":"844712","string_id":"zUl0fvpD","status":"1","parent_id":"844706","slug":"zUl0fvpD","order":"5","name":"Ad Scenario","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1782884289","add_time":"1782799894","update_time":"1782884289","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"844712","content":"On the **App - Ad Scene** page, you can create and edit ad scenes. Before creating an ad scene, you must first create an app and at least one Ad Placement.\n\nOn the Ad Scene page, you can:\n\n- Add ad scenes\n- View ad scene data\n\n**1.** Ad Scene Introduction\n---------\n\n**(1) View SDK loading and impression ad conversion data to improve revenue**\n\nBy using the ad scene feature, you can view the data of each ad loading and impression flow in the SDK on the [Funnel Analysis Report](https:\/\/help.takuad.com\/docs\/qlHqYM), determine whether ad settings are reasonable, analyze optimization opportunities for each flow conversion, and improve conversion to boost revenue.\n\n**(2) Reduce Ad Placement configuration costs**\n\nDevelopers usually use different Ad Placements to distinguish data for different ad scenarios. This effectively differentiates impression and revenue data under each scenario, but also increases operational costs (needing to maintain Ad Source configurations for multiple Ad Placements).\n\nThe Taku platform supports creating multiple ad scenes under a single Ad Placement, effectively differentiating impression and click data under different ad scenarios, reducing the cost of configuring Ad Placements.\n\n**2.** Ad Scene Integration Process\n-------------\n\n**(1) When the current Ad Placement corresponds to only one ad scene:**\n\nAfter adding the ad scene arrival code, Taku will provide the following core metrics in the [Comprehensive Report](https:\/\/help.takuad.com\/docs\/DVM3Tf) and [Funnel Analysis Report](https:\/\/help.takuad.com\/docs\/qlHqYM), offering more complete analysis data for your ad monetization:\n\nWhen the SDK reaches the ad scene, call Taku SDK's `entryAdScenario()` method. You may skip passing the ad scene ID, and the data will be classified under the default ad scene.\n\n**(2) When the current Ad Placement corresponds to multiple ad scenes** and you need to differentiate impression and click data across different ad scenes:\n\n1. Create ad scenes in the Taku backend and optionally customize the ad scene ID.\n2. Accurately add the ad scene arrival code in the app (call Taku SDK's `entryAdScenario()` method and pass the respective ad scene IDs).\n3. Pass the scenarioId in the `show` method when displaying the ad.\n\n**3.** Timing for Calling Ad Scene Arrival\n--------------\n\nBased on different ad types and your app's ad logic, you can call Taku SDK to add the ad scene arrival code within the app.\n\n### 3.1 Rewarded Video\n\nRefer to the following examples for calling the ad scene arrival method:\n\n| App Type | Ad Name | Ad Flow | Timing of Ad Scene Arrival Call |\n|---|---|---|---|\n| Game | Rewarded Video Claim Reward | Enter Game -> Click Stamina\/Currency entry -> Pop up \"Watch Ad to Get Reward\" popup -> Click button to watch Rewarded Video | Pop up \"Watch Ad to Get Reward\" popup |\n| App | Watch Video to Clean Junk | Enter App -> Enter Clean Junk feature -> Scan junk -> Click Clean Now -> Pop up \"Watch Ad to Clean Junk\" popup -> Click button to watch Rewarded Video | Pop up \"Watch Ad to Clean Junk\" popup |\n\n\n\nGame Rewarded Video Claim Reward:\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec1d0e8b.png)\n\nApp Watch Video to Clean Junk:\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec1a2c02.png)\n\n### 3.2 Interstitial (Full Screen \/ Half Screen)\n\nRefer to the following examples for calling the ad scene arrival method:\n\n| App Type | Ad Name | Ad Flow | Timing of Ad Scene Arrival Call |\n|---|---|---|---|\n| Game | Level Complete Interstitial | Enter Game -> Enter Level -> Level Complete popup -> Click Next Level \/ Return to Level page button -> Interstitial appears -> Enter next level \/ Level page | Level Complete popup |\n| App | Cleanup End Interstitial | Enter App -> Enter Clean Junk feature -> Scan junk -> Click Clean Now -> Cleaning animation -> Full screen Interstitial appears -> Cleanup result page | Cleaning animation |\n| App | Page Switch Interstitial | Enter App -> Homepage -> Click other features on homepage tab -> Arrive at other feature page -> Interstitial popup appears | Arrive at other feature page |\n\n\n\nApp Page Switch Interstitial:\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec1aedc7.png)\n\n### 3.3 Native \/ Feed\n\nRefer to the following examples for calling the ad scene arrival method:\n\n| App Type | Ad Name | Ad Flow | Timing of Ad Scene Arrival Call |\n|---|---|---|---|\n| Game\/App | Check-In Popup Native Ad | Enter Game\/App -> Check-in popup appears -> Display Native Ad below check-in popup | Check-in popup appears |\n| App | Page Native Ad | Enter App -> Enter feature page \/ long list page -> Native Ad embedded in page | Enter feature page \/ long list page |\n\n\n\n### 3.4 Banner\n\nRefer to the following examples for calling the ad scene arrival method:\n\n| App Type | Ad Name | Ad Flow | Timing of Ad Scene Arrival Call |\n|---|---|---|---|\n| Game\/App | Banner Below Popup | Enter Game\/App -> Message popup \/ Feature popup appears -> Display Banner below popup | Message popup \/ Feature popup appears |\n| Game\/App | Fixed Banner | Enter Game\/App -> Enter level page \/ novel reading page etc. -> Display fixed Banner at bottom of page | Enter level page \/ novel reading page etc. |\n\n\n\nBanner ads support both preloaded and non-preloaded modes, and the ad scene can be called on the above pages. If Banner auto-refreshes, the ad scene arrival data will be less than the impression data.\n\n### 3.5 Splash\n\nRefer to the following examples for calling the ad scene arrival method:\n\n| App Type | Ad Name | Ad Flow | Timing of Ad Scene Arrival Call |\n|---|---|---|---|\n| Game\/App | Splash Ad | Enter Game\/App -> Display company logo page -> Display Splash Ad | Display company logo page; if there is no logo page and the app launches directly, you can call the ad scene upon entering the Game\/App, or skip calling the ad scene |\n\n\n\n**4.** Creating Ad Scenes and Obtaining Ad Scene IDs\n------------------\n\nIf you need to use multiple ad scenes to differentiate data, you can create ad scenes in the backend and obtain the ad scene IDs.\n\n(1) App -> Select the corresponding app -> View Ad Placement list -> Scene Management\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec19af4b.png)\n\n(2) Click Add Ad Scene\n\n1. Each Ad Placement has a Default scene. The default ad scene ID is \"\", and when calling the ad scene arrival method without passing an ad scene ID, the data will be classified under the default scene.\n2. You can customize the ad scene ID (supported by Taku SDK v6.2.48 and above), making it easier for developers to differentiate ad scenes during integration; if no ad scene ID is filled in, one will be auto-generated.\n3. For Rewarded Video ads, you can add reward information (reward name and reward amount) in the ad scene. The reward information will be called back to the developer. For details, refer to iOS - Callback Information and Android - Callback Information.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec1dcb80.png)\n\n(3) View the scene list and obtain the ad scene ID to provide to the development team for integration.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec197b36.png)\n\n**5.** Ad Scene Integration Code Samples\n--------------\n\n### 5.1 Taku Android SDK Code Samples\n\n| Ad Type | Sample Code |\n|---|---|\n| Rewarded Video | [View](\/docs\/i0WOv2) |\n| Interstitial | [View](\/docs\/Yn1nat) |\n| Splash | [View](\/docs\/j4SZ6n) |\n| Native | [View](\/docs\/oct5Mn) |\n| Banner | [View](\/docs\/fygHI5) |\n\n\n\n### 5.2 Taku iOS SDK Code Samples\n\n| Ad Type | Sample Code |\n|---|---|\n| Rewarded Video | [View](\/docs\/DUxiCT#4._%E5%B9%BF%E5%91%8A%E5%9C%BA%E6%99%AF%E7%BB%9F%E8%AE%A1) |\n| Interstitial | [View](\/docs\/K6lur5#4._%E5%B9%BF%E5%91%8A%E5%9C%BA%E6%99%AF%E7%BB%9F%E8%AE%A1) |\n| Splash | [View](\/docs\/uGZEUP#4._%E5%B9%BF%E5%91%8A%E5%9C%BA%E6%99%AF%E7%BB%9F%E8%AE%A1) |\n| Native | [View](\/docs\/JDKIwh#4._%E5%B9%BF%E5%91%8A%E5%9C%BA%E6%99%AF%E7%BB%9F%E8%AE%A1) |\n| Banner | [View](\/docs\/eoMVXS#4._%E5%B9%BF%E5%91%8A%E5%9C%BA%E6%99%AF%E7%BB%9F%E8%AE%A1) |\n\n\n\n### 5.3 Notes\n\n**(1) If the passed ad scene ID is incorrect or does not belong to the current Ad Placement, Taku will count that data under the Default scene.**\n\n**(2) If no ad scene ID is passed in the `entryAdScenario()` or `Show()` methods, Taku will count that data under the Default scene.**\n\n**(3) If a paused ad scene ID is passed in the `entryAdScenario()` or `Show()` methods, Taku will count that data under the Default scene.**\n\n(4) Taku SDK version support for ad scenes by ad type:\n\n| Taku SDK Version | Ad Types Supporting Ad Scenes |\n|---|---|\n| >=5.4.7 | **Rewarded Video**, **Interstitial** |\n| >=5.7.9 (5.7.09) | **Rewarded Video**, **Interstitial**, **Native**, **Banner**, **Splash** |\n\n\n\n**Taku backend custom ad scene ID supported version: >= v6.2.48**\n\n**6.** Viewing Ad Scene Data\n-----------\n\n### 6.1 Ad Scene Data Reports\n\nYou can view data for each ad scene of a specific Ad Placement in [Ad Scene](https:\/\/help.takuad.com\/docs\/1RWLAv) and [Reports](https:\/\/help.takuad.com\/docs\/DVM3Tf).\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec18dd69.png)\n\n### 6.2 Funnel Analysis Report\n\nYou can view the app's funnel analysis data in the [Funnel Analysis Report](https:\/\/help.takuad.com\/docs\/qlHqYM).\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/zFZfea\/66e16ec1b8937.png)","pure_content":"On the App - Ad Scene page, you can create and edit ad scenes. Before creating an ad scene, you must first create an app and at least one Ad Placement.\nOn the Ad Scene page, you can:\n\nAdd ad scenes\nView ad scene data\n\n1. Ad Scene Introduction\n(1) View SDK loading and impression ad conversion data to improve revenue\nBy using the ad scene feature, you can view the data of each ad loading and impression flow in the SDK on the Funnel Analysis Report, determine whether ad settings are reasonable, analyze optimization opportunities for each flow conversion, and improve conversion to boost revenue.\n(2) Reduce Ad Placement configuration costs\nDevelopers usually use different Ad Placements to distinguish data for different ad scenarios. This effectively differentiates impression and revenue data under each scenario, but also increases operational costs (needing to maintain Ad Source configurations for multiple Ad Placements).\nThe Taku platform supports creating multiple ad scenes under a single Ad Placement, effectively differentiating impression and click data under different ad scenarios, reducing the cost of configuring Ad Placements.\n2. Ad Scene Integration Process\n(1) When the current Ad Placement corresponds to only one ad scene:\nAfter adding the ad scene arrival code, Taku will provide the following core metrics in the Comprehensive Report and Funnel Analysis Report, offering more complete analysis data for your ad monetization:\nWhen the SDK reaches the ad scene, call Taku SDK's entryAdScenario() method. You may skip passing the ad scene ID, and the data will be classified under the default ad scene.\n(2) When the current Ad Placement corresponds to multiple ad scenes and you need to differentiate impression and click data across different ad scenes:\n\nCreate ad scenes in the Taku backend and optionally customize the ad scene ID.\nAccurately add the ad scene arrival code in the app (call Taku SDK's entryAdScenario() method and pass the respective ad scene IDs).\nPass the scenarioId in the show method when displaying the ad.\n\n3. Timing for Calling Ad Scene Arrival\nBased on different ad types and your app's ad logic, you can call Taku SDK to add the ad scene arrival code within the app.\n3.1 Rewarded Video\nRefer to the following examples for calling the ad scene arrival method:\n\n\n\n App Type\n Ad Name\n Ad Flow\n Timing of Ad Scene Arrival Call\n\n\n\n\n Game\n Rewarded Video Claim Reward\n Enter Game -> Click Stamina\/Currency entry -> Pop up \"Watch Ad to Get Reward\" popup -> Click button to watch Rewarded Video\n Pop up \"Watch Ad to Get Reward\" popup\n\n\n App\n Watch Video to Clean Junk\n Enter App -> Enter Clean Junk feature -> Scan junk -> Click Clean Now -> Pop up \"Watch Ad to Clean Junk\" popup -> Click button to watch Rewarded Video\n Pop up \"Watch Ad to Clean Junk\" popup\n\n\n\nGame Rewarded Video Claim Reward:\n\nApp Watch Video to Clean Junk:\n\n3.2 Interstitial (Full Screen \/ Half Screen)\nRefer to the following examples for calling the ad scene arrival method:\n\n\n\n App Type\n Ad Name\n Ad Flow\n Timing of Ad Scene Arrival Call\n\n\n\n\n Game\n Level Complete Interstitial\n Enter Game -> Enter Level -> Level Complete popup -> Click Next Level \/ Return to Level page button -> Interstitial appears -> Enter next level \/ Level page\n Level Complete popup\n\n\n App\n Cleanup End Interstitial\n Enter App -> Enter Clean Junk feature -> Scan junk -> Click Clean Now -> Cleaning animation -> Full screen Interstitial appears -> Cleanup result page\n Cleaning animation\n\n\n App\n Page Switch Interstitial\n Enter App -> Homepage -> Click other features on homepage tab -> Arrive at other feature page -> Interstitial popup appears\n Arrive at other feature page\n\n\n\nApp Page Switch Interstitial:\n\n3.3 Native \/ Feed\nRefer to the following examples for calling the ad scene arrival method:\n\n\n\n App Type\n Ad Name\n Ad Flow\n Timing of Ad Scene Arrival Call\n\n\n\n\n Game\/App\n Check-In Popup Native Ad\n Enter Game\/App -> Check-in popup appears -> Display Native Ad below check-in popup\n Check-in popup appears\n\n\n App\n Page Native Ad\n Enter App -> Enter feature page \/ long list page -> Native Ad embedded in page\n Enter feature page \/ long list page\n\n\n\n3.4 Banner\nRefer to the following examples for calling the ad scene arrival method:\n\n\n\n App Type\n Ad Name\n Ad Flow\n Timing of Ad Scene Arrival Call\n\n\n\n\n Game\/App\n Banner Below Popup\n Enter Game\/App -> Message popup \/ Feature popup appears -> Display Banner below popup\n Message popup \/ Feature popup appears\n\n\n Game\/App\n Fixed Banner\n Enter Game\/App -> Enter level page \/ novel reading page etc. -> Display fixed Banner at bottom of page\n Enter level page \/ novel reading page etc.\n\n\n\nBanner ads support both preloaded and non-preloaded modes, and the ad scene can be called on the above pages. If Banner auto-refreshes, the ad scene arrival data will be less than the impression data.\n3.5 Splash\nRefer to the following examples for calling the ad scene arrival method:\n\n\n\n App Type\n Ad Name\n Ad Flow\n Timing of Ad Scene Arrival Call\n\n\n\n\n Game\/App\n Splash Ad\n Enter Game\/App -> Display company logo page -> Display Splash Ad\n Display company logo page; if there is no logo page and the app launches directly, you can call the ad scene upon entering the Game\/App, or skip calling the ad scene\n\n\n\n4. Creating Ad Scenes and Obtaining Ad Scene IDs\nIf you need to use multiple ad scenes to differentiate data, you can create ad scenes in the backend and obtain the ad scene IDs.\n(1) App -> Select the corresponding app -> View Ad Placement list -> Scene Management\n\n(2) Click Add Ad Scene\n\nEach Ad Placement has a Default scene. The default ad scene ID is \"\", and when calling the ad scene arrival method without passing an ad scene ID, the data will be classified under the default scene.\nYou can customize the ad scene ID (supported by Taku SDK v6.2.48 and above), making it easier for developers to differentiate ad scenes during integration; if no ad scene ID is filled in, one will be auto-generated.\nFor Rewarded Video ads, you can add reward information (reward name and reward amount) in the ad scene. The reward information will be called back to the developer. For details, refer to iOS - Callback Information and Android - Callback Information.\n\n\n(3) View the scene list and obtain the ad scene ID to provide to the development team for integration.\n\n5. Ad Scene Integration Code Samples\n5.1 Taku Android SDK Code Samples\n\n\n\n Ad Type\n Sample Code\n\n\n\n\n Rewarded Video\n View\n\n\n Interstitial\n View\n\n\n Splash\n View\n\n\n Native\n View\n\n\n Banner\n View\n\n\n\n5.2 Taku iOS SDK Code Samples\n\n\n\n Ad Type\n Sample Code\n\n\n\n\n Rewarded Video\n View\n\n\n Interstitial\n View\n\n\n Splash\n View\n\n\n Native\n View\n\n\n Banner\n View\n\n\n\n5.3 Notes\n(1) If the passed ad scene ID is incorrect or does not belong to the current Ad Placement, Taku will count that data under the Default scene.\n(2) If no ad scene ID is passed in the entryAdScenario() or Show() methods, Taku will count that data under the Default scene.\n(3) If a paused ad scene ID is passed in the entryAdScenario() or Show() methods, Taku will count that data under the Default scene.\n(4) Taku SDK version support for ad scenes by ad type:\n\n\n\n Taku SDK Version\n Ad Types Supporting Ad Scenes\n\n\n\n\n >=5.4.7\n Rewarded Video, Interstitial\n\n\n >=5.7.9 (5.7.09)\n Rewarded Video, Interstitial, Native, Banner, Splash\n\n\n\nTaku backend custom ad scene ID supported version: >= v6.2.48\n6. Viewing Ad Scene Data\n6.1 Ad Scene Data Reports\nYou can view data for each ad scene of a specific Ad Placement in Ad Scene and Reports.\n\n6.2 Funnel Analysis Report\nYou can view the app's funnel analysis data in the Funnel Analysis Report.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1782799894","update_time":"1782884289"},"pure_content":"On the App - Ad Scene page, you can create and edit ad scenes. Before creating an ad scene, you must first create an app and at least one Ad Placement.\nOn the Ad Scene page, you can:\n\nAdd ad scenes\nVi"},{"id":"844708","string_id":"OPEtKSdg","status":"1","parent_id":"844706","slug":"OPEtKSdg","order":"4","name":"Cold Start Strategy","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1782884289","add_time":"1782799888","update_time":"1782884289","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"844708","content":"Ad request latency significantly impacts Splash Ad impression performance, especially in cold start scenarios. To address this, Taku SDK optimizes for cold start and supports configuring independent ad request strategies for cold start scenarios, further improving ad impression results.\n\n> **Glossary:** Cold Start: Refers to the scenario where an app is restarted from a fully closed state. An app is generally considered to be in a fully closed state when it has never been launched, has been in the background for too long and reclaimed by the system, or has been actively killed by the user. Difference between cold start and hot start: Cold start requires creating and initializing the app, then loading the page; hot start refers to the scenario where the app is already open but was sent to the background by pressing the Back key, Home key, etc., or the app was switched away from, and is then reopened. Hot start does not require creating and initializing the app, and the page loads directly.\n\nThis document describes how to configure Taku SDK's cold start traffic group to optimize cold start Splash Ad impression results.\n\n**1.** Introduction\n-----\n\nTaku supports developers adding **Cold Start Request** rules when setting up traffic groups, serving as that placement's **Cold Start Strategy**. When the app is in a cold start state, Taku reads the **Cold Start Strategy** to request ads, improving the ad display rate during cold start.\n\nIf an app needs to support **Cold Start Strategy**, no additional code development is required; simply update to Taku SDK v6.1.78 or above.\n\n**2.** Creating a Traffic Group for Cold Start Strategy\n---------------\n\nTo use the Cold Start Strategy, you need to add cold start rules under a traffic group. The specific process is as follows:\n\n(1) On the **Mediation Management** page, add or edit a traffic group, add a new traffic group rule, and select **Cold Start Request**\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/BeYyMI\/66e2977af0ed4.png)\n\n(2) The **Cold Start Request** rule in a traffic group can be used simultaneously with other rules, but this also means that in cold start scenarios, all other set rules must also be satisfied for the strategy to take effect.\n\n**3.** FAQ\n---------\n\n**(1) What is the relationship and difference between Cold Start Strategy and SDK Preset Strategy?**\n\n**Answer:**\n\n**1 Similarities: Both Cold Start Strategy and SDK Preset Strategy preload strategies on the client side to reduce network request latency and support configuring independent ad Waterfall request strategies to optimize Splash scenario efficiency.**\n\n**2 Differences: SDK Preset Strategy is exported from the Taku backend and preloaded into the app when integrating Taku SDK. The SDK Preset Strategy is released with the app and is only used during the first launch after install or update. Once Taku SDK successfully fetches the online ad placement strategy, it will no longer be used. Cold Start Strategy is fetched online and is used during cold starts when the app is not being launched for the first time after installation.**\n\nA more intuitive explanation can be found in the diagram below:\n\n![Article Image](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/BeYyMI\/66e2977b0e4b8.png)\n\n**(2) How to improve Splash Ad loading efficiency?**\n\nFor v6.1.78 and above, refer to the following optimization suggestions:\n\n1. For the first launch after install scenario, set up **SDK Preset Strategy** and import it during app version integration. For specific settings and usage instructions of the preset strategy, refer to [SDK Preset Strategy Documentation](https:\/\/help.takuad.com\/docs\/wERYJv).\n\n2. For cold start scenarios that are not the first launch, set up **Cold Start Strategy**. It is recommended to reduce the number of high-price Waterfall tiers, enable [**Taku ADX**](https:\/\/help.takuad.com\/docs\/0a2ZxO) to speed up the Splash Ad retrieval, and consider increasing the number of concurrent requests.","pure_content":"Ad request latency significantly impacts Splash Ad impression performance, especially in cold start scenarios. To address this, Taku SDK optimizes for cold start and supports configuring independent ad request strategies for cold start scenarios, further improving ad impression results.\n\nGlossary: Cold Start: Refers to the scenario where an app is restarted from a fully closed state. An app is generally considered to be in a fully closed state when it has never been launched, has been in the background for too long and reclaimed by the system, or has been actively killed by the user. Difference between cold start and hot start: Cold start requires creating and initializing the app, then loading the page; hot start refers to the scenario where the app is already open but was sent to the background by pressing the Back key, Home key, etc., or the app was switched away from, and is then reopened. Hot start does not require creating and initializing the app, and the page loads directly.\n\nThis document describes how to configure Taku SDK's cold start traffic group to optimize cold start Splash Ad impression results.\n1. Introduction\nTaku supports developers adding Cold Start Request rules when setting up traffic groups, serving as that placement's Cold Start Strategy. When the app is in a cold start state, Taku reads the Cold Start Strategy to request ads, improving the ad display rate during cold start.\nIf an app needs to support Cold Start Strategy, no additional code development is required; simply update to Taku SDK v6.1.78 or above.\n2. Creating a Traffic Group for Cold Start Strategy\nTo use the Cold Start Strategy, you need to add cold start rules under a traffic group. The specific process is as follows:\n(1) On the Mediation Management page, add or edit a traffic group, add a new traffic group rule, and select Cold Start Request\n\n(2) The Cold Start Request rule in a traffic group can be used simultaneously with other rules, but this also means that in cold start scenarios, all other set rules must also be satisfied for the strategy to take effect.\n3. FAQ\n(1) What is the relationship and difference between Cold Start Strategy and SDK Preset Strategy?\nAnswer:\n1 Similarities: Both Cold Start Strategy and SDK Preset Strategy preload strategies on the client side to reduce network request latency and support configuring independent ad Waterfall request strategies to optimize Splash scenario efficiency.\n2 Differences: SDK Preset Strategy is exported from the Taku backend and preloaded into the app when integrating Taku SDK. The SDK Preset Strategy is released with the app and is only used during the first launch after install or update. Once Taku SDK successfully fetches the online ad placement strategy, it will no longer be used. Cold Start Strategy is fetched online and is used during cold starts when the app is not being launched for the first time after installation.\nA more intuitive explanation can be found in the diagram below:\n\n(2) How to improve Splash Ad loading efficiency?\nFor v6.1.78 and above, refer to the following optimization suggestions:\n\n\nFor the first launch after install scenario, set up SDK Preset Strategy and import it during app version integration. For specific settings and usage instructions of the preset strategy, refer to SDK Preset Strategy Documentation.\n\n\nFor cold start scenarios that are not the first launch, set up Cold Start Strategy. It is recommended to reduce the number of high-price Waterfall tiers, enable Taku ADX to speed up the Splash Ad retrieval, and consider increasing the number of concurrent requests.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1782799888","update_time":"1782884289"},"pure_content":"Ad request latency significantly impacts Splash Ad impression performance, especially in cold start scenarios. To address this, Taku SDK optimizes for cold start and supports configuring independent a"},{"id":"844709","string_id":"WfbYYEzV","status":"1","parent_id":"844706","slug":"WfbYYEzV","order":"3","name":"Custom Traffic Grouping","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1782884289","add_time":"1782799890","update_time":"1782962831","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"844709","content":"> **Tips:**\n> \n> 1. It is recommended to call the corresponding method before Taku SDK initialization to pass custom rule parameters.\n> 2. For more information about traffic groups, please refer to [Traffic Groups](\/docs\/KjVUSq)\n\n1. App-Level Global Custom Rule Settings\n----------------\n\n> **Note:** This custom rule is a **global** setting and applies to all Ad Placements.\n\n| Platform | Method |\n|---|---|\n| Android | initCustomMap |\n| iOS | customData |\n| Unity | initCustomMap |\n\n \n**Predefined Keys for Custom Rules**\n\nTaku SDK predefines the following keys for App-level global custom rules:\n\n| Key | Description |\n|---|---|\n| user\\_id | User ID. Defined and passed by the developer to TopOn SDK. Subsequently, TopOn supports statistics based on the User ID dimension. |\n| channel | Channel. It is recommended to use the following character rules: uppercase and lowercase letters, digits, and underscores \\[A-Za-z0-9\\_\\] |\n| sub\\_channel | Sub-Channel. It is recommended to use the following character rules: uppercase and lowercase letters, digits, and underscores \\[A-Za-z0-9\\_\\] |\n| user\\_number | User Number. Developers can assign numbers to users, such as each user corresponding to a globally non-unique number. Only supported by Android SDK v6.1.32 and above. |\n| age | Age |\n| gender | Gender, e.g., male, female, unknow |\n| iap\\_amount | In-App Purchase Amount |\n| iap\\_currency | In-App Purchase Currency, e.g., \"USD\" |\n| iap\\_time | In-App Purchase Count |\n\n\n\n\n\n\n\n> **Note:** If the above predefined keys cannot meet your needs, you may add custom keys. Note, however, that the key must match when adding custom traffic groups.\n\n2. Placement-Level Custom Rule Settings\n--------------------\n\n> **Note:** This custom rule only applies to the **current** Placement. You can add Placement-specific custom rules on top of the App-level custom rules.\n\n| Platform | Method |\n|---|---|\n| Android | initPlacementCustomMap |\n| iOS | setCustomData:forPlacementID |\n| Unity | setCustomDataForPlacementID |\n\n3. Sample Code\n-------\n\n> **Note:** The following code sample represents a user with **age=18**, **male**, acquired through the ByteDance promotion channel.\n\n**Android**\n```\nMap customMap = new HashMap<>();\ncustomMap.put(\"age\",\"18\"); \ncustomMap.put(\"gender\",\"male\"); \ncustomMap.put(\"channel\",\"bytedance\"); \nATSDK.initCustomMap(customMap); \/\/ Effective for all Placements\nATSDK.initPlacementCustomMap(placementId, customMap); \/\/ Effective only for the current Placement\n```\n\n\n\n**iOS**\n\n```\n\/\/ Effective for all Placements\n[ATAPI sharedInstance].customData = @{kATCustomDataUserIDKey:@\"test_custom_user_id\",\n kATCustomDataChannelKey:@\"custom_data_channel\",\n kATCustomDataSubchannelKey:@\"custom_data_subchannel\",\n kATCustomDataAgeKey:@18,\n kATCustomDataGenderKey:@\"male\",\n kATCustomDataNumberOfIAPKey:@19,\n kATCustomDataIAPAmountKey:@20.0f,\n kATCustomDataIAPCurrencyKey:@\"usd\",\n}; \n\n\/\/ Effective only for the current Placement\n[[ATAPI sharedInstance] setCustomData:@{\n kATCustomDataChannelKey:@\"placement_custom_data_channel\",\n kATCustomDataSubchannelKey:@\"placement_custom_data_subchannel\"\n} forPlacementID:@\"your placementID\"];\n\n```\n\n**Unity**\n\n```\n\/\/ Set custom Map info to match the configured ad source priority list (App level) (optional)\nATSDKAPI.initCustomMap(new Dictionary { { \"unity3d_data\", \"test_data\" } }); \n\n\/\/ Set custom Map info to match the configured ad source priority list (Placement level) (optional)\nATSDKAPI.setCustomDataForPlacementID(new Dictionary { { \"unity3d_data_pl\", \"test_data_pl\" } } ,placementId);\n\n```","pure_content":"Tips:\n\nIt is recommended to call the corresponding method before Taku SDK initialization to pass custom rule parameters.\nFor more information about traffic groups, please refer to Traffic Groups\n\n\n\n\nApp-Level Global Custom Rule Settings\n\n\n\nNote: This custom rule is a global setting and applies to all Ad Placements.\n\n\n\n\n Platform\n Method\n\n\n\n\n Android\n initCustomMap\n\n\n iOS\n customData\n\n\n Unity\n initCustomMap\n\n\n\nPredefined Keys for Custom Rules\nTaku SDK predefines the following keys for App-level global custom rules:\n\n\n\n Key\n Description\n\n\n\n\n user_id\n User ID. Defined and passed by the developer to TopOn SDK. Subsequently, TopOn supports statistics based on the User ID dimension.\n\n\n channel\n Channel. It is recommended to use the following character rules: uppercase and lowercase letters, digits, and underscores [A-Za-z0-9_]\n\n\n sub_channel\n Sub-Channel. It is recommended to use the following character rules: uppercase and lowercase letters, digits, and underscores [A-Za-z0-9_]\n\n\n user_number\n User Number. Developers can assign numbers to users, such as each user corresponding to a globally non-unique number. Only supported by Android SDK v6.1.32 and above.\n\n\n age\n Age\n\n\n gender\n Gender, e.g., male, female, unknow\n\n\n iap_amount\n In-App Purchase Amount\n\n\n iap_currency\n In-App Purchase Currency, e.g., \"USD\"\n\n\n iap_time\n In-App Purchase Count\n\n\n\n\nNote: If the above predefined keys cannot meet your needs, you may add custom keys. Note, however, that the key must match when adding custom traffic groups.\n\n\nPlacement-Level Custom Rule Settings\n\n\n\nNote: This custom rule only applies to the current Placement. You can add Placement-specific custom rules on top of the App-level custom rules.\n\n\n\n\n Platform\n Method\n\n\n\n\n Android\n initPlacementCustomMap\n\n\n iOS\n setCustomData:forPlacementID\n\n\n Unity\n setCustomDataForPlacementID\n\n\n\n\nSample Code\n\n\n\nNote: The following code sample represents a user with age=18, male, acquired through the ByteDance promotion channel.\n\nAndroid\nMap customMap = new HashMap();\ncustomMap.put(\"age\",\"18\"); \ncustomMap.put(\"gender\",\"male\"); \ncustomMap.put(\"channel\",\"bytedance\"); \nATSDK.initCustomMap(customMap); \/\/ Effective for all Placements\nATSDK.initPlacementCustomMap(placementId, customMap); \/\/ Effective only for the current Placement\n\niOS\n\/\/ Effective for all Placements\n[ATAPI sharedInstance].customData = @{kATCustomDataUserIDKey:@\"test_custom_user_id\",\n kATCustomDataChannelKey:@\"custom_data_channel\",\n kATCustomDataSubchannelKey:@\"custom_data_subchannel\",\n kATCustomDataAgeKey:@18,\n kATCustomDataGenderKey:@\"male\",\n kATCustomDataNumberOfIAPKey:@19,\n kATCustomDataIAPAmountKey:@20.0f,\n kATCustomDataIAPCurrencyKey:@\"usd\",\n}; \n\n\/\/ Effective only for the current Placement\n[[ATAPI sharedInstance] setCustomData:@{\n kATCustomDataChannelKey:@\"placement_custom_data_channel\",\n kATCustomDataSubchannelKey:@\"placement_custom_data_subchannel\"\n} forPlacementID:@\"your placementID\"];\n\n\nUnity\n\/\/ Set custom Map info to match the configured ad source priority list (App level) (optional)\nATSDKAPI.initCustomMap(new Dictionary { { \"unity3d_data\", \"test_data\" } }); \n\n\/\/ Set custom Map info to match the configured ad source priority list (Placement level) (optional)\nATSDKAPI.setCustomDataForPlacementID(new Dictionary { { \"unity3d_data_pl\", \"test_data_pl\" } } ,placementId);","is_draft":"0","editor_type":"2","file_path":"","add_time":"1782799890","update_time":"1782962831"},"pure_content":"Tips:\n\nIt is recommended to call the corresponding method before Taku SDK initialization to pass custom rule parameters.\nFor more information about traffic groups, please refer to Traffic Groups"},{"id":"844710","string_id":"TVGLPdoI","status":"1","parent_id":"844706","slug":"TVGLPdoI","order":"2","name":"SDK Preset Strategy","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1782884285","add_time":"1782799892","update_time":"1788919941","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"844710","content":"To reduce the time Taku SDK takes to fetch Taku Ad Placement strategy on the first request, and to avoid scenarios where Taku SDK fails to fetch the Taku Ad Placement strategy, Taku supports preloading Taku Ad Placement strategy locally within the app.\n\nTaku SDK supports all ad types using **SDK Preset Strategy**: Splash, Rewarded Video, Interstitial, Native, and Banner.\n\n**1.** Introduction\n-----\n\nTaku supports developers exporting **Ad Placement-level SDK Preset Strategy** and preloading it into the app before release. When the Ad Placement is requested for the first time, Taku uses the SDK Preset Strategy to request ads, improving ad request efficiency on the first request.\n\n> **Notes:**\n> \n> 1. Preloading SDK strategy locally in the app requires updating to Taku SDK v6.1.78 or above.\n> \n> **2. SDK Preset Strategy is only used for the first Ad Placement request.** Once Taku SDK successfully fetches the online Ad Placement strategy, subsequent requests will use the Taku online Ad Placement strategy.\n\n**2.** Creating a Traffic Group for SDK Preset Strategy\n-----------------\n> **Note:**\nIf an A\/B test is currently in progress for the ad placement (including traffic group A\/B tests and ad placement A\/B tests), creating an SDK preset strategy group is not supported at this time.\n\nUsing SDK Preset Strategy requires creating a specific traffic group. The process is as follows:\n\n(1) On the Mediation Management page, add a traffic group and select **SDK Built-in Strategy** as the traffic group rule.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/xConRS\/65e8427c37c24.png)\n\n(2) The **SDK Preset Strategy** rule in a traffic group cannot be used simultaneously with other rules.\n\n**(3) SDK Preset Strategy traffic group's Ad Placement strategy is only for export and preloading into your app.**\n\n(4) If you modify the **SDK Preset Strategy**, you need to re-export and preload it into your app.\n\n(5) You can create multiple **SDK Preset Strategies** under a Taku Ad Placement. To better analyze the performance of **SDK Preset Strategy** across different Taku SDK versions, it is recommended to create different **SDK Preset Strategies** for different Taku SDK versions.\n\n**3.** Configuring SDK Preset Strategy\n------------\n\nAfter creating the **SDK Preset Strategy** traffic group, you can configure this **SDK Preset Strategy** just like other traffic groups, such as adding\/editing\/copying Ad Sources, modifying Advanced Settings, etc.\n\n**4.** Exporting SDK Preset Strategy\n------------\n\n(1) After modifying the SDK Preset Strategy's Ad Placement strategy, the Taku server needs 15 minutes to complete the new strategy synchronization. It is recommended to wait 15 minutes after completing the SDK Preset Strategy configuration before exporting the SDK Preset Strategy.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/xConRS\/65e8427c9a04c.png)\n\n(2) When **exporting SDK Preset Strategy**, you need to select the Taku SDK version used in your app. Ensure that the exported Taku SDK version matches the Taku SDK version integrated in your app. (**SDK version >= Preset Strategy export version**)\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/xConRS\/65e8427d01ee3.png)\n\n(3) If the following prompt appears when exporting SDK Preset Strategy, it means the Taku server has not yet completed the Ad Placement strategy synchronization for the SDK Preset Strategy. It is recommended to wait 15 minutes before exporting the SDK Preset Strategy again.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/xConRS\/65e8427d582da.png)\n\n(4) After successfully **exporting the SDK Preset Strategy**, Taku generates a json file named after the Ad Placement ID.\n\n5. Importing SDK Preset Strategy into the App\n---------------\n\n1. Place the exported json file into your app project, and follow the SDK integration documentation to complete the **SDK Preset Strategy** code integration in the app project.\n2. Refer to the Taku SDK integration instructions below.\n\n### 5.1 Android Integration Instructions\n\n(1) Create a directory named localStrategy under the project's src\/main\/assets directory. The directory naming rule can be customized and is used in the following steps.\n\n(2) Place the json file exported from the backend into the newly created directory src\/main\/assets\/localStrategy.\n\n(3) Simply call the ATSDK#setLocalStrategyAssetPath(Context context, String path) API before initiating ad loading. The Path parameter is the directory name localStrategy created in step one. Sample code:\n\n```\n\/\/ Called in Application#onCreate()\npublic class DemoApplication extends Application {\n @Override\n public void onCreate() {\n super.onCreate();\n \/\/...\n ATSDK.setLocalStrategyAssetPath(this, \"localStrategy\");\n \/\/...\n }\n}\n\n```\n\n### 5.2 iOS Integration Instructions\n\n(1) Import the json file exported from the backend into the project.\n\n(2) Call the setPresetPlacementConfigPathBundle: API before initiating ad loading. The Bundle parameter is the Bundle where the json file was imported into the project. Sample code:\n\n```\n\/\/ Pass the Bundle where the json file was imported into the project. This example uses mainBundle\n[[ATAPI sharedInstance] setPresetPlacementConfigPathBundle:[NSBundle mainBundle]];\n```\n\n**6.** Viewing SDK Preset Strategy Data\n---------------\n\n(1) You can view the **SDK Preset Strategy** traffic group on the **Mediation Management** page. You can also filter by **A\/B Test** and **Traffic Group** in the **Comprehensive Report** to view the **SDK Preset Strategy** traffic group data.\n\n(2) If the Ad Placement already had an **SDK Preset Strategy** traffic group created before enabling A\/B Test, after enabling A\/B Test, the **SDK Preset Strategy** traffic group will also be copied to the experiment group with the smallest ID in the A\/B Test.\n\n(3) After enabling A\/B Test, the original **SDK Preset Strategy** traffic group's data can be viewed under **Ungrouped**.\n\n**7.** FAQ\n-------\n\n**(1) How long after completing SDK Preset Strategy configuration can I export?**\n\nAnswer: After modifying the SDK Preset Strategy's Ad Placement strategy, the Taku server needs 15 minutes to complete the new strategy synchronization. It is recommended to wait 15 minutes after completing the SDK Preset Strategy configuration before exporting the SDK Preset Strategy.\n\n**(2) Do I need to re-import the Taku SDK Preset Strategy file every time I release an app update?**\n\nAnswer: It is recommended to re-import the Taku **SDK Preset Strategy** file in the following situations:\n\n(1) If this app release includes a Taku SDK update, it is recommended to re-export the **SDK Preset Strategy** for the updated Taku SDK version and preload it into the app (ensure the exported Taku SDK version matches the Taku SDK version integrated in your app).\n\n(2) When you have modified the **SDK Preset Strategy** Ad Placement strategy, it is recommended to re-import the Taku **SDK Preset Strategy** in the next app release.\n\n**(3) What is the impact if the new app version updates Taku SDK but does not update the old SDK Preset Strategy file?**\n\nAnswer: The new version of Taku SDK will be backward-compatible with the old version of the **SDK Preset Strategy** file. If the new version adds new Ad Placement strategy features, but your app has not re-imported the corresponding version of the **SDK Preset Strategy** file, the new features of the new Taku SDK version may not take effect. To ensure better monetization results, if you have updated the Taku SDK version, it is recommended to re-export the **SDK Preset Strategy** for the updated Taku SDK version and preload it into the app.\n\nNote: **Older versions of Taku SDK cannot use newer versions of the SDK Preset Strategy file.**\n\n**(4) How to improve first-launch Splash loading efficiency?**\n\nFor v6.1.78 and above, refer to the following optimization suggestions:\n\n1. Add a **Fallback Ad Source** to the Splash Ad Placement's **SDK Preset Strategy**. Refer to [Fallback Ad](https:\/\/help.takuad.com\/docs\/cXus5n#3._%E5%85%9C%E5%BA%95%E5%B9%BF%E5%91%8A) to configure the Ad Source (you do not need to export the Fallback Ad Source configuration).\n\n2. Use **SDK Preset Strategy** for the Splash Ad Placement during app integration.","pure_content":"To reduce the time Taku SDK takes to fetch Taku Ad Placement strategy on the first request, and to avoid scenarios where Taku SDK fails to fetch the Taku Ad Placement strategy, Taku supports preloading Taku Ad Placement strategy locally within the app.\nTaku SDK supports all ad types using SDK Preset Strategy: Splash, Rewarded Video, Interstitial, Native, and Banner.\n1. Introduction\nTaku supports developers exporting Ad Placement-level SDK Preset Strategy and preloading it into the app before release. When the Ad Placement is requested for the first time, Taku uses the SDK Preset Strategy to request ads, improving ad request efficiency on the first request.\n\nNotes:\n\nPreloading SDK strategy locally in the app requires updating to Taku SDK v6.1.78 or above.\n\n2. SDK Preset Strategy is only used for the first Ad Placement request. Once Taku SDK successfully fetches the online Ad Placement strategy, subsequent requests will use the Taku online Ad Placement strategy.\n\n2. Creating a Traffic Group for SDK Preset Strategy\n\nNote:\nIf an A\/B test is currently in progress for the ad placement (including traffic group A\/B tests and ad placement A\/B tests), creating an SDK preset strategy group is not supported at this time.\n\nUsing SDK Preset Strategy requires creating a specific traffic group. The process is as follows:\n(1) On the Mediation Management page, add a traffic group and select SDK Built-in Strategy as the traffic group rule.\n\n(2) The SDK Preset Strategy rule in a traffic group cannot be used simultaneously with other rules.\n(3) SDK Preset Strategy traffic group's Ad Placement strategy is only for export and preloading into your app.\n(4) If you modify the SDK Preset Strategy, you need to re-export and preload it into your app.\n(5) You can create multiple SDK Preset Strategies under a Taku Ad Placement. To better analyze the performance of SDK Preset Strategy across different Taku SDK versions, it is recommended to create different SDK Preset Strategies for different Taku SDK versions.\n3. Configuring SDK Preset Strategy\nAfter creating the SDK Preset Strategy traffic group, you can configure this SDK Preset Strategy just like other traffic groups, such as adding\/editing\/copying Ad Sources, modifying Advanced Settings, etc.\n4. Exporting SDK Preset Strategy\n(1) After modifying the SDK Preset Strategy's Ad Placement strategy, the Taku server needs 15 minutes to complete the new strategy synchronization. It is recommended to wait 15 minutes after completing the SDK Preset Strategy configuration before exporting the SDK Preset Strategy.\n\n(2) When exporting SDK Preset Strategy, you need to select the Taku SDK version used in your app. Ensure that the exported Taku SDK version matches the Taku SDK version integrated in your app. (SDK version >= Preset Strategy export version)\n\n(3) If the following prompt appears when exporting SDK Preset Strategy, it means the Taku server has not yet completed the Ad Placement strategy synchronization for the SDK Preset Strategy. It is recommended to wait 15 minutes before exporting the SDK Preset Strategy again.\n\n(4) After successfully exporting the SDK Preset Strategy, Taku generates a json file named after the Ad Placement ID.\n\nImporting SDK Preset Strategy into the App\n\n\n\nPlace the exported json file into your app project, and follow the SDK integration documentation to complete the SDK Preset Strategy code integration in the app project.\nRefer to the Taku SDK integration instructions below.\n\n5.1 Android Integration Instructions\n(1) Create a directory named localStrategy under the project's src\/main\/assets directory. The directory naming rule can be customized and is used in the following steps.\n(2) Place the json file exported from the backend into the newly created directory src\/main\/assets\/localStrategy.\n(3) Simply call the ATSDK#setLocalStrategyAssetPath(Context context, String path) API before initiating ad loading. The Path parameter is the directory name localStrategy created in step one. Sample code:\n\/\/ Called in Application#onCreate()\npublic class DemoApplication extends Application {\n @Override\n public void onCreate() {\n super.onCreate();\n \/\/...\n ATSDK.setLocalStrategyAssetPath(this, \"localStrategy\");\n \/\/...\n }\n}\n\n\n5.2 iOS Integration Instructions\n(1) Import the json file exported from the backend into the project.\n(2) Call the setPresetPlacementConfigPathBundle: API before initiating ad loading. The Bundle parameter is the Bundle where the json file was imported into the project. Sample code:\n\/\/ Pass the Bundle where the json file was imported into the project. This example uses mainBundle\n[[ATAPI sharedInstance] setPresetPlacementConfigPathBundle:[NSBundle mainBundle]];\n\n6. Viewing SDK Preset Strategy Data\n(1) You can view the SDK Preset Strategy traffic group on the Mediation Management page. You can also filter by A\/B Test and Traffic Group in the Comprehensive Report to view the SDK Preset Strategy traffic group data.\n(2) If the Ad Placement already had an SDK Preset Strategy traffic group created before enabling A\/B Test, after enabling A\/B Test, the SDK Preset Strategy traffic group will also be copied to the experiment group with the smallest ID in the A\/B Test.\n(3) After enabling A\/B Test, the original SDK Preset Strategy traffic group's data can be viewed under Ungrouped.\n7. FAQ\n(1) How long after completing SDK Preset Strategy configuration can I export?\nAnswer: After modifying the SDK Preset Strategy's Ad Placement strategy, the Taku server needs 15 minutes to complete the new strategy synchronization. It is recommended to wait 15 minutes after completing the SDK Preset Strategy configuration before exporting the SDK Preset Strategy.\n(2) Do I need to re-import the Taku SDK Preset Strategy file every time I release an app update?\nAnswer: It is recommended to re-import the Taku SDK Preset Strategy file in the following situations:\n(1) If this app release includes a Taku SDK update, it is recommended to re-export the SDK Preset Strategy for the updated Taku SDK version and preload it into the app (ensure the exported Taku SDK version matches the Taku SDK version integrated in your app).\n(2) When you have modified the SDK Preset Strategy Ad Placement strategy, it is recommended to re-import the Taku SDK Preset Strategy in the next app release.\n(3) What is the impact if the new app version updates Taku SDK but does not update the old SDK Preset Strategy file?\nAnswer: The new version of Taku SDK will be backward-compatible with the old version of the SDK Preset Strategy file. If the new version adds new Ad Placement strategy features, but your app has not re-imported the corresponding version of the SDK Preset Strategy file, the new features of the new Taku SDK version may not take effect. To ensure better monetization results, if you have updated the Taku SDK version, it is recommended to re-export the SDK Preset Strategy for the updated Taku SDK version and preload it into the app.\nNote: Older versions of Taku SDK cannot use newer versions of the SDK Preset Strategy file.\n(4) How to improve first-launch Splash loading efficiency?\nFor v6.1.78 and above, refer to the following optimization suggestions:\n\n\nAdd a Fallback Ad Source to the Splash Ad Placement's SDK Preset Strategy. Refer to Fallback Ad to configure the Ad Source (you do not need to export the Fallback Ad Source configuration).\n\n\nUse SDK Preset Strategy for the Splash Ad Placement during app integration.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1782799892","update_time":"1788919941"},"pure_content":"To reduce the time Taku SDK takes to fetch Taku Ad Placement strategy on the first request, and to avoid scenarios where Taku SDK fails to fetch the Taku Ad Placement strategy, Taku supports preloadin"},{"id":"844711","string_id":"776qfgoL","status":"1","parent_id":"844706","slug":"776qfgoL","order":"1","name":"Server-Side Reward","type":"2","cover":"","cover_alt":"","desc":null,"website":"","contact":"","seo_title":"","seo_keyword":"","seo_desc":"","share_switch":"0","share_code":"","author":"Welch","published_time":"1782884289","add_time":"1782799893","update_time":"1782962845","corp_auth_id":"0","verify_code_auth_id":"0","editor_type":"2","file_type":"","auth_id":"[\"-1\"]","content":{"content_id":"844711","content":"**1.** Server-Side Reward Introduction\n----------\n\nServer-Side Reward (Server-to-Server): Allows developers to decide whether to grant rewards to users who watch Rewarded Video ads. When a user finishes watching a Rewarded Video, the developer's server will be notified, and the developer will handle the reward distribution.\n\n- Taku SDK < v5.7.56: Developers need to use [Third-party Ad Platform Server-Side Reward](https:\/\/help.takuad.com\/docs\/msbnkj#2._%E7%AC%AC%E4%B8%89%E6%96%B9%E5%B9%BF%E5%91%8A%E5%B9%B3%E5%8F%B0%E6%9C%8D%E5%8A%A1%E7%AB%AF%E6%BF%80%E5%8A%B1%E7%9A%84%E4%BD%BF%E7%94%A8%E6%B5%81%E7%A8%8B)\n- Taku SDK >= v5.7.56: Developers can use [Taku Server-Side Reward](https:\/\/help.takuad.com\/docs\/msbnkj)\n\n> **Note:** To ensure the accuracy of server-side rewards, for third-party ad platforms, it is strongly recommended that developers prioritize using the third-party ad platform's server-side reward callback. For Taku Adx, Direct Offer, and Cross Promotion, developers can directly use Taku's server-side reward callback. You can use the Network Firm ID to determine whether to accept only Taku's server-side reward callback:\n> \n> 1. Taku Adx Network Firm ID = 66\n> \n> 2. Taku Direct Offer Network Firm ID = 67\n> \n> 3. Taku Cross Promotion Network Firm ID = 35\n\n**2.** Usage Flow for Third-Party Ad Platform Server-Side Reward\n--------------------\n\n(1) Developers need to configure the callback URL of their own server in the third-party ad platform's backend.\n\n(2) In code, developers pass **UserID (unique user ID)** and **UserCustomData (user-defined data)** through the Taku SDK API. These parameters will ultimately be passed to the developer via the callback URL.\n\n(3) When a user finishes watching a Rewarded Video, the ad platform will notify the developer through the configured callback URL, and the developer will decide and grant the reward.\n\n> **Ad platforms supporting server-side reward are listed below: (Clickable links lead to the ad platform's documentation on server-side reward. For non-clickable links, please log in to the ad platform's backend directly to configure the callback URL.)**\n\n### 2.1 Android\n\n| Ad Platform | Reference URL | Remarks |\n|---|---|---|\n| Facebook | | |\n| Admob & Google Ad Manger | [https:\/\/support.google.com\/admob\/answer\/9603226?hl=zh-Hans&ref\\_topic=7382891](https:\/\/support.google.com\/admob\/answer\/9603226?hl=zh-Hans&ref_topic=7382891) | |\n| Applovin | - | Please log in to the Applovin backend to configure the callback URL |\n| Mintegral | [http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown\\_v2\/index.html?file=sdk-m\\_sdk-android&lang=cn](http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown_v2\/index.html?file=sdk-m_sdk-android&lang=cn) | |\n| Mopub | | |\n| ironSource | | |\n| UnityAds | | |\n| Vungle | | |\n| AdColony | | |\n| Pangle | [https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=4&docId=5de8d9b725b16b00113af0e5&osType=android#5d15f2](https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=4&docId=5de8d9b725b16b00113af0e5&osType=android#5d15f2) | |\n| AppNext | | |\n| Ogury | | |\n| Huawei | - | Please log in to the Huawei backend to configure the callback URL |\n| Tencent Ads | [https:\/\/developers.adnet.qq.com\/doc\/android\/union\/union\\_reward\\_video](https:\/\/developers.adnet.qq.com\/doc\/android\/union\/union_reward_video) | Please log in to the Tencent Ads backend to configure the callback URL **Supported from Taku SDK v5.7.8 and above** |\n| Sigmob | | **Starting from v5.7.40**, supports passing customData, which is sent to the developer as a JSON string via the developer-configured callback URL (Key is **user\\_custom\\_data**, Value is customData) |\n| Kuaishou | | **Supported from v5.7.25**, both **userId and customData** must be passed before loading the ad |\n| Baidu | | |\n\n\n\n### 2.2 iOS\n\n| Ad Platform | Reference URL | Remarks |\n|---|---|---|\n| Facebook | | |\n| Admob & Google Ad Manger | | |\n| Applovin | | |\n| Mintegral | [http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown\\_v2\/index.html?file=sdk-m\\_sdk-ios&lang=cn](http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown_v2\/index.html?file=sdk-m_sdk-ios&lang=cn) | |\n| ironSource | | |\n| Vungle | | |\n| AdColony | | |\n| Pangle | [https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=23&docId=5de8d72ab1afac00129330e6&osType=ios#620104](https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=23&docId=5de8d72ab1afac00129330e6&osType=ios#620104) | |\n| AppNext | | |\n| Ogury | | |\n| Nend | [Click to View](https:\/\/github.com\/fan-ADN\/nendSDK-iOS\/wiki\/%E6%BF%80%E5%8A%B1%E6%80%A7%E8%A7%86%E9%A2%91%E5%B9%BF%E5%91%8A%E4%BD%BF%E7%94%A8%E6%95%99%E7%A8%8B#%E7%94%A8%E6%88%B7id%E7%9A%84%E8%AE%BE%E7%BD%AE) | |\n| Sigmob | | **Starting from v5.7.41**, supports passing customData, which is sent to the developer as a JSON string via the developer-configured callback URL (Key is **user\\_custom\\_data**, Value is customData) |\n| UnityAds | | |\n| Tapjoy | - | Please log in to the Tapjoy backend to configure the callback URL |\n| Tencent Ads | [https:\/\/developers.adnet.qq.com\/doc\/ios\/union\/union\\_reward\\_video](https:\/\/developers.adnet.qq.com\/doc\/ios\/union\/union_reward_video) | Please log in to the Tencent Ads backend to configure the callback URL **Supported from Taku SDK v5.7.8 and above** |\n| Kuaishou | | |\n| Baidu | | |\n\n\n\n**3.** Taku Server-Side Reward Usage Instructions\n-----------------\n\n1. Taku SDK >= v5.7.56 can use Taku server-side reward callbacks.\n2. Taku SDK >= v5.7.78 and above supports returning impression-level data in Taku server-side reward callbacks (developers can add the {ilrd} parameter in the callback URL to retrieve the corresponding data).\n\n### 3.1 Server-Side Reward Usage Flow\n\n(1) Developers need to enable server-side reward on the Rewarded Video Ad Placement in the Taku backend and configure the callback URL.\n\n(2) Developers need to pass UserID (unique user ID) and UserCustomData (user-defined data) in code through the Taku SDK API. These parameters will ultimately be passed to the developer via the callback URL.\n\n(3) When a user finishes watching a Rewarded Video, the Taku platform will notify the developer through the configured callback URL, and the developer will decide and grant the reward.\n\n### 3.2 Developer Server-Side Reward Integration Guide\n\n(1) Developers need to enable server-side reward on the Rewarded Video Ad Placement in the Taku backend and configure the developer's server-side reward **Callback URL**, as shown below:\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/j5x6Lk\/65e84277975cc.png)\n\nExample of a developer's **Callback URL**:\n\n```\nhttps:\/\/www.takuad.com\/onrewardedverify?user_id={user_id}&trans_id={trans_id}&reward_amount={reward_amount}&reward_name={reward_name}&placement_id={placement_id}&extra_data={extra_data}&network_firm_id={network_firm_id}&adsource_id={adsource_id}&scenario_id={scenario_id}&sign={sign}&ilrd={ilrd}\n```\n\n(2) Taku will request the developer's **Callback URL** via **GET method**, appending the following parameters:\n\n```\nuser_id={user_id}&trans_id={trans_id}&reward_amount={reward_amount}&reward_name={reward_name}&placement_id={placement_id}&extra_data={extra_data}&network_firm_id={network_firm_id}&adsource_id={adsource_id}&scenario_id={scenario_id}&sign={sign}&ilrd={ilrd}\n```\n\n(3) The placeholders for the developer's custom callback URL information are as follows. Note:\n\n1. You do not need to configure all placeholders; configure only those for the information you need.\n2. If the signature mechanism is required (i.e., configured with sign={sign}), then all placeholders involved in the signing process (see below: **sign** Signature Rules) must be configured.\n3. In addition to the custom configured information, the callback URL sent to the developer may sometimes include additional RMB-to-USD exchange rate information (e.g., exch\\_rate\\_c2u=0.1375), which can be ignored if not needed.\n4. When creating or editing a server-side reward Ad Placement in the developer backend, Taku will default to calling back the reward URL configured in the backend once. This is to immediately check whether the developer-configured URL is working properly. In this callback, the URL placeholders are not replaced, and an additional callback parameter is\\_test=1 is appended.\n\n| Parameter | Description | Remarks |\n|---|---|---|\n| {user\\_id} | User ID | Set by the developer via the Taku SDK API |\n| {extra\\_data} | User business parameters | Set by the developer via the Taku SDK API |\n| {trans\\_id} | Trans ID generated by the Taku server, globally unique | **It is strongly recommended that developers verify whether a reward has already been issued for the trans_id on their server before granting the reward, to avoid issuing duplicate rewards for the same trans_id (corresponds to `getShowId()` in the client-side impression callback).** |\n| {reward\\_name} | Reward name | Configured in the developer backend (supports configuration at **Ad Placement** or **Ad Scene** level) |\n| {reward\\_amount} | Reward amount | Configured in the developer backend (supports configuration at **Ad Placement** or **Ad Scene** level) |\n| {placement\\_id} | Taku Ad Placement ID | - |\n| {network\\_firm\\_id} | Ad Platform ID in Taku Mediation | **[Special Note] 1). If you need to use server-side reward and also use Taku Adx, Direct Offer, or Cross Promotion: For third-party ad platforms, it is recommended to prioritize using the third-party ad platform's server-side reward callback. For Taku Adx, Direct Offer, and Cross Promotion, you can use Taku's server-side reward callback. 2). You can use the Network Firm ID to determine whether to accept only Taku's server-side reward callback: 1. Taku Adx Network Firm ID = 66 2. Taku Direct Offer Network Firm ID = 67 3. Taku Cross Promotion Network Firm ID = 35 [View Taku Ad Platform ID List](https:\/\/help.takuad.com\/docs\/JSLSJN#outline_3)** |\n| {adsource\\_id} | Taku Ad Source ID | - |\n| {scenario\\_id} | Taku Ad Scene ID | Set by the developer via the Taku SDK API |\n| {package\\_name} | Developer app package name or Bundle ID | Obtained by Taku SDK from the developer's app package name or Bundle ID |\n| {platform} | System platform, Android or iOS | Returned as the following enum: 1: Android, 2: iOS |\n| {ilrd} | Impression-level data called back by Taku SDK. **The data is a JSON string.** | **Supported by Taku SDK v5.7.78 and above.** Taku SDK provides impression-level data to developers when calling back the Rewarded Video OnReward event. [Refer to specific data format](https:\/\/help.takuad.com\/docs\/msbnkj#5._ILRD%E6%95%B0%E6%8D%AE%E8%AF%B4%E6%98%8E) **Note: The ilrd parameter is only for behavioral data analysis reference and cannot be directly used as the basis for reward distribution.** |\n| {sign} | Signature information | Refer to the signature rules description |\n\n\n\n**(4) sign** Signature Rules Description\n\nWhen receiving Taku's server-side reward callback, developers can verify the callback parameters using the sign.\n\n1. Taku server generates the sign signature as follows (without ilrd):\n\n```\nsign =MD5(\"trans_id=\"+trans_id+\"&placement_id=\"+placement_id+\"&adsource_id=\"+adsource_id+\"&reward_amount=\"+reward_amount+\"&reward_name=\"+reward_name+\"&sec_key=\"+sec_key)\n\n```\n\n2. Taku server generates the sign signature as follows (with ilrd):\n\nIf the callback URL includes the {ilrd} parameter, the following sign signature rule must be used:\n\n```\nsign =MD5(\"trans_id=\"+trans_id+\"&placement_id=\"+placement_id+\"&adsource_id=\"+adsource_id+\"&reward_amount=\"+reward_amount+\"&reward_name=\"+reward_name+\"&sec_key=\"+sec_key+\"&ilrd=\"+ilrd)\n\n```\n\n(5) sign Signature Example\n\n| Parameter | Example |\n|---|---|\n| trans\\_id | xxxxxxxxxxxxxxxx |\n| placement\\_id | b5b449fb3d89d7 |\n| adsource\\_id | 56789 |\n| reward\\_amount | 1 |\n| reward\\_name | coin |\n| sec\\_key | cyvmwmzrqts7csphhexpqxqxxgljfisb |\n| ilrd | abc |\n\n\n\nsign signature example:\n\n```\nsign=MD5(trans_id=xxxxxxxxxxxxxxxx&placement_id=b5b449fb3d89d7&adsource_id=56789&reward_amount=1&reward_name=coin&sec_key=cyvmwmzrqts7csphhexpqxqxxgljfisb&ilrd=abc)\n```\n\n(6) After the developer's callback URL receives Taku's server-side reward callback, it must return a status code of **200 or 601 or 602** to the Taku server. After Taku receives a success or failure status code, it will not resend the server-side reward callback.\n\nSpecial note: The callback data may sometimes be very large (especially when ilrd is included). Developers should ensure that the GET callback URL length limit is removed, otherwise the developer's server may return a 414 error (for example, when using nginx, which has a default length limit).\n\n| Return Status Code | Description |\n|---|---|\n| 200 | Success |\n| 601 | Signature verification failed |\n| 602 | Other failure |\n\n\n\nIf there is no response within 2 seconds after the Taku server initiates the server-side reward callback, it is considered a timeout. After a timeout, Taku will retry sending the reward callback at intervals (e.g., 2 seconds, 4 seconds, 8 seconds, etc.). If Taku has retried a maximum of 5 times and still times out, it will no longer send the reward callback to the developer's callback URL.\n\n### 3.3 Per-Ad-Scene Server-Side Reward\n\nTo support developers granting different rewards in different Rewarded Video ad scenes, Taku allows developers to set different reward names and reward amounts for different ad scenes. The specific usage flow is as follows:\n\n(1) Enable the server-side reward callback for the Rewarded Video Ad Placement and receive the Taku callback's **Ad Scene ID {scenario\\_id}** in the **callback URL**.\n\n(2) Set the **reward amount** and **reward name** under the ad scene in the Taku backend, as shown below:\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/j5x6Lk\/65e842780a0f3.png)\n\n(3) When receiving Taku's server-side reward callback, the developer grants different rewards based on the **Ad Scene ID {scenario\\_id}**.\n\n### 3.4 Quick Reuse of Server-Side Reward Rules\n\nTo reduce the time developers spend manually configuring server-side reward callback rules, Taku allows developers to quickly reuse server-side reward callback rules. The steps are as follows:\n\n(1) In the **Advanced Features** dropdown menu, go to **Server-Side Callback**.\n\n(2) Create a **Callback Rule**, edit it, and save the rule.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/j5x6Lk\/65e842786bc55.png)\n\n(3) When creating or editing an Ad Placement, enable the server-side callback toggle and select the corresponding rule to quickly reuse that rule.\n\n![](https:\/\/resource.helplook.net\/docker_production\/5expvy\/article\/j5x6Lk\/65e84278d61aa.png)\n\n**4.** Taku SDK Integration\n-------------\n\n### 4.1 Taku Android SDK Code Sample\n\n```\nMap localMap = new HashMap<>();\nlocalMap.put(ATAdConst.KEY.USER_ID, \"test_user_id\");\nlocalMap.put(ATAdConst.KEY.USER_CUSTOM_DATA, \"test_user_data\");\nmRewardVideoAd.setLocalExtra(localMap);\n\nmRewardVideoAd.load();\n```\n\n### 4.2 Taku iOS SDK Code Sample\n\n```\n[[ATAdManager sharedManager] loadADWithPlacementID:placementId extra:@{kATAdLoadingExtraMediaExtraKey:@\"test_user_data\", kATAdLoadingExtraUserIDKey:@\"test_user_id\"} delegate:self];\n```\n\n### 4.3 Taku Unity SDK Code Sample\n\n```\nDictionary jsonmap = new Dictionary();\n\njsonmap.Add(ATConst.USERID_KEY, \"test_user_id\");\njsonmap.Add(ATConst.USER_EXTRA_DATA, \"test_user_data\");\n\nATRewardedVideo.Instance.loadVideoAd(placementId, jsonmap);\n```\n\n### 4.4 Taku Cocos2dx SDK Code Sample\n\n```\ncocos2d::ValueMap extra;\nextra[ATCocosSdk::KEY_USER_ID] = \"test_user_id\";\nextra[ATCocosSdk::KEY_MEDIA_EXT] = \"test_user_data\";\nATCocosSdk::loadRewardedVideoAd(placementId, extra);\n```\n\n### 4.5 Taku CocosCreator SDK Code Sample\n\n```\nvar setting = {};\nsetting[ATRewardedVideoJSSDK.userIdKey] = \"test_user_id\";\nsetting[ATRewardedVideoJSSDK.userDataKey] = \"test_user_data\";\nATRewardedVideoJSSDK.loadRewardedVideo(placementId, setting);\n```\n\n### 4.6 Taku ReactNative SDK Code Sample\n\n```\nvar setting = {};\nsettings[ATRewardedVideoRNSDK.userIdKey] = \"test_user_id\";\nsettings[ATRewardedVideoRNSDK.userDataKey] = \"test_user_data\";\nATRewardedVideoRNSDK.loadAd(placementId, settings);\n```\n\n**5.** ILRD Data Description\n-----------\n\n**Note: The ilrd parameter is only for behavioral data analysis reference and cannot be directly used as the basis for reward distribution. If you need to use impression revenue data for reward share calculations, please use impression revenue data. Reference documents:** **[Impression Ad Source eCPM Encryption](https:\/\/help.takuad.com\/docs\/ecpm_key), [Ad Impression Server-Side Callback (S2S)](https:\/\/help.takuad.com\/docs\/9frd63)**\n\n| Variable | Type | Description |\n|---|---|---|\n| network\\_firm\\_id | int | Gets the Ad Platform corresponding ID, used to distinguish ad platforms. |\n| adsource\\_id | string | Gets the Ad Source ID. You can query specific Network information by Ad Source ID in the developer backend or via Taku Open API. |\n| adsource\\_index | int | Gets the current Ad Source's position in the WaterFall **(starting from 0)**. |\n| adsource\\_price | dounble | Gets the ECPM, the unit can be obtained via **\"currency\"**. |\n| adsource\\_isheaderbidding | int | Whether it is a Header Bidding Ad Source, **1: Yes, 2: No**. |\n| id | string | Gets the unique ID generated for each **ad impression**. |\n| publisher\\_revenue | double | Gets the impression revenue. |\n| currency | string | Gets the currency unit, e.g., \"USD\". |\n| country | string | Gets the country code, e.g., \"CN\". |\n| adunit\\_id | string | Gets the Taku Ad Placement ID. |\n| adunit\\_format | string | Gets the ad type, including: **\"Native\", \"RewardedVideo\", \"Banner\", \"Interstitial\", \"Splash\"**. |\n| precision | string | Gets the ECPM precision. **\"publisher\\_defined\"**: The eCPM defined by the developer for the Ad Source in the Taku backend **(cross-promotion eCPM also falls under this type)**. **\"estimated\"**: Taku's estimated eCPM (auto eCPM). **\"exact\"**: Header Bidding real-time bidding eCPM. |\n| network\\_type | string | Gets the Network type. **\"Network\"**: Third-party ad platform. **\"Cross\\_Promotion\"**: Cross promotion. **\"Adx\"**: Taku Adx. |\n| network\\_placement\\_id | string | Gets the Network's Ad Placement ID. |\n| ecpm\\_level | int | Gets the Ad Source's eCPM tier, **Header Bidding Ad Sources default to 0**. |\n| segment\\_id | int | Gets the Traffic Group ID. |\n| scenario\\_id | string | Gets the Ad Scene ID, **only supported for Rewarded Video & Interstitial (starting from v5.7.20, Native & Banner are also supported)**. |\n| scenario\\_reward\\_name | string | Gets the Ad Scene reward name, **only supported for Rewarded Video**. |\n| scenario\\_reward\\_number | int | Gets the Ad Scene reward amount, **only supported for Rewarded Video**. |\n| sub\\_channel | string | Gets the sub-channel information. |\n| channel | string | Gets the channel information. |\n| custom\\_rule | Dictionary | Gets the **JSON string** of custom rules at the **Placement + App level**. |\n| user\\_load\\_extra\\_data | string | Gets the custom parameters passed during Load, corresponding to [getLocalExtra()](https:\/\/help.takuad.com\/docs\/JSLSJN). |\n| show\\_custom\\_ext | show\\_custom\\_ext | Gets the custom parameters passed during Show, corresponding to [getShowCustomExt()](https:\/\/help.takuad.com\/docs\/JSLSJN). |\n\n\n\n**6. FAQ**\n-----------\n\n**(1) What is the difference between Taku's server-side reward callback and third-party platforms' callbacks?**\n\n1. Taku's server-side reward callback provides reward callbacks that include data such as Taku ADX and third-party platform estimated eCPM.\n\nIf using Taku ADX, Cross Promotion, Direct Offer ads, etc., configuring the server-side reward callback in Taku will be more accurate. Third-party platform server-side reward callbacks will be more accurate when going through the respective third-party platform.\n\n2. **To ensure the accuracy of reward callbacks as much as possible, it is recommended to use client-side reward callbacks, third-party server-side reward callbacks, and Taku server-side reward callbacks simultaneously, and perform parameter consistency verification across all three callbacks.**","pure_content":"1. Server-Side Reward Introduction\nServer-Side Reward (Server-to-Server): Allows developers to decide whether to grant rewards to users who watch Rewarded Video ads. When a user finishes watching a Rewarded Video, the developer's server will be notified, and the developer will handle the reward distribution.\n\nTaku SDK Third-party Ad Platform Server-Side Reward\n\nTaku SDK >= v5.7.56: Developers can use Taku Server-Side Reward\n\n\n\nNote: To ensure the accuracy of server-side rewards, for third-party ad platforms, it is strongly recommended that developers prioritize using the third-party ad platform's server-side reward callback. For Taku Adx, Direct Offer, and Cross Promotion, developers can directly use Taku's server-side reward callback. You can use the Network Firm ID to determine whether to accept only Taku's server-side reward callback:\n\n\nTaku Adx Network Firm ID = 66\n\n\nTaku Direct Offer Network Firm ID = 67\n\n\nTaku Cross Promotion Network Firm ID = 35\n\n\n\n2. Usage Flow for Third-Party Ad Platform Server-Side Reward\n(1) Developers need to configure the callback URL of their own server in the third-party ad platform's backend.\n(2) In code, developers pass UserID (unique user ID) and UserCustomData (user-defined data) through the Taku SDK API. These parameters will ultimately be passed to the developer via the callback URL.\n(3) When a user finishes watching a Rewarded Video, the ad platform will notify the developer through the configured callback URL, and the developer will decide and grant the reward.\n\nAd platforms supporting server-side reward are listed below: (Clickable links lead to the ad platform's documentation on server-side reward. For non-clickable links, please log in to the ad platform's backend directly to configure the callback URL.)\n\n2.1 Android\n\n\n\n Ad Platform\n Reference URL\n Remarks\n\n\n\n\n Facebook\n https:\/\/developers.facebook.com\/docs\/audience-network\/guides\/ad-formats\/rewarded-video\/android\n \n\n\n Admob & Google Ad Manger\n https:\/\/support.google.com\/admob\/answer\/9603226?hl=zh-Hans&ref_topic=7382891\n \n\n\n Applovin\n -\n Please log in to the Applovin backend to configure the callback URL\n\n\n Mintegral\n http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown_v2\/index.html?file=sdk-m_sdk-android&lang=cn\n \n\n\n Mopub\n https:\/\/developers.mopub.com\/publishers\/android\/rewarded-video\/#passing-custom-data\n \n\n\n ironSource\n https:\/\/developers.ironsrc.com\/ironsource-mobile\/android\/advanced-settings\/#step-2\n \n\n\n UnityAds\n http:\/\/unityads.unity3d.com\/help\/resources\/s2s-redeem-callbacks\n \n\n\n Vungle\n https:\/\/support.vungle.com\/hc\/en-us\/articles\/204374244-Setting-Up-Rewarded-Ads#server-to-server-s2s-callbacks-0-0\n \n\n\n AdColony\n https:\/\/github.com\/AdColony\/AdColony-Android-SDK\/wiki\/Showing-Rewarded-Interstitial-Ads#server-side-rewards\n \n\n\n Pangle\n https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=4&docId=5de8d9b725b16b00113af0e5&osType=android#5d15f2\n \n\n\n AppNext\n https:\/\/developers.appnext.com\/docs\/appnext-android-rewarded-fullscreen#server-side-postback---rewarded-video\n \n\n\n Ogury\n https:\/\/ogury-ltd.gitbook.io\/android\/ad-formats\/opt-in-video-ad\n \n\n\n Huawei\n -\n Please log in to the Huawei backend to configure the callback URL\n\n\n Tencent Ads\n https:\/\/developers.adnet.qq.com\/doc\/android\/union\/union_reward_video\n Please log in to the Tencent Ads backend to configure the callback URL Supported from Taku SDK v5.7.8 and above\n\n\n Sigmob\n https:\/\/support.sigmob.com\/#\/%E5%B9%B3%E5%8F%B0%E6%93%8D%E4%BD%9C%E6%8C%87%E5%8D%97\/Sigmob%E5%8F%98%E7%8E%B0\/%E6%BF%80%E5%8A%B1%E8%A7%86%E9%A2%91%E6%9C%8D%E5%8A%A1%E7%AB%AF%E9%AA%8C%E8%AF%81\/\n Starting from v5.7.40, supports passing customData, which is sent to the developer as a JSON string via the developer-configured callback URL (Key is user_custom_data, Value is customData)\n\n\n Kuaishou\n https:\/\/static.yximgs.com\/udata\/pkg\/KS-Android-KSAdSDk\/doc\/4701b963d40a77bc0f45fd71d30b57da.pdf\n Supported from v5.7.25, both userId and customData must be passed before loading the ad\n\n\n Baidu\n https:\/\/union.baidu.com\/miniappblog\/2020\/12\/01\/newAndroidSDK\/\n \n\n\n\n2.2 iOS\n\n\n\n Ad Platform\n Reference URL\n Remarks\n\n\n\n\n Facebook\n https:\/\/developers.facebook.com\/docs\/audience-network\/guides\/ad-formats\/rewarded-video\/ios\n \n\n\n Admob & Google Ad Manger\n https:\/\/developers.google.com\/admob\/ios\/rewarded-video-ssv\n \n\n\n Applovin\n https:\/\/dash.applovin.com\/docs\/integration#iosRewardedVids\n \n\n\n Mintegral\n http:\/\/cdn-adn.rayjump.com\/cdn-adn\/v2\/markdown_v2\/index.html?file=sdk-m_sdk-ios&lang=cn\n \n\n\n ironSource\n https:\/\/developers.ironsrc.com\/ironsource-mobile\/ios\/advanced-settings-2\/#step-3\n \n\n\n Vungle\n https:\/\/support.vungle.com\/hc\/en-us\/articles\/204374244-Setting-Up-Rewarded-Ads#server-to-server-s2s-callbacks-0-0\n \n\n\n AdColony\n https:\/\/github.com\/AdColony\/AdColony-iOS-SDK\/wiki\/Showing-Rewarded-Interstitial-Ads#server-side-rewards\n \n\n\n Pangle\n https:\/\/www.pangle.cn\/union\/media\/union\/download\/detail?id=23&docId=5de8d72ab1afac00129330e6&osType=ios#620104\n \n\n\n AppNext\n https:\/\/developers.appnext.com\/docs\/appnext-ios-rewarded-fullscreen#server-side-postback---rewarded-video-ad\n \n\n\n Ogury\n https:\/\/ogury-ltd.gitbook.io\/ios\/ad-formats\/opt-in-video-ad\n \n\n\n Nend\n Click to View\n \n\n\n Sigmob\n https:\/\/support.sigmob.com\/#\/%E5%B9%B3%E5%8F%B0%E6%93%8D%E4%BD%9C%E6%8C%87%E5%8D%97\/Sigmob%E5%8F%98%E7%8E%B0\/%E6%BF%80%E5%8A%B1%E8%A7%86%E9%A2%91%E6%9C%8D%E5%8A%A1%E7%AB%AF%E9%AA%8C%E8%AF%81\/\n Starting from v5.7.41, supports passing customData, which is sent to the developer as a JSON string via the developer-configured callback URL (Key is user_custom_data, Value is customData)\n\n\n UnityAds\n https:\/\/unityads.unity3d.com\/help\/resources\/s2s-redeem-callbacks\n \n\n\n Tapjoy\n -\n Please log in to the Tapjoy backend to configure the callback URL\n\n\n Tencent Ads\n https:\/\/developers.adnet.qq.com\/doc\/ios\/union\/union_reward_video\n Please log in to the Tencent Ads backend to configure the callback URL Supported from Taku SDK v5.7.8 and above\n\n\n Kuaishou\n https:\/\/static.yximgs.com\/udata\/pkg\/KSAdSDKTarGz\/doc\/ksadsdk-iOS-readme-ad-3.3.9.pdf\n \n\n\n Baidu\n https:\/\/union.baidu.com\/miniappblog\/2020\/08\/11\/iOSSDK\/\n \n\n\n\n3. Taku Server-Side Reward Usage Instructions\n\nTaku SDK >= v5.7.56 can use Taku server-side reward callbacks.\nTaku SDK >= v5.7.78 and above supports returning impression-level data in Taku server-side reward callbacks (developers can add the {ilrd} parameter in the callback URL to retrieve the corresponding data).\n\n3.1 Server-Side Reward Usage Flow\n(1) Developers need to enable server-side reward on the Rewarded Video Ad Placement in the Taku backend and configure the callback URL.\n(2) Developers need to pass UserID (unique user ID) and UserCustomData (user-defined data) in code through the Taku SDK API. These parameters will ultimately be passed to the developer via the callback URL.\n(3) When a user finishes watching a Rewarded Video, the Taku platform will notify the developer through the configured callback URL, and the developer will decide and grant the reward.\n3.2 Developer Server-Side Reward Integration Guide\n(1) Developers need to enable server-side reward on the Rewarded Video Ad Placement in the Taku backend and configure the developer's server-side reward Callback URL, as shown below:\n\nExample of a developer's Callback URL:\nhttps:\/\/www.takuad.com\/onrewardedverify?user_id={user_id}&trans_id={trans_id}&reward_amount={reward_amount}&reward_name={reward_name}&placement_id={placement_id}&extra_data={extra_data}&network_firm_id={network_firm_id}&adsource_id={adsource_id}&scenario_id={scenario_id}&sign={sign}&ilrd={ilrd}\n\n(2) Taku will request the developer's Callback URL via GET method, appending the following parameters:\nuser_id={user_id}&trans_id={trans_id}&reward_amount={reward_amount}&reward_name={reward_name}&placement_id={placement_id}&extra_data={extra_data}&network_firm_id={network_firm_id}&adsource_id={adsource_id}&scenario_id={scenario_id}&sign={sign}&ilrd={ilrd}\n\n(3) The placeholders for the developer's custom callback URL information are as follows. Note:\n\nYou do not need to configure all placeholders; configure only those for the information you need.\nIf the signature mechanism is required (i.e., configured with sign={sign}), then all placeholders involved in the signing process (see below: sign Signature Rules) must be configured.\nIn addition to the custom configured information, the callback URL sent to the developer may sometimes include additional RMB-to-USD exchange rate information (e.g., exch_rate_c2u=0.1375), which can be ignored if not needed.\nWhen creating or editing a server-side reward Ad Placement in the developer backend, Taku will default to calling back the reward URL configured in the backend once. This is to immediately check whether the developer-configured URL is working properly. In this callback, the URL placeholders are not replaced, and an additional callback parameter is_test=1 is appended.\n\n\n\n\n Parameter\n Description\n Remarks\n\n\n\n\n {user_id}\n User ID\n Set by the developer via the Taku SDK API\n\n\n {extra_data}\n User business parameters\n Set by the developer via the Taku SDK API\n\n\n {trans_id}\n Trans ID generated by the Taku server, globally unique\n It is strongly recommended that developers verify whether a reward has already been issued for the trans_id on their server before granting the reward, to avoid issuing duplicate rewards for the same trans_id (corresponds to getShowId() in the client-side impression callback).\n\n\n {reward_name}\n Reward name\n Configured in the developer backend (supports configuration at Ad Placement or Ad Scene level)\n\n\n {reward_amount}\n Reward amount\n Configured in the developer backend (supports configuration at Ad Placement or Ad Scene level)\n\n\n {placement_id}\n Taku Ad Placement ID\n -\n\n\n {network_firm_id}\n Ad Platform ID in Taku Mediation\n [Special Note] 1). If you need to use server-side reward and also use Taku Adx, Direct Offer, or Cross Promotion: For third-party ad platforms, it is recommended to prioritize using the third-party ad platform's server-side reward callback. For Taku Adx, Direct Offer, and Cross Promotion, you can use Taku's server-side reward callback. 2). You can use the Network Firm ID to determine whether to accept only Taku's server-side reward callback: 1. Taku Adx Network Firm ID = 66 2. Taku Direct Offer Network Firm ID = 67 3. Taku Cross Promotion Network Firm ID = 35 View Taku Ad Platform ID List\n\n\n {adsource_id}\n Taku Ad Source ID\n -\n\n\n {scenario_id}\n Taku Ad Scene ID\n Set by the developer via the Taku SDK API\n\n\n {package_name}\n Developer app package name or Bundle ID\n Obtained by Taku SDK from the developer's app package name or Bundle ID\n\n\n {platform}\n System platform, Android or iOS\n Returned as the following enum: 1: Android, 2: iOS\n\n\n {ilrd}\n Impression-level data called back by Taku SDK. The data is a JSON string.\n Supported by Taku SDK v5.7.78 and above. Taku SDK provides impression-level data to developers when calling back the Rewarded Video OnReward event. Refer to specific data format Note: The ilrd parameter is only for behavioral data analysis reference and cannot be directly used as the basis for reward distribution.\n\n\n {sign}\n Signature information\n Refer to the signature rules description\n\n\n\n(4) sign Signature Rules Description\nWhen receiving Taku's server-side reward callback, developers can verify the callback parameters using the sign.\n\nTaku server generates the sign signature as follows (without ilrd):\n\nsign =MD5(\"trans_id=\"+trans_id+\"&placement_id=\"+placement_id+\"&adsource_id=\"+adsource_id+\"&reward_amount=\"+reward_amount+\"&reward_name=\"+reward_name+\"&sec_key=\"+sec_key)\n\n\n\nTaku server generates the sign signature as follows (with ilrd):\n\nIf the callback URL includes the {ilrd} parameter, the following sign signature rule must be used:\nsign =MD5(\"trans_id=\"+trans_id+\"&placement_id=\"+placement_id+\"&adsource_id=\"+adsource_id+\"&reward_amount=\"+reward_amount+\"&reward_name=\"+reward_name+\"&sec_key=\"+sec_key+\"&ilrd=\"+ilrd)\n\n\n(5) sign Signature Example\n\n\n\n Parameter\n Example\n\n\n\n\n trans_id\n xxxxxxxxxxxxxxxx\n\n\n placement_id\n b5b449fb3d89d7\n\n\n adsource_id\n 56789\n\n\n reward_amount\n 1\n\n\n reward_name\n coin\n\n\n sec_key\n cyvmwmzrqts7csphhexpqxqxxgljfisb\n\n\n ilrd\n abc\n\n\n\nsign signature example:\nsign=MD5(trans_id=xxxxxxxxxxxxxxxx&placement_id=b5b449fb3d89d7&adsource_id=56789&reward_amount=1&reward_name=coin&sec_key=cyvmwmzrqts7csphhexpqxqxxgljfisb&ilrd=abc)\n\n(6) After the developer's callback URL receives Taku's server-side reward callback, it must return a status code of 200 or 601 or 602 to the Taku server. After Taku receives a success or failure status code, it will not resend the server-side reward callback.\nSpecial note: The callback data may sometimes be very large (especially when ilrd is included). Developers should ensure that the GET callback URL length limit is removed, otherwise the developer's server may return a 414 error (for example, when using nginx, which has a default length limit).\n\n\n\n Return Status Code\n Description\n\n\n\n\n 200\n Success\n\n\n 601\n Signature verification failed\n\n\n 602\n Other failure\n\n\n\nIf there is no response within 2 seconds after the Taku server initiates the server-side reward callback, it is considered a timeout. After a timeout, Taku will retry sending the reward callback at intervals (e.g., 2 seconds, 4 seconds, 8 seconds, etc.). If Taku has retried a maximum of 5 times and still times out, it will no longer send the reward callback to the developer's callback URL.\n3.3 Per-Ad-Scene Server-Side Reward\nTo support developers granting different rewards in different Rewarded Video ad scenes, Taku allows developers to set different reward names and reward amounts for different ad scenes. The specific usage flow is as follows:\n(1) Enable the server-side reward callback for the Rewarded Video Ad Placement and receive the Taku callback's Ad Scene ID {scenario_id} in the callback URL.\n(2) Set the reward amount and reward name under the ad scene in the Taku backend, as shown below:\n\n(3) When receiving Taku's server-side reward callback, the developer grants different rewards based on the Ad Scene ID {scenario_id}.\n3.4 Quick Reuse of Server-Side Reward Rules\nTo reduce the time developers spend manually configuring server-side reward callback rules, Taku allows developers to quickly reuse server-side reward callback rules. The steps are as follows:\n(1) In the Advanced Features dropdown menu, go to Server-Side Callback.\n(2) Create a Callback Rule, edit it, and save the rule.\n\n(3) When creating or editing an Ad Placement, enable the server-side callback toggle and select the corresponding rule to quickly reuse that rule.\n\n4. Taku SDK Integration\n4.1 Taku Android SDK Code Sample\nMap localMap = new HashMap();\nlocalMap.put(ATAdConst.KEY.USER_ID, \"test_user_id\");\nlocalMap.put(ATAdConst.KEY.USER_CUSTOM_DATA, \"test_user_data\");\nmRewardVideoAd.setLocalExtra(localMap);\n\nmRewardVideoAd.load();\n\n4.2 Taku iOS SDK Code Sample\n[[ATAdManager sharedManager] loadADWithPlacementID:placementId extra:@{kATAdLoadingExtraMediaExtraKey:@\"test_user_data\", kATAdLoadingExtraUserIDKey:@\"test_user_id\"} delegate:self];\n\n4.3 Taku Unity SDK Code Sample\nDictionary jsonmap = new Dictionary();\n\njsonmap.Add(ATConst.USERID_KEY, \"test_user_id\");\njsonmap.Add(ATConst.USER_EXTRA_DATA, \"test_user_data\");\n\nATRewardedVideo.Instance.loadVideoAd(placementId, jsonmap);\n\n4.4 Taku Cocos2dx SDK Code Sample\ncocos2d::ValueMap extra;\nextra[ATCocosSdk::KEY_USER_ID] = \"test_user_id\";\nextra[ATCocosSdk::KEY_MEDIA_EXT] = \"test_user_data\";\nATCocosSdk::loadRewardedVideoAd(placementId, extra);\n\n4.5 Taku CocosCreator SDK Code Sample\nvar setting = {};\nsetting[ATRewardedVideoJSSDK.userIdKey] = \"test_user_id\";\nsetting[ATRewardedVideoJSSDK.userDataKey] = \"test_user_data\";\nATRewardedVideoJSSDK.loadRewardedVideo(placementId, setting);\n\n4.6 Taku ReactNative SDK Code Sample\nvar setting = {};\nsettings[ATRewardedVideoRNSDK.userIdKey] = \"test_user_id\";\nsettings[ATRewardedVideoRNSDK.userDataKey] = \"test_user_data\";\nATRewardedVideoRNSDK.loadAd(placementId, settings);\n\n5. ILRD Data Description\nNote: The ilrd parameter is only for behavioral data analysis reference and cannot be directly used as the basis for reward distribution. If you need to use impression revenue data for reward share calculations, please use impression revenue data. Reference documents: Impression Ad Source eCPM Encryption, Ad Impression Server-Side Callback (S2S)\n\n\n\n Variable\n Type\n Description\n\n\n\n\n network_firm_id\n int\n Gets the Ad Platform corresponding ID, used to distinguish ad platforms.\n\n\n adsource_id\n string\n Gets the Ad Source ID. You can query specific Network information by Ad Source ID in the developer backend or via Taku Open API.\n\n\n adsource_index\n int\n Gets the current Ad Source's position in the WaterFall (starting from 0).\n\n\n adsource_price\n dounble\n Gets the ECPM, the unit can be obtained via \"currency\".\n\n\n adsource_isheaderbidding\n int\n Whether it is a Header Bidding Ad Source, 1: Yes, 2: No.\n\n\n id\n string\n Gets the unique ID generated for each ad impression.\n\n\n publisher_revenue\n double\n Gets the impression revenue.\n\n\n currency\n string\n Gets the currency unit, e.g., \"USD\".\n\n\n country\n string\n Gets the country code, e.g., \"CN\".\n\n\n adunit_id\n string\n Gets the Taku Ad Placement ID.\n\n\n adunit_format\n string\n Gets the ad type, including: \"Native\", \"RewardedVideo\", \"Banner\", \"Interstitial\", \"Splash\".\n\n\n precision\n string\n Gets the ECPM precision. \"publisher_defined\": The eCPM defined by the developer for the Ad Source in the Taku backend (cross-promotion eCPM also falls under this type). \"estimated\": Taku's estimated eCPM (auto eCPM). \"exact\": Header Bidding real-time bidding eCPM.\n\n\n network_type\n string\n Gets the Network type. \"Network\": Third-party ad platform. \"Cross_Promotion\": Cross promotion. \"Adx\": Taku Adx.\n\n\n network_placement_id\n string\n Gets the Network's Ad Placement ID.\n\n\n ecpm_level\n int\n Gets the Ad Source's eCPM tier, Header Bidding Ad Sources default to 0.\n\n\n segment_id\n int\n Gets the Traffic Group ID.\n\n\n scenario_id\n string\n Gets the Ad Scene ID, only supported for Rewarded Video & Interstitial (starting from v5.7.20, Native & Banner are also supported).\n\n\n scenario_reward_name\n string\n Gets the Ad Scene reward name, only supported for Rewarded Video.\n\n\n scenario_reward_number\n int\n Gets the Ad Scene reward amount, only supported for Rewarded Video.\n\n\n sub_channel\n string\n Gets the sub-channel information.\n\n\n channel\n string\n Gets the channel information.\n\n\n custom_rule\n Dictionary\n Gets the JSON string of custom rules at the Placement + App level.\n\n\n user_load_extra_data\n string\n Gets the custom parameters passed during Load, corresponding to getLocalExtra().\n\n\n show_custom_ext\n show_custom_ext\n Gets the custom parameters passed during Show, corresponding to getShowCustomExt().\n\n\n\n6. FAQ\n(1) What is the difference between Taku's server-side reward callback and third-party platforms' callbacks?\n\nTaku's server-side reward callback provides reward callbacks that include data such as Taku ADX and third-party platform estimated eCPM.\n\nIf using Taku ADX, Cross Promotion, Direct Offer ads, etc., configuring the server-side reward callback in Taku will be more accurate. Third-party platform server-side reward callbacks will be more accurate when going through the respective third-party platform.\n\n\nTo ensure the accuracy of reward callbacks as much as possible, it is recommended to use client-side reward callbacks, third-party server-side reward callbacks, and Taku server-side reward callbacks simultaneously, and perform parameter consistency verification across all three callbacks.","is_draft":"0","editor_type":"2","file_path":"","add_time":"1782799893","update_time":"1782962845"},"pure_content":"1. Server-Side Reward Introduction\nServer-Side Reward (Server-to-Server): Allows developers to decide whether to grant rewards to users who watch Rewarded Video ads. When a user finishes watching a Re"}],"content":{"icon":"","desc":"","content_id":"844706","add_time":"1782799876","update_time":"1782799876","content":"","is_traffic_less":"0","file_type":""},"hot_list":[],"user_read_num":"0","is_auth":"0"},"msg":"Success","code":200}