Terms
Last updated：2023-02-21
Terms
Basic Terms
| Term | Meaning |
|---|---|
| Project | The highest business isolation unit in Operation Growth. Business data and user data are isolated between different projects. |
| appkey | The application ID that can be integrated into an Operation Growth project. Currently each project supports adding only one application. APPKEY can be used for Android, iOS, Web, Mini Program, Official Account, HTTP API, and other platforms. |
| Master Secret | Used with AppKey by developers when calling Jiguang service APIs for authentication. Keep the Master Secret secure and prevent leakage. |
| Data Source | The source from which Operation Growth obtains data, used to support operation growth features, data collection and reporting, and other business scenarios. Includes Android, iOS, Web, WeChat Mini Program, WeChat Official Account, and HTTP API. |
| Reach Channel | Six channel types, each with its own service protocol: |
| Contact Method | Used to send reach messages and identify where users receive reach messages. Each user can have multiple contact methods for each reach channel. |
| User Identifier | Any field that can be used to distinguish user identity. Custom creation is supported, such as loginID, ID card number, faceID, device ID, WeChat openID, phone, OAID, IDFA, and so on. |
| Device ID | The device identifier ID of an end user based on APPKEY. |
| CUID | The unique user ID of an Operation Growth product project. |
Tags
| Term | Meaning |
|---|---|
| Tag | Labeling users and differentiated group evaluation based on customer business behavior data and operational experience through tag rules. |
| Custom Tag Value | Customize each tag value name and calculation rules to segment audiences. Examples: gender tag, VIP level, visit channel, etc. |
| Basic Metric Value | Use calculation results such as event completion count as tag values. Examples: logins in last 7 days, monthly consumption amount, etc. |
| First/Last Feature | Use the time of first or last completion, days from today, or event properties as tag values. Examples: days since last active, first payment amount, etc. |
| Event Preference Attribute | Group and rank users by an event property; use top-ranked groups as tag values. Examples: top 3 shared product categories, top 5 financial products by purchase amount, etc. |
| Behavior Distribution Result | Use days or hours of event distribution in a period as tag values. Examples: hourly page view distribution yesterday, login days in last 30 days, etc. |
In-app Marketing Score
| Term | Meaning |
|---|---|
| Marketing Score | Score and differentiated individual evaluation based on customer business behavior data and operational experience through scoring rules. |
| Custom Rules | Customize scoring items and rules; add corresponding scores for users meeting conditions. Examples: user value score, credit score, etc. |
Was this document helpful?
