SDK Preset Strategy

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.

Taku SDK supports all ad types using SDK Preset Strategy: Splash, Rewarded Video, Interstitial, Native, and Banner.

1. Introduction

Taku 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.

Notes:

1. Preloading SDK strategy locally in the app requires updating to Taku SDK v6.1.78 or above.

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.

2. Creating a Traffic Group for SDK Preset Strategy

Using SDK Preset Strategy requires creating a specific traffic group. The process is as follows:

(1) On the Mediation Management page, add a traffic group and select SDK Built-in Strategy as the traffic group rule.

(2) The SDK Preset Strategy rule in a traffic group cannot be used simultaneously with other rules.

(3) SDK Preset Strategy traffic group's Ad Placement strategy is only for export and preloading into your app.

(4) If you modify the SDK Preset Strategy, you need to re-export and preload it into your app.

(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.

3. Configuring SDK Preset Strategy

After 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.

4. Exporting SDK Preset Strategy

(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.

(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)

(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.

(4) After successfully exporting the SDK Preset Strategy, Taku generates a json file named after the Ad Placement ID.

5. Importing SDK Preset Strategy into the App

1. 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.
2. Refer to the Taku SDK integration instructions below.

5.1 Android Integration Instructions

(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.

(2) Place the json file exported from the backend into the newly created directory src/main/assets/localStrategy.

(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:

// Called in Application#onCreate()
public class DemoApplication extends Application {
      @Override
    public void onCreate() {
        super.onCreate();
             //...
          ATSDK.setLocalStrategyAssetPath(this, "localStrategy");
          //...
    }
}

5.2 iOS Integration Instructions

(1) Import the json file exported from the backend into the project.

(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:

// Pass the Bundle where the json file was imported into the project. This example uses mainBundle
[[ATAPI sharedInstance] setPresetPlacementConfigPathBundle:[NSBundle mainBundle]];

6. Viewing SDK Preset Strategy Data

(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.

(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.

(3) After enabling A/B Test, the original SDK Preset Strategy traffic group's data can be viewed under Ungrouped.

7. FAQ

(1) How long after completing SDK Preset Strategy configuration can I export?

Answer: 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.

(2) Do I need to re-import the Taku SDK Preset Strategy file every time I release an app update?

Answer: It is recommended to re-import the Taku SDK Preset Strategy file in the following situations:

(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).

(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.

(3) What is the impact if the new app version updates Taku SDK but does not update the old SDK Preset Strategy file?

Answer: 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.

Note: Older versions of Taku SDK cannot use newer versions of the SDK Preset Strategy file.

(4) How to improve first-launch Splash loading efficiency?

For v6.1.78 and above, refer to the following optimization suggestions:

1. Add 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).

2. Use SDK Preset Strategy for the Splash Ad Placement during app integration.