@thinkingai/ae-cli 1.0.28 → 6.0.16-1

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/react-native/release-notes.md

@@ -0,0 +1,79 @@
+---
+code: rn_sdk_release_note
+name: "Release Notes"
+wikiToken: AFo8wnhUbi2qQRkTN4TcBCQhnQc
+parentWikiToken: E1F3wNsc3iW7dckzhH9cA2h2nIg
+updateTime: 1778726185000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=rn_sdk_release_note
+---
+
+## v3.2.1
+**Date: **05/14/2026
+**notes：**
+- Known issue fixes
+## v3.2.0
+**Date: **12/01/2025
+**notes：**
+- Upgrade the Android and iOS SDKs to the latest stable version, and upgrade third-party plugins to the latest version.
+- Intermediate layer adjustments, using TDAnalytics
+- Added page view and element click events
+- Known issue fixes
+## v3.1.0
+**Date: **09/01/2025
+**notes：**
+- Native and Webview are connected
+## v3.0.1
+**Date: **11/27/2023
+**notes：**
+- Upgrade Android SDK to 3.0.0
+## v3.0.0
+**Date: **11/08/2023
+**notes：**
+- Code specifications and comment specifications
+## v2.4.6
+**Date: **04/19/2023
+**notes：**
+- Optimize code
+- Upgrade iOS SDK to v2.8.3.2
+## v2.4.5
+**Date: **02/17/2023
+**notes：**
+- Optimize code
+## v2.4.4
+**Date: **02/13/2023
+**notes：**
+- Optimize code
+## v2.4.3
+**Date: **02/13/2023
+**notes：**
+- Optimize code
+## v2.4.2
+**Date: **02/10/2023
+**notes：**
+- Compatible with web
+## v2.4.1
+**Date: **02/08/2023
+**notes：**
+- Remove "react-native" version dependency
+## v2.4.0
+**Date: **01/30/2023
+**notes：**
+- Optimize third-party data integration
+## v2.3.0 
+**Date: **08/10/2022
+**notes：**
+- Reconstructs RN external interfaces
+- Supports dynamic public attributes
+## v2.2.0
+**Date: **05/26/2022
+**notes：**
+- Support three-party data access
+- Support data encryption 
+- Support userUniqAppend 
+- Optimized the interface for stopping or suspending data reporting
+- Support prefabricated attribute acquisition
+- Auto-tracking event support custom static public properties
+- Added interface for obtaining static public properties
+- Support obtaining distinct id
+- Support obtaining device id
+- Optimize the initialization mode

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/react-native.md

@@ -0,0 +1,137 @@
+---
+code: rn_sdk_support
+name: "React Native"
+wikiToken: E1F3wNsc3iW7dckzhH9cA2h2nIg
+parentWikiToken: JRIIwKqb5iVJMAkCwTic7H17ncg
+updateTime: 1778726153000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=rn_sdk_support
+---
+::: tip
+Before you begin, please read [<text color="purple" underline="true">Preparation before Data Ingestion</text>](https://thinkingdata.feishu.cn/wiki/OhD8we9iai6Xk5kM1QNc8ITRnQe)
+ :::
+**Latest version:** 3.2.1
+**Update time:** 05/14/2026
+**Resource download: **[**SDK**](https%3A%2F%2Fgithub.com%2FThinkingDataAnalytics%2Freact-native-sdk.git)
+## **1. ****SDK**** Integration**
+### **1.1 Automatic Integration**
+#### npm install the react-native-thinking-data module
+```json
+"dependencies": {    
+    "react-native-thinking-data": "3.2.1"
+}
+```
+
+## **2. Initialization**
+```javascript
+import TDAnalytics,{TDAutoTrackEventType} from "react-native-thinking-data";
+TDAnalytics.init({ appId: "xxx",serverUrl: "https://xxx"});
+```
+
+Instruction on parameters:
+- `APPID`: The APPID of your project, which can be found on the project management page of the TE.
+- `SERVER_URL`: 
+  - If you are using a SaaS version, please check the receiver URL on this page
+<image token="H0jHb0iMvok3Cmx034dcwZtHnYb" width="1674" height="1318" align="center"/>
+
+- If you use the private deployment version, you can customize the data tracking URL .
+<quote-container>
+Since Android 9.0+ restricts HTTP requests by default, please use HTTPS protocol only.
+</quote-container>
+
+## **3. Common Features**
+We suggested that you read [User Identification Rules](https://thinkingdata.feishu.cn/wiki/Pov9wECdsi2QQsk4NN9cEPsvnyc) before using common features; SDK would generate a random number that would be used as the distinct ID, and save the ID locally. Before the user logs in, the distinct ID would be used as the identification ID.   Note: The distinct ID would change after the user reinstalled the APP or used the APP with a new device.
+### **3.1 Login**
+When the users log in , `login` could be called to set the account ID of the user. TE would use the account ID as the identification ID, and this ID would be saved before `logout` is called. The previous account ID would be replaced if `login` has been called multiple times.
+```java
+TDAnalytics.login("TA")
+```
+
+<quote-container>
+**Login events wouldn't be uploaded in this method.**
+</quote-container>
+
+### 3.2 **Super Properties**
+Super Properties refer to properties that each event might have. You can call `setSuperProperties` to set Super Properties. It is recommended that you set Super Properties first before sending data. Some important properties (e.g., the membership class of users, source channels, etc.) should be set in each event. At this time, you can set these properties as Super Properties.
+```javascript
+TDAnalytics.setSuperProperties({
+    'channel': 'te',//string
+    'age': 1,//number
+    'isSuccess': true,//boolean
+    'birthday': new Date(),//time
+    'object': {
+      'key': 'value'
+    },//object
+    'object_arr': [
+      { 'key': 'value' }
+    ],//array object
+    'arr': ['value']//array
+})
+```
+
+Super Properties would be saved in local storage, and will not need to be called every time the App is opened. If the Super Properties set previously are uploaded after calling `setSuperProperties`, previous properties would be replaced. 
+- Key is the name of the property and refers to the string type. It must start with a character, and contain numbers, characters (insensitive to case, and upper cases would be transformed into lower cases by TE) and underscores "_", with a maximum length of 50 characters. 
+- Value, the value of the property, supports string, numbers, Boolean, time, object, array object, and array
+<quote-container>
+**The requirements for event properties and user properties are the same with that for super properties**
+</quote-container>
+
+### **3.3 Automatically Track Events**
+The following code is an example of install, active and inactive events. To get more information about the automatic tracking of SDK, please refer to [Detailed introduction of automatic tracking function](https://thinkingdata.feishu.cn/wiki/EVwUwiZdYi3jhEkcAhHcNxSrnkd)
+```javascript
+TDAnalytics.enableAutoTrack(TDAutoTrackEventType.APP_START | TDAutoTrackEventType.APP_END | TDAutoTrackEventType.APP_CRASH | TDAutoTrackEventType.APP_INSTALL)
+```
+
+### **3.4 Sending Events**
+You can call `track` to upload events. It is suggested that you set event properties based on the data tracking plan drafted previously. Here is an example of a user buying an item:
+```javascript
+TDAnalytics.track({
+    eventName:"product_buy",
+    properties:{
+        product_name:'productName'
+    }
+})
+```
+
+The event name is string type. It could only start with a character and could contain figures, characters, and an underline "_", with a maximum length of 50 characters.
+### **3.5 User Properties**
+You can set general user properties by calling `user_set` API. The original properties would be replaced by the properties uploaded via this api. The data type of newly-created user properties must be the same as the uploaded properties. User name setting is taken as the example here: 
+```javascript
+//the username now is TA
+TDAnalytics.userSet({ username:"TA"})
+//the username now is TE
+TDAnalytics.userSet({ username:"TE"})
+```
+
+## **4. Best Practice**
+The following sample code covers all the above-mentioned operations. It is recommended that the SDK be used in the following steps:
+```javascript
+import TDAnalytics,{TDAutoTrackEventType} from "react-native-thinking-data";
+if (Authorized Privacy policy)
+{
+   //SDK init
+   TDAnalytics.init({appId: "xxx",serverUrl: "https://xxx",});
+   //if the user has logged in, the account ID of the user could be set as the unique identifier 
+   TDAnalytics.login("TA")
+   //After setting super properties, each event would have super properties
+   TDAnalytics.setSuperProperties({
+     'channel': 'ta',//string
+     'age': 1,//number
+     'isSuccess': true,//boolean
+     'birthday': new Date(),//time
+     'object': {'key': 'value'},//object
+     'object_arr': [{ 'key': 'value'}],//array object
+    'arr': ['value']//array
+    })
+   //Enable auto-tracking
+   TDAnalytics.enableAutoTrack(TDAutoTrackEventType.APP_START | TDAutoTrackEventType.APP_END | TDAutoTrackEventType.APP_CRASH | TDAutoTrackEventType.APP_INSTALL)
+   //upload events
+    TDAnalytics.track({
+        eventName:"product_buy",
+        properties:{
+          'product_name':'tv'
+        }
+    }) 
+   //Set user properties
+   TDAnalytics.userSet({ username:"TE"})
+}
+```

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/release-notes.md

@@ -0,0 +1,24 @@
+---
+code: uniapp_sdk_release_note
+name: "Release Notes"
+wikiToken: AVZBwxwHEiRgw9kEfQLcIyDEn1k
+parentWikiToken: N0e7w3csPiU7MkkMCO9c7PXVnSb
+updateTime: 1774249177000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_release_note
+---
+
+## v3.0.0
+**Date**: 11/10/2023  [<text color="blue">Download</text>](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2FUniapp%2Fta_uniapp_sdk_v3.0.0.zip)
+**Notes**：
+- Code specifications and comment specifications
+## [<text color="blue">#</text>](https%3A%2F%2Fdocs.thinkingdata.cn%2Fta-manual%2Flatest%2Finstallation%2Finstallation_menu%2Fclient_sdk%2Fapp_third_support%2Funiapp_sdk_installation%2Funiapp_sdk_release_note.html%23v1-0-1)v1.0.1
+**Date**: 04/21/2023  [<text color="blue">Download</text>](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2FUniapp%2Fta_uniapp_sdk_v1.0.1.zip)
+**Notes**：
+- Support initialization delay
+- Code specifications
+## v1.0.0
+**Date:** 11/15/2022
+**Notes:**
+- Supports the setting of visitor ID and user account
+- Supports event and user attribute reporting
+- Supports the reporting of first, update, and overwrite event

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/uniapp-advanced/automatically-track-events.md

@@ -0,0 +1,54 @@
+---
+code: uniapp_sdk_autotrack
+name: "Automatically Track Events"
+wikiToken: F2MmwPLE7iVwHfktWXFc3htdnIg
+parentWikiToken: DM7kwtiBMiCpWCkk7icczidxn7c
+updateTime: 1774249169000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_autotrack
+---
+
+We provide auto-tracking  function. You only need to enable the events you need to automatically collect in config when creating the instance. SDK will automatically collect some behaviors of the mini program.
+automated data collection is now supported:
+1. mini program initialization,this is triggered only once by a user
+2. mini program active， including startup and background back to  foreground
+3. mini program inactive，and record the time of this access (start to the background)
+the methods for collecting each type of data are described in detail next
+## **1. Enable Auto-Tracking**
+in config, the elements in the autoTrack parameter represent the switch for each auto collection event, set to true to enable auto collection:
+```javascript
+var config = {
+  appid: "YOU-APP-ID",
+  server_url: "https://youserverurl.com",
+  autoTrack: {
+    appLaunch: true, // auto-tracking ta_mp_launch
+    appShow: true, // auto-tracking ta_mp_show
+    appHide: true, // auto-tracking ta_mp_hide
+    pageShow: true, // auto-tracking ta_mp_view
+    pageShare: true, // auto-tracking ta_mp_share
+  }
+};
+```
+
+- `appLaunch`：auto tracking mini-program launch
+- `appShow`：auto tracking mini-program active and resume mini-program from the background
+- `appHide`：auto tracking mini-program enter in background
+## **2.Detailed Introduction**
+### 2.1 mini-program initialization
+mini-program initialization will be triggered when the mini-program is opened for the first time or when the user kills the process and starts it again. It will only be triggered once in the life cycle of the process. The detailed event is described as follows:
+- event name:ta_mp_launch
+- auto-tracking attributes: `#scene`, the scene value is taken from the scene value provided by wechat
+Through the mini-program initialization event, you can calculate the daily user usage and per-capita user usage, including viewing the usage of users with different scenario values grouped by scenario values.
+### 2.2 mini-program active
+mini-program active will be triggered when mini-program is started, or when mini-program is called back to the foreground from the background. The detailed event is described as follows:
+- event name:ta_mp_show
+- auto-tracking attributes：
+- `#scene`，the scene value is taken from the scene value provided by wechat
+- `#url_path`，page path, mini-program to start the displayed page path
+the startup of mini-program is not suitable for direct analysis due to the influence of the call out before and after (many), but it can be used in the behavior path to identify a user's use, can be used as the initial behavior of the user behavior path
+### 2.3 mini-program inactive
+mini-program  inactive will be triggered when the mini-program is called into the background, and record the duration of this use,The detailed event is described as follows:
+- event name:ta_mp_hide
+- auto-tracking attributes： 
+  - `#scene`，the scene value is taken from the scene value provided by wechat
+  - `#duration`，The value is a numeric value, indicating the duration from this start (ta_mp_show) to hiding
+mini-program inactive events record the usage duration (in seconds), so you can directly calculate the total user usage duration and per capita duration, or you can divide by the initialization times to calculate the single usage duration.

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/uniapp-advanced/debugging-and-logging.md

@@ -0,0 +1,53 @@
+---
+code: uniapp_sdk_debug
+name: "Debugging and Logging"
+wikiToken: CnOtw65kJiO0q8k3Y6qcCVF8nwb
+parentWikiToken: DM7kwtiBMiCpWCkk7icczidxn7c
+updateTime: 1774251990000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_debug
+---
+
+During the process of SDK access, you can perform real-time debugging by checking SDK's logs in the IDE console or using the Debug function of TE.
+## **1. Logging**
+```javascript
+var config = {
+    appId: "xxx",
+    serverUrl: "xxx",
+    enableLog:true
+};
+```
+
+
+After this function is enabled, the reported data will be printed on the browser console.
+
+
+## **2. Debugging**
+You need to follow the following two steps to enable the Debug mode:
+1. Enable the debug mode at the client side
+The sample code for enabling the Debug mode on the client side is as follows:
+```java
+/*
+Set the operation mode as the Debug mode
+NORMAL mode: the data would be saved in caches and reported according to relevant cache policies under the NORMAL mode by default. It is recommended to use the mode in an online environment
+Debug mode: report data item by item. If problems occur, the user would be notified with logs and anomalies. It is recommended to use the Debug mode in an online environment
+DebugOnly mode: data would be verified without being stored; it is not recommended to use the DebugOnly mode in an online environment
+ */
+var config = {
+  appid: "YOUR_APPID",
+  server_url: "YOUR_SERVER_URL",
+  debugMode: "debug"
+};
+TDAnalytics.init(config);
+```
+
+2. Add Device
+To avoid launching the Debug mode in the production environment, it is required that only specified device can enable Debug mode. The Debug mode can only be enabled for devices whose IDs have been configured in the "Debug data"sector on the "tracking management" page of the TE when the client side has enabled the Debug mode.
+
+
+Device ID could be obtained by the following three means:
+- #Device_id property in the event data of the TE platform
+- Client-side log: DeviceID would be printed after SDK is initialized
+Call [obtain device ID](https://thinkingdata.feishu.cn/wiki/DM7kwtiBMiCpWCkk7icczidxn7c) through the instance interface
+
+
+The Debug mode may undermine the data tracking quality and stability of the App. It could only be used for data verification at the integration stage, and should not be used in the online environment.

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/uniapp-advanced/multi-instance.md

@@ -0,0 +1,42 @@
+---
+code: uniapp_sdk_multi_appid
+name: "Multi-Instance"
+wikiToken: UwidwC00DiRr0pkIdqDccoCOnwh
+parentWikiToken: DM7kwtiBMiCpWCkk7icczidxn7c
+updateTime: 1774249174000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_multi_appid
+---
+
+The multi-APPID feature could create multiple SDK instances to perform data tracking based on their own APPID. That is, you can report data to multiple APPIDs. 
+Multiple instances share preset device-related attributes (including device ids). Other attributes are not shared:
+- `#distinct_id` distinct ID
+- `#account_id` account ID
+- super propert、Dynamic public property
+- `timeEvent` related event
+You can report data to another project by creating a child instance, or to another set of user ids.
+```javascript
+var config_1 = {
+  appId: "app-id-1", 
+  serverUrl: "https://youserverurl.1.com"
+};
+TDAnalytics.init(config_1);
+
+var config_2 = {
+  appId: "app-id-2", 
+  serverUrl: "https://youserverurl.2.com"
+};
+TDAnalytics.init(config_2);
+
+//Report events to app-id-1
+TDAnalytics.track({
+    eventName: 'event_from_appid_1'
+});
+//Report events to app-id-1
+TDAnalytics.track({
+    eventName: 'event_from_appid_1'
+}, 'app-id-1');
+//Report events to app-id-2
+TDAnalytics.track({
+    eventName: 'event_from_appid_2'
+}, 'app-id-2');
+```

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/uniapp-advanced/preset-properties.md

@@ -0,0 +1,119 @@
+---
+code: uniapp_sdk_properties
+name: "Preset Properties"
+wikiToken: A0F9wOoF7iGC3mk9Lg8cu3FRnKg
+parentWikiToken: DM7kwtiBMiCpWCkk7icczidxn7c
+updateTime: 1774249172000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_properties
+---
+
+## **1. Preset Properties of All Events**
+The following present properties are properties that all events in uni-app SDK (including auto-tracking events) would have.
+<sheet token="X0QPs90lBhtKBqtrrZ0cZ604nVg_DYl05h"/>
+
+## **2. Preset Properties of Auto-tracking Event**
+The following preset properties are the properties set specially for each auto-tracking event
+- Preset properties of  mini porgram active(ta_mp_show)
+
+<lark-table rows="2" cols="4" column-widths="243,171,130,275">
+
+  <lark-tr>
+    <lark-td>
+      **Property name **
+    </lark-td>
+    <lark-td>
+      **Display name **
+    </lark-td>
+    <lark-td>
+      **Property type**  {align="center"}
+    </lark-td>
+    <lark-td>
+      **Instruction**
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      #url_path
+    </lark-td>
+    <lark-td>
+      page path
+    </lark-td>
+    <lark-td>
+      Text {align="center"}
+    </lark-td>
+    <lark-td>
+      The mini program starts the path to the page being displayed
+    </lark-td>
+  </lark-tr>
+</lark-table>
+
+- Preset properties of  mini porgram inactive(ta_mp_hide)
+
+<lark-table rows="2" cols="4" column-widths="243,174,130,268">
+
+  <lark-tr>
+    <lark-td>
+      **Property name **
+    </lark-td>
+    <lark-td>
+      **Display name **
+    </lark-td>
+    <lark-td>
+      **Property type ** {align="center"}
+    </lark-td>
+    <lark-td>
+      **Instruction**
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      #duration
+    </lark-td>
+    <lark-td>
+      event duration
+    </lark-td>
+    <lark-td>
+      Numeric value  {align="center"}
+    </lark-td>
+    <lark-td>
+      Indicates the duration between the start of ta_mp_show and the hiding of ta_mp_hide, in seconds
+    </lark-td>
+  </lark-tr>
+</lark-table>
+
+## 3.**Obtain Preset Properties**
+ You can call `getPresetProperties()` to obtain preset properties. 
+When some preset properties of the App side is required for the server-side data tracking, this method can be applied to obtain the preset properties of the App side and then send them to the server. 
+```javascript
+//obtain property objects
+var presetProperties=TDAnalytics.getPresetProperties();
+//generate event preset properties
+var properties=presetProperties.toEventPresetProperties();
+/*
+      {
+         "#device_model":"iPhone 5",
+         "#device_id":"3204487163-1624513721217",
+         "#screen_width":320,
+         "#screen_height":568,
+         "#os":"iOS",
+         "#os_version":"10.0.1",
+         "#network_type":"wifi",
+         "#zone_offset":8,
+         "#manufacturer":"Apple"
+       }
+ */
+//obtain a certain preset properties
+var os=presetProperties.os;//os type
+var osVersion=presetProperties.osVersion;//system version number
+var networkType=presetProperties.networkType;//network type
+var manufacture=presetProperties.manufacture;//mobile phone manufacturer, e.g., HuaWei
+var deviceModel=presetProperties.deviceModel; //device model
+var screenWidth=presetProperties.screenWidth; //screen width
+var screenHeight=presetProperties.screenHeight; //screen height
+var deviceId=presetProperties.deviceId;//unique identifier of device
+var zoneOffset=presetProperties.zoneOffset;////timezone offset value
+```
+
+<quote-container>
+IP and national city information are parsed and generated by the server. The client side shall not provide the interface to obtain such properties
+</quote-container>

package/wiki/te-docs/raw/data-ingestion-guide/client-sdk/cross-platform/uni-app/uniapp-advanced/support-native.md

@@ -0,0 +1,81 @@
+---
+code: uniapp_sdk_native
+name: "Support Native"
+wikiToken: OcNWwiFFPiRBP6kivKicaRgEnKh
+parentWikiToken: DM7kwtiBMiCpWCkk7icczidxn7c
+updateTime: 1774249176000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=uniapp_sdk_native
+---
+
+## 1. Support  iOS Native 
+### 1.1 Building an iOS Project
+- Create an iOS project
+- Open HBuilderX- Publish - Generate App package resources
+- Copy the locally packaged App resources to the Pandora -> apps path in the project directory
+### **1.2 Configuring the ****iOS**** Project**
+- Add iOS project dependency files
+Install the SDK using CocoaPods
+Create and edit Podfile content (edit directly if you already have it) :
+Create a Podfile, project (.xcodeproj) file in the same directory as the command line:
+```shell
+pod init
+```
+
+Edit Podfile as follows:
+```javascript
+pod 'TAGameEngine'
+```
+
+Running the Installation Command
+```javascript
+pod install
+```
+
+## 2.Support Android Native
+### 1.1 Building an Android Project
+- Create an Android project
+- Open HBuilderX- Publish - Generate App package resources
+- Copy app resources to project assets->apps
+### **2.2 Configuring the Android Project**
+- Add the following configuration dependencies to the build.gradle file at the Project
+```plaintext
+buildscript {
+    repositories {
+        jcenter()
+        mavenCentral()
+    }
+}
+```
+
+-  Add the dependencies to the build.gradle file in the Module project directory
+```plaintext
+implementation 'cn.thinkingdata.android:TAGameEngine:1.2.0'
+implementation 'cn.thinkingdata.android:ThinkingAnalyticsSDK:3.0.0.1
+```
+
+## 3.Enabling Native Support
+When initializing the SDK, set enableNative: true in config to enableNative support.
+```go
+
+var config = {
+  appId: "YOUR_APPID", 
+  serverUrl: "YOUR_SERVER_URL", 
+  enableNative: true, // enable native support
+  autoTrack: {
+    appLaunch: true, // auto-tracking ta_mp_launch
+    appShow: true, // auto-tracking ta_mp_show
+    appHide: true, // auto-tracking ta_mp_hide
+    appInstall:true,// auto-tracking ta_app_install(only for native)
+    appCrash: true, // auto-tracking ta_app_crash(only for native)
+  }
+};
+
+// init
+TDAnalytics.init(config);
+TDAnalytics.track({
+    eventName: "product_buy",
+    properties: {
+        product_name: "tv"
+    }
+ });
+```