Advanced guide

Last updated 10/03/2026

1. Initialization parameters

The TDStrategySettings configuration passed in during initialization is described below

1.1 TDStrategySettings

Property name	Type	Description
appId	String	app id of the project created in the AE backend
serverUrl	String	server url of the project created in the AE backend
mode	TDStrategyMode	SDK running mode

2. Set client parameters

When you create a client-triggered task, you can fill in Client-side Conditions. For configuration details, see Create client-triggered tasks

The parameters available in Client-side Conditions come from the environment parameters that the client collects automatically and the client parameters that you set through the TDRemoteConfig SDK. After you SET custom client parameters through the APIs provided by the TDRemoteConfig SDK, you can add them to the Client Parameters module in the AE Engage settings and use them in operation tasks.

Note: The names and types of the parameters you SET on the client must match the client parameters configured in the AE Engage backend.

Add client parameters

TDRemoteConfig.addClientParams({
  "key":"value"
});

Delete client parameters

TDRemoteConfig.removeClientParam("key")

Get client parameters

//Get all client parameters
TDRemoteConfig.getClientParams();

//Get a single client parameter
TDRemoteConfig.getClientParamValueForKey("key");

Client parameters with accumulated values

TDRemoteConfig.accumulateNum("key", 1);

3. Customize fetch timing

3.1 Automatic fetching

The SDK automatically fetches remote configuration data in the following scenarios

• App cold start
• App foreground/background switch, more than 6 hours after the previous one
• The ThinkingSDK account system changes, for example, on login or logout

3.2 Manual fetching

Call the SDK method manually to fetch remote configuration at any time

TDStrategy.fetch();

This API has internal rate limiting. Avoid fetching too frequently.

4. Touch funnel events

When you create a client-triggered channel, you can enable the touch funnel settings. For configuration details, see Channel Settings

After you enable the touch funnel, you can configure the event names associated with the funnel steps. You can then view the conversion data of the configured steps on the data details page of operation tasks that use this channel.

Events selected for Delivered and Clicked must meet the following requirements:

• The event must carry Engage-specific parameters. You can get these parameters from the opsProperties property of the TDStrategyResult object in the push content, and report them as follows:

TDStrategy.setTriggerListener((tdStrategyResult) {
  TDAnalytics.track("ops_click",properties:tdStrategyResult["opsProperties"] );
});

5. Send Test

To quickly verify the availability of a channel and the validity of a task, the SDK supports a test mode.

//All three SDKs must use DEBUG mode at the same time
TDConfig config = TDConfig();
config.appId = "appId";
config.serverUrl = "serverUrl";
config.setMode(TDMode.DEBUG);
TDAnalytics.initWithConfig(config);

TDRemoteConfigSettings settings = TDRemoteConfigSettings();
settings.appId = "appId";
settings.serverUrl = "serverUrl";
settings.mode = TDRemoteConfigMode.DEBUG;
TDRemoteConfig.initWithConfig(settings);

TDStrategySettings strategySettings = TDStrategySettings();
strategySettings.appId = "appId";
strategySettings.serverUrl = "serverUrl";
strategySettings.mode = TDStrategyMode.DEBUG;
TDStrategy.initWithConfig(strategySettings);

After you enable debug mode on the client, the client fetches test tasks every 5s. In the AE Engage module, you can create channel tests or task tests. While a task is waiting to be triggered, you can watch the progress nodes on the frontend page.

Related documentation: Send Test for tasks, Send Test for channels

Send tests for client-triggered tasks require test devices. You can select or add test devices in the test device list