@thinkingai/ae-cli 1.0.28 → 6.0.16-1

package/wiki/te-docs/raw/preparations-before-data-ingestion.md

@@ -0,0 +1,203 @@
+---
+code: pre_installation_menu
+name: "Preparations before Data Ingestion"
+wikiToken: OhD8we9iai6Xk5kM1QNc8ITRnQe
+parentWikiToken: Hx0SwfT0aiwGRekQp2ocJ7okn0g
+updateTime: 1776412189000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=pre_installation_menu
+---
+
+::: tip
+The section of [<text underline="true">Basic knowledge</text>](https://thinkingdata.feishu.cn/docx/PCFEdBbNOo306LxIghpc7IfinHf) offers AE data rules that must be understood before data ingestion.
+The section of [<text underline="true">Information required data ingestion</text>](https://thinkingdata.feishu.cn/docx/PCFEdBbNOo306LxIghpc7IfinHf) has listed the system parameters that should be configured before data ingestion. 
+:::
+The AE (AgenticEngine) system provides a full-end data ingestion scheme. 
+Generally speaking, one has to complete three steps before accessing AE: firstly, sorting out the data tracking scheme based on service requirements. Analysts of Thinking data would help you finish the task; secondly, the R&D staff should complete data ingestion according to the data tracking scheme; finally, the correctness of data ingestion should be verified. The data ingestion procedure is shown in the following figure:
+<image token="CIwHbD3iXo0vpqxVaa3ctkM3nZg" width="1198" height="240" align="center"/>
+
+It is important to understand the basic knowledge about the AE system before data ingestion. This document would offer an overall introduction to the knowledge related to data ingestion. Meanwhile, it would also specify how to obtain help when you want to gain more information. 
+This document is targeted at all colleagues who participated in data ingestion, including business personnel, R&D staff, testing personnel, etc.
+## **I. Overview**
+AE provides a full-end data ingestion scheme, introducing the following major ingestion methods:
+- [Client SDK](https://thinkingdata.feishu.cn/wiki/KaFCwNeV3iRxjNkpT3QcDMg3n5V): able to track device information and user behavior information having no communication with the server, which is easy to use 
+- [Server SDK](https://thinkingdata.feishu.cn/wiki/IKVPwn4NfiIhijk5EcAcMf6pn7e): more accurate content tracking; applicable to core service data tracking
+- [Data import tool](https://thinkingdata.feishu.cn/wiki/S9D7wPqKDiC6zhkvv2dc6MgonCg): used for importing historical data in general situations; combining the server-side SDK with LogBus is also a frequently used server-side data tracking scheme
+For general apps and Web development, we provide:
+- [<text underline="true">React Native SDK quick start guide</text>](https://thinkingdata.feishu.cn/wiki/E1F3wNsc3iW7dckzhH9cA2h2nIg)
+- [<text underline="true">Flutter SDK quick start guide</text>](https://thinkingdata.feishu.cn/wiki/OzW1wBUwbiX7D5k8ZaSc6Uy0ndh)
+- Original SDK: [<text underline="true">Android SDK</text>](https://thinkingdata.feishu.cn/wiki/Sis2weaL2iJOOWklkX1cZAtcnVc), [<text underline="true">iOS SDK</text>](https://thinkingdata.feishu.cn/wiki/Wxc7wQj3FitXYVkTuW5cAAtPnCc)
+- Third-party framework: [<text underline="true">Flutter</text>](https://thinkingdata.feishu.cn/wiki/OzW1wBUwbiX7D5k8ZaSc6Uy0ndh), [<text underline="true">Reactive Native</text>](https://thinkingdata.feishu.cn/wiki/E1F3wNsc3iW7dckzhH9cA2h2nIg)
+- H5 development:<text color="purple" underline="true"> </text>[<text color="purple" underline="true">JavaScript SDK</text>](https://thinkingdata.feishu.cn/wiki/HwzHwHeb5iFceqk6Eylcd03UnMh), [<text underline="true">H5 and original SDK connection</text>](https://thinkingdata.feishu.cn/wiki/FOFZwGHJii1Jm2ke88DcFrrJnUb)
+For the development of mini-games, we provide:
+- Support from mainstream game engines: [<text underline="true">Cocos Creator</text>](https://thinkingdata.feishu.cn/wiki/AL6VwEXmiiAgK7kXq97c8YXNnLc)
+For the development of mobile games, we provide:
+- [<text underline="true">Unity SDK</text>](https://thinkingdata.feishu.cn/wiki/NaFYwOKI1iN5mgkTPQwcZY0tnRg)
+- [<text underline="true">Unreal 4 SDK</text>](https://thinkingdata.feishu.cn/wiki/Tjh7wx7FYinevfkG0mwcLxsSnea)
+As for the service-side tracking scheme, we recommend the scheme of [<text underline="true">Server SDK</text>](https://thinkingdata.feishu.cn/wiki/IKVPwn4NfiIhijk5EcAcMf6pn7e)<text underline="true"> </text>+ [<text underline="true">Logbus</text>](https://thinkingdata.feishu.cn/wiki/SlE6wOEK3isQvukzEbnc5V0inNa). This scheme has robust performance in terms of the stability, timeliness and efficiency of data importing.
+If you need to import certain historical heterogeneous data or supplement some data into the AE system, you can import the data with [<text underline="true">DataX</text>](https://thinkingdata.feishu.cn/wiki/Taa9wJpfHiBIgckwrQtcGauRnTh). Different from the Logbus scheme, DataX is not a resident service. The timeliness of data could not be ensured for the generation of new data could not be monitored and new data could not be imported timely. The advantage of DataX is its ability to import the heterogeneous data of multiple data sources with simple operations.
+If you have used Filebeat and Logstash to collect logs and want to import log data into the AE system, you can use [Filebeat +Logstash](https://thinkingdata.feishu.cn/wiki/PX2xwuYOwiaSnOkWUjrcNm0lnGf) scheme. 
+You can choose the scheme that is suitable for the technical structure and service requirements of your products according to the status quo of your business when designing the data tracking scheme. If you have any questions about the tracking scheme, please consult our analysts or technical support colleague in the support group chat.
+## **II. Basic Knowledge**
+### **2.1 ****AE data model**
+Before data ingestion, we need to understand what is the data in AE. 
+Indeed, designing data tracking scheme is a process of determining which user behavior event should be collected according to the objectives of service analysis. For example, if we need to analyze the status quo of user recharging, we need to track the payment behavior data of users. User behavior data can be divided into who, when, where, how and what, as shown in the following figure:
+<image token="CY2vbnMs1ohzwKxPBmjcbfz8nAh" width="1510" height="702" align="center"/>
+
+User behavior data could be organized as user-related data and event-related data in AE and stored in the user table and list table respectively. User data could mainly be used to describe the user state and properties that would not change frequently. Event data is used to describe information related to specific behavior events.
+In the data tracking scheme, you should determine when should user data tracking be triggered and when should event tracking be triggered. 
+All of our data ingestion guidance would introduce the method for tracking event data and user data respectively.
+### **2.2 User identification rules**
+It should be clarified to which user each piece of user data or event data belongs. In scenarios without an account system, the ID related to the device could be used as the unique identifier of the user. However, in scenarios with an account system, a user may generate data on multiple devices. Therefore, the data in multiple terminals should be included in the analysis, which does not apply to the unique ID related to devices.
+To handle the above two scenarios, two user Ids should be used in the data ingestion process of identifier users:
+- Distinct ID (#distinct_id): the client side would generate a random distinct ID by default to identify users. It also provides an interface to read and modify default distinct IDs. 
+- Account ID (#account_id): when the client logs in, the account ID could be set. The data in multiple devices could be correlated through the account ID.
+Each piece of data must contain a distinct ID or account ID. A distinct ID could be generated by the client-side SDK by default. After you call the `login` interface to set the account ID, all the data would carry distinct ID and account ID simultaneously during the data tracking process. You need to upload at least one of account ID and distinct ID when tracking data through the server. 
+In the AE background, the unique ID of a user should be identified as the AE user ID (#user_id field). When receiving the data, we will create a new user according to specific [<text underline="true">User identification Rules</text>](https://thinkingdata.feishu.cn/wiki/Pov9wECdsi2QQsk4NN9cEPsvnyc), or bind the data with an existing user. 
+[<text underline="true">User identification rules</text>](https://thinkingdata.feishu.cn/wiki/Pov9wECdsi2QQsk4NN9cEPsvnyc) are very important. If the user ID is not set correctly, the data might be bound with the wrong user, which would undermine the analysis effect. Please read the rules carefully before data ingestion and specify the user identification scheme in the data tracking scheme.
+### **2.3 Data format**
+No matter which method is applied for data ingestion, the unified data format, and the same data restrictions should be used to send data to the receiving end. Chapter [<text underline="true">data rules</text>](https://thinkingdata.feishu.cn/wiki/L5rSwhPp8iycp4kWAnGc35gvn3f) offer a detailed description of the data format and corresponding data restrictions. 
+When connecting data through SDK, you only need to call the corresponding interface. SDK would process the data with the required format before reporting the data. If you connect data through data import tools or [<text underline="true">Restful API</text>](https://thinkingdata.feishu.cn/wiki/Jsp1w2ewJiXA2wkBvU8ckXxhn6g)<text underline="true">,</text> you need to collate the data format according to the description in [<text underline="true">Data Rules</text>](https://thinkingdata.feishu.cn/wiki/L5rSwhPp8iycp4kWAnGc35gvn3f) before reporting the data. 
+Special attention should be paid to the naming rules and data type to ensure that the data format conforms to relevant requirements.
+- Naming rules: the event name and property name both could only contain letters, figures, and underline _, starting with letters with a maximum length of 50 characters 
+<quote-container>
+Note: The property name is insensitive to the upper case and lower case, while the event name is sensitive to the upper and lower case.
+</quote-container>
+
+- Data type of property value
+
+<lark-table rows="8" cols="4" column-widths="155,173,219,187">
+
+  <lark-tr>
+    <lark-td>
+      ** ****AE data type**** **
+    </lark-td>
+    <lark-td>
+      ** Sample value **
+    </lark-td>
+    <lark-td>
+      ** Instructions on values **
+    </lark-td>
+    <lark-td>
+      ** Type of data **
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Numerical value
+    </lark-td>
+    <lark-td>
+      123,1.23
+    </lark-td>
+    <lark-td>
+      Data range: -9E15 to 9E15
+    </lark-td>
+    <lark-td>
+      Number
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Text
+    </lark-td>
+    <lark-td>
+      "ABC","Shanghai"
+    </lark-td>
+    <lark-td>
+      The upper limit of characters is 2KB by default
+    </lark-td>
+    <lark-td>
+      String
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Time
+    </lark-td>
+    <lark-td>
+      "2019-01-01 00:00:00","2019-01-01 00:00:00.000"
+    </lark-td>
+    <lark-td>
+      "yyyy-MM-dd HH:mm:ss.SSS" or "yyyy-MM-dd HH:mm:ss". If it is necessary to indicate the date, "yyyy-MM-dd 00:00:00" could be used
+    </lark-td>
+    <lark-td>
+      String
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Boolean
+    </lark-td>
+    <lark-td>
+      true,false
+    </lark-td>
+    <lark-td>
+      -
+    </lark-td>
+    <lark-td>
+      Boolean
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      List
+    </lark-td>
+    <lark-td>
+      ["a","1","true"]
+    </lark-td>
+    <lark-td>
+      Elements in the list would all be converted into character strings, with at most 500 elements in the list
+    </lark-td>
+    <lark-td>
+      Array(String)
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Object
+    </lark-td>
+    <lark-td>
+      {hero_name:"Liu Bei",hero_level:22,hero_equipment: {"hero_name":"Liu Bei","hero_level":22,"hero_equipment": ["Male and female swords","Delu"],"hero_if_support":False}
+    </lark-td>
+    <lark-td>
+      Each sub-property (Key) in the object has its own data type. For detailed instructions on the values, please refer to the general properties of the corresponding above-mentioned types. There are at most 100 sub-properties inside the object
+    </lark-td>
+    <lark-td>
+      Object
+    </lark-td>
+  </lark-tr>
+  <lark-tr>
+    <lark-td>
+      Object group
+    </lark-td>
+    <lark-td>
+      {hero_name:"Liu Bei",hero_level:22,hero_equipment: ["Male and female swords","Delu"],"hero_if_support":False}, {"hero_name":"Liu Bei","hero_level":22,"hero_equipment": ["Male and female swords","Delu"],"hero_if_support":False}]
+    </lark-td>
+    <lark-td>
+      Each sub-property (Key) in the object has its own data type. For detailed instructions on the values, please refer to the general properties of the corresponding above-mentioned types. There are at most 500 OBJECTS inside the object group
+    </lark-td>
+    <lark-td>
+      Array(Object)
+    </lark-td>
+  </lark-tr>
+</lark-table>
+
+
+<quote-container>
+Note: in the AE background, the type of property value would be determined according to the type of property received for the first time. In the future, if the type of a certain property value in the data is inconsistent with the type confirmed previously, the property would be abandoned.
+</quote-container>
+
+In the AE background, you may notice that certain property names start with #, which is used as preset properties. It is unnecessary to set preset properties especially. SDK would track such properties by default. For detailed information, please refer to [<text underline="true">Preset properties and system fields</text>](https://thinkingdata.feishu.cn/wiki/HoS9wEGASi5cpMkA2KocFLkfndg).
+You should be especially noted that when the data format or type is not set correctly, the data could not be stored. Therefore, during and after the data ingestion process, you may need to verify or observe the correctness of data tracking through the [Tracking plan](https://thinkingdata.feishu.cn/wiki/K443wTChAiFc47kBz8ucXqVfnSf) module and modify the problems that occurred timely.
+## **III. Information Required for Data Ingestion**
+Before the R&D staff performs data ingestion officially, you should ensure the following information has been obtained:
+1. Project APP ID: when you create a project in the AE background, the APP ID of the project would be generated, which could be checked on the project management page. 
+2. Confirm the address of the data receiving end 
+- If you are using a SaaS version, please check the receiver URL on this page
+<image token="PCQTbAnrio8PtyxRz8bcmuG0ngb" width="1674" height="1318" align="center"/>
+
+- If you use the private deployment version, you can customize the data tracking URL .
+3. Verify the address of the receiving end: visit https://YOUR_RECEIVER_URL/health-check with the browser. If the page returns ok, it means the address is right.
+4. Data tracking scheme should include: 
+- Data ingestion method: client-side SDK. Server SDK, data import tool, or methods combining several schemes
+- Content and trigger time of data to be ingested
+You have finished reading the document of preparation before data ingestion. Congratulations. Now, you can perform data ingestion according to the method selected by referring to the corresponding data ingestion guidance.

package/wiki/te-docs/raw//345/256/242/346/210/267/347/253/257-sdk/openharmony//345/220/210/350/247/204/346/214/207/345/215/227.md

@@ -0,0 +1,96 @@
+---
+code: openharmony_sdk_compliance
+name: "合规指南"
+wikiToken: Oqo5wFXnSi28nZkThtZcyF4qnEK
+parentWikiToken: G1ZhwUWl2iwrvbkLDr3cThPDngd
+updateTime: 1776262493000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=zh-CN&code=openharmony_sdk_compliance
+---
+
+## 一、最新SDK版本说明
+满足监管新规的最新SDK版本：1.7.6
+## 二、权限调用合规要求
+
+| 权限名称 | 权限说明 | 使用目的 | 权限申请时机 |
+|---|---|---|---|
+| *ohos.permission.INTERNET* | *允许使用Internet网络* | *在使用上报数据功能时，用于访问网络数据* | *SDK初始化或者调用上报数据接口时* |
+| *ohos.permission.GET_NETWORK_INFO* | *允许应用获取网络信息* | *在使用上报数据功能时，SDK 会根据网络状态选择是否发送数据* | *SDK初始化时* |
+| *ohos.permission.STORE_PERSISTENT_DATA* | *允许应用存储持久化的数据* | *存储应用卸载之后需要保持不变的数据* | *SDK初始化时* |
+
+## 三、延迟初始化要求
+为了避免您的应用在未获取用户的同意前SDK提前处理用户的个人信息，SDK需要在用户同意 《隐私政策》后初始化。
+示例代码如下：
+```java
+// 根据隐私协议判断是否开启数据采集
+if (授权隐私政策) {
+    TDAnalytics.init(context, "appId", "serverUrl")
+}
+```
+
+SDK初始化的时候会收集操作系统版本、设备制造商、操作系统、屏幕分辨率、设备型号、APP 版本、网络状态、网络运营商、应用安装时间、系统语言等信息，用于统计分析功能。
+## 四、SDK 可选个人信息的配置说明
+开发者可以通过 SDK 可选个⼈信息的配置示例说明进⾏配置。您可以在SDK初始化的时候配置`disablePresetProperties` 参数，配置需要禁用的设备信息数组。disablePresetProperties默认是空数组，就是默认会采集所有的预置属性，如果你需要禁用某一个预置属性，可以将需要禁用的预置属性添加到disablePresetProperties数组中。
+以下是SDK 中所有事件默认采集的预置属性：
+
+| **属性名** | **中文名** | **属性类型** | **采集时机** | **说明** |
+|---|---|---|---|---|
+| #ip | IP 地址 | 文本 | 服务端采集 | 用户的 IP 地址，AE 将以此获取用户的地理位置信息 |
+| #country | 国家 | 文本 | 服务端采集 | 用户所在国家，根据 IP 地址生成 |
+| #country_code | 国家代码 | 文本 | 服务端采集 | 用户所在国家的国家代码(ISO 3166-1 alpha-2，即两位大写英文字母)，根据 IP 地址生成 |
+| #province | 省份 | 文本 | 服务端采集 | 用户所在省份，根据 IP 地址生成 |
+| #city | 城市 | 文本 | 服务端采集 | 用户所在城市，根据 IP 地址生成 |
+| #os_version | 操作系统版本 | 文本 | 初始化时采集一次 | iOS 11.2.2、Android 8.0.0 等 |
+| #manufacturer | 设备制造商 | 文本 | 初始化时采集一次 | 用户设备的制造商，如 Apple，vivo 等 |
+| #os | 操作系统 | 文本 | 初始化时采集一次 | 如 Android、iOS、HarmonyOS 等 |
+| #device_id | 设备 ID | 文本 | 初始化时采集一次 | 用户的设备 ID，iOS 取用户的 IDFV 或 UUID，Android 取 androidID |
+| #screen_height | 屏幕高度 | 数值 | 初始化时采集一次 | 用户设备的屏幕高度，如 1920 等 |
+| #screen_width | 屏幕宽度 | 数值 | 初始化时采集一次 | 用户设备的屏幕高度，如 1080 等 |
+| #device_model | 设备型号 | 文本 | 初始化时采集一次 | 用户设备的型号，如 iPhone 8 等 |
+| #device_type | 设备类型 | 文本 | 初始化时采集一次 | 设备类型，如 "Tablet"、"Phone" |
+| #app_version | APP 版本 | 文本 | 初始化时采集一次 | 您的 APP 的版本 |
+| #bundle_id | 应用唯一标识 | 文本 | 初始化时采集一次 | 应用包名或进程名 |
+| #lib | SDK 类型 | 文本 | 初始化时采集一次 | 您接入 SDK 的类型，如 Android，iOS 等 |
+| #lib_version | SDK 版本 | 文本 | 初始化时采集一次 | 您接入 SDK 的版本 |
+| #network_type | 网络状态 | 文本 | 初始化时采集一次，网络状态变化时采集 | 上传事件时的网络状态，如 WIFI、3G、4G 等 |
+| #carrier | 网络运营商 | 文本 | 初始化时采集一次 | 用户设备的网络运营商，如中国移动，中国电信等 |
+| #zone_offset | 时区偏移 | 数值 | 事件发生时采集 | 数据时间相对 UTC 时间的偏移小时数 |
+| #install_time | 程序安装时间 | 时间 | 初始化时采集一次 | 用户安装应用的时间，值来源于系统 |
+| #system_language | 系统语言 | 文本 | 初始化时采集一次 | 用户设备的系统语言(ISO 639-1，即两位小写英文字母)，如 zh, en 等 |
+
+例如您需要禁用#os（操作系统）、#os_version（操作系统版本），配置示例代码如下：
+```typescript
+let config = new TDConfig()
+config.appId = 'appId'
+config.serverUrl = 'url'
+config.disablePresetProperties =["#os", "#os_version"]
+TDAnalytics.initWithConfig(context, config)
+```
+
+如果您需要禁用全部的预置属性，可以将所有的属性配置到disablePresetProperties数组中，示例代码如下：
+```typescript
+let config = new TDConfig()
+config.appId = 'appId'
+config.serverUrl = 'url'
+config.disablePresetProperties =["#lib", "#lib_version", "#os", "#os_version", "#bundle_id", "#install_time", "#manufacturer", "#device_model",
+"#device_type", "#screen_width", "#screen_height","#system_language","#carrier","#app_version","#device_id","#network_type","#ip"]
+TDAnalytics.initWithConfig(context, config)
+```
+
+## 五、隐私政策披露要求与示例说明
+在您接入、使用数数科技SDK服务前，我们要求您在隐私政策中向用户告知我们SDK的名称、SDK提供方名称、收集个人信息类型、使用目的、隐私政策链接，并获取用户的同意或取得其他合法性基础。您可以参考如下方式提供条款内容：
+**第三方SDK名称**：数数科技SDK
+**第三方公司名称**：数数信息科技(上海)有限公司
+**收集个人信息类型**：在《隐私政策》中收集和获得您的个人信息栏目中根据实际情况填写以下内容，当您在激活使用时，我们会通过数数科技SDK收集您的设备信息（IP 地址解析的位置信息、国家、国家代码、省份、城市、操作系统版本、设备制造商、操作系统、屏幕分辨率、设备型号、APP 版本、网络状态、网络运营商、应用安装时间、系统语言）。
+**个人信息收集时机：**SDK初始化时获取。
+**使用目的**：用于统计分析用户在 App 内的使用效果。
+**隐私政策链接：****https://docs-v2.thinkingdata.cn/?version=latest&lan=zh-CN&code=privacy_cn&anchorId=**
+## 六、最终用户授权同意的建议方式
+App ⾸次运⾏时应当有隐私弹窗，隐私弹窗中应公示简版隐私政策内容并附完整版隐私政策链接，并明 确提示最终⽤户阅读并选择是否同意隐私政策；隐私弹窗应提供同意按钮和拒绝同意的按钮，并由最终⽤户主动选择。
+建议通过弹窗的形式征求用户授权同意，弹窗内容中需包含数数科技SDK需要申请的权限和采集的用户相关信息。
+隐私政策授权弹窗示例：
+
+（图片：隐私政策授权弹窗示例）
+
+敏感个人信息授权弹窗示例：
+
+（图片：敏感个人信息授权弹窗示例）

package/wiki/te-docs/raw//345/256/242/346/210/267/347/253/257-sdk/openharmony//346/233/264/346/226/260/346/227/245/345/277/227.md

@@ -0,0 +1,97 @@
+---
+code: openharmony_sdk_release_note
+name: "更新日志"
+wikiToken: ROKawkPC4ikdvfkxKUac2tsDnAh
+parentWikiToken: G1ZhwUWl2iwrvbkLDr3cThPDngd
+updateTime: 1775528174000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=zh-CN&code=openharmony_sdk_release_note
+---
+
+## v1.8.1
+**更新时间: 2026/03/25 **[下载](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2Fharmony%2Ftd_harmony_sdk_v1.8.1.zip)
+**更新内容：**
+- 已知问题修复
+## v1.8.0
+**更新时间: 2026/03/18 **[下载](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2Fharmony%2Ftd_harmony_sdk_v1.8.0.zip)
+**更新内容：**
+- 使用gzip压缩优化数据上报
+- 优化时区问题，使用number类型
+- 页面浏览支持Navigation
+- 页面浏览支持自定义参数
+- 元素点击支持自定义参数
+## v1.7.6
+**更新时间: 2026/01/05 **[下载](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2Fharmony%2Ftd_harmony_sdk_v1.7.6.zip)
+**更新内容：**
+- 已知问题修复
+## v1.7.5
+**更新时间: 2025/09/23 **[下载](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2Fharmony%2Ftd_harmony_sdk_v1.7.5.zip)
+**更新内容：**
+- 已知问题修复
+## v1.7.4
+**更新时间: 2025/08/29**
+**更新内容：**
+- 使用发布证书签名
+## v1.7.3
+**更新时间: 2025/08/12 **[下载](https%3A%2F%2Fdownload.thinkingdata.cn%2Fclient%2Fharmony%2Ftd_harmony_sdk_v1.7.3.zip)
+**更新内容：**
+- 已知问题修复
+## v1.7.1
+**更新时间: 2025/03/15**
+**更新内容：**
+- 更改为正式签名
+## v1.7.0
+**更新时间: 2025/03/10**
+**更新内容：**
+- SDK签名、混淆、字节码打包
+## v1.6.0
+**更新时间: 2025/01/20**
+**更新内容：**
+- 支持自动采集控件点击事件
+- 支持自动采集Router页面浏览事件
+- 设备号卸载之后保持不变
+## v1.5.0
+**更新时间: 2024/12/30**
+**更新内容：**
+- 提供获取账号ID接口
+- 解决API调用时序问题
+- 自动采集事件支持自定义属性
+- 预置属性开关
+- H5页面数据打通
+- 代码优化
+## v1.4.0
+**更新时间: 2024/10/10**
+**更新内容：**
+- 支持在work线程中调用
+## v1.3.0
+**更新时间: 2024/06/07**
+**更新内容：**
+- 修复userUnset带时间无效的问题
+- userDelete支持带时间
+- 初始化、timeEvent、calibrateTime去除await
+## v1.2.1
+**更新时间: 2024/05/15**
+**更新内容：**
+- 指定http协议为1.1解决部分手机上报数据失败问题
+## v1.2.0
+**更新时间: 2024/04/12**
+**更新内容：**
+- 增加数据缓存和批量发送功能
+- 支持自动采集
+- 支持数据存储和上报加密
+- 支持自定义时区
+- 支持事件上报带时区
+- 数据上报策略-支持WIFI、ALL
+## v1.1.0
+**更新时间: 2024/01/11**
+**更新内容：**
+- 适配ArkTS
+- 解决获取访客ID为空的问题
+## v1.0.0
+**更新时间: 2023/10/23**
+**更新内容：**
+- 支持事件和用户属性上报
+- 支持首次、更新、重写事件的上报
+- 支持 访客 ID 和 用户账号 的设置
+- 支持静态公共属性和动态公共属性设置
+- 支持Debug和DebugOnly模式上报数据
+- 支持时间校准功能

package/wiki/te-docs/raw//345/256/242/346/210/267/347/253/257-sdk/openharmony//350/277/233/351/230/266/346/214/207/345/215/227//345/244/232/345/256/236/344/276/213.md

@@ -0,0 +1,52 @@
+---
+code: openharmony_sdk_multi_appid
+name: "多实例"
+wikiToken: PJlcwcsswiCeAgkTqnKcmAo8nsb
+parentWikiToken: OC7JwBjzKiqT9Ck1WPAcpEaGnBd
+updateTime: 1774247886000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=zh-CN&code=openharmony_sdk_multi_appid
+---
+
+## 一、功能介绍
+我们支持使用多个Appid，创建SDK实例，我们简称为多实例。通过多实例功能，您可以上报数据到不同的项目。
+## 二、创建多实例
+传入不同的 APP ID 完成 SDK 初始化，即可创建多个 SDK 实例：
+```javascript
+//初始化配置1
+var config_1 = {
+  appId: "app-id-1", 
+  serverUrl: "https://youserverurl.1.com"
+};
+TDAnalytics.init(config_1);
+
+//初始化配置2
+var config_2 = {
+  appId: "app-id-2", 
+  serverUrl: "https://youserverurl.2.com"
+};
+TDAnalytics.init(config_2);
+
+//上报事件到配置1（不传app-id，默认上报到配置1）
+TDAnalytics.track({
+    eventName: 'event_from_appid_1'
+});
+//上报事件到配置1（指定app-id-1）
+TDAnalytics.track({
+    eventName: 'event_from_appid_1'
+}, 'app-id-1');
+//上报事件到配置2（指定app-id-2）
+TDAnalytics.track({
+    eventName: 'event_from_appid_2'
+}, 'app-id-2');
+```
+
+请注意多个 SDK 实例的 APP ID 必须不同，多实例之间的大多数数据是不共通的，详情可参考第四节"多实例间的数据、设置共享"。
+## 三、多实例间的数据共享
+大多数接口都是由实例对象所调用，因此绝大部分数据与设置在多 APPID 实例、父实例与轻量实例间是不共享的，但有部分数据与设置会对所有实例生效，以下是所有数据与设置在多实例间是否共享的详细说明：
+1. 账号相关信息
+- 系统默认生成的访客 ID`#distinct_id`：共享
+- 调用 `identify` 设置的访客 ID`#distinct_id`：不共享
+- 调用`login`设置的账号 ID`#account_id`：不共享
+2. 事件上报`track`与用户属性上报`user_set`、`user_setOnce`、`user_add`、`user_delete`：不共享
+3. 公共属性`setSuperProperties`和动态公共属性`setDynamicSuperPropertiesTracker`：不共享
+1. 记录事件时长`timeEvent`：不共享

package/wiki/te-docs/raw//345/256/242/346/210/267/347/253/257-sdk/openharmony//350/277/233/351/230/266/346/214/207/345/215/227//345/256/236/346/227/266/350/260/203/350/257/225.md

@@ -0,0 +1,48 @@
+---
+code: openharmony_sdk_debug
+name: "实时调试"
+wikiToken: R62wwxYpFiaRGRkVYS1c3hECnBc
+parentWikiToken: OC7JwBjzKiqT9Ck1WPAcpEaGnBd
+updateTime: 1776262486000
+sourceUrl: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=zh-CN&code=openharmony_sdk_debug
+---
+
+在SDK接入过程中，您可以通过查看SDK在IDE控制台中的日志或者使用 AE 的Debug功能，进行实时调试。
+## 一、打印SDK日志
+```javascript
+TDAnalytics.enableLog(true)
+```
+
+<quote-container>
+打开日志后，可以在IDE中来观察 SDK 的数据上报。
+</quote-container>
+
+## 二、开启 Debug 模式
+开启Debug模式需要如下两步操作:
+1. 客户端开启Debug模式
+以下是客户端开启Debug模式的示例代码:
+```java
+/*
+设置运行模式为 Debug 模式
+TDMode.NORMAL:数据会存入缓存，并依据一定的缓存策略上报,默认为NORMAL模式；建议在线上环境使用
+TDMode.DEBUG:数据逐条上报。当出现问题时会以日志和异常的方式提示用户；不建议在线上环境使用
+TDMode.DEBUG_ONLY:只对数据做校验，不会入库；不建议在线上环境使用
+ */
+let config = new TDConfig()
+config.appId = 'appID'
+config.serverUrl = 'serverUrl'
+config.mode = TDMode.DEBUG
+await TDAnalytics.initWithConfig(this.context, config)
+```
+
+1. TA后台添加Debug设备
+为了避免 Debug 模式在生产环境上线，规定只有指定的设备才能开启 Debug 模式。只有在客户端开启了 Debug 模式，并且设备 ID 在 TA 后台的"埋点管理"页的"Debug 数据"板块中配置了的设备才能开启 Debug 模式。
+<image token="FicqbANgwo0FcnxiCojcYR51nZN" width="2309" height="857" align="center"/>
+
+设备 ID 可以通过以下三种方式获取：
+- TA 平台中事件数据中的 #device_id 属性
+- 客户端日志：SDK 初始化完成后会打印设备 DeviceId
+- 通过实例接口调用：[<text color="purple" underline="true">获取设备ID</text>](https://thinkingdata.feishu.cn/wiki/OC7JwBjzKiqT9Ck1WPAcpEaGnBd)
+<quote-container>
+Debug 模式可能会影响数据采集质量和 App 的稳定性，只用于集成阶段数据验证，不要在线上环境使用。
+</quote-container>