Glossary - Jiguang Docs

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: App notification: JPush public cloud protocol and JPush private cloud protocol SMS: Jiguang SMS protocol, Chuanglan protocol, Montnets protocol, CMPP protocol WeChat Mini Program: subscription messages WeChat Official Account: template messages Email: SMTP sending protocol Alipay Life Account: template messages
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 by users 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.

Operation Plans

Term	Meaning
Operation Plan	The basic module of Jiguang Operation. Helps operators quickly create plans to reach target audiences through a reach method (SMS, app notification, etc.) when certain conditions are met. Examples: welcome push for new users, payment reminder after adding to cart without payment, SMS after successful payment.
Scheduled - One-time Send	A plan type for one-time execution at a fixed time. Example: pre-event warm-up push.
Scheduled - Recurring Send	A plan type for recurring execution at fixed times each cycle. Example: new user gift reminder in the first cycle.
Trigger - Complete Event A	A trigger plan sent when the user completes a behavior. Example: real-name verification reminder after first login following registration.
Trigger - Complete Event A but Not Event B	A trigger plan sent when the user completes one behavior but does not complete another within a period. Example: purchase reminder 1 hour after adding to cart without payment.
Frequency Control Strategy	A user may be triggered by the same plan multiple times. To avoid excessive disturbance, set the maximum number of participations per user in a time period (customizable), or the minimum interval between participations in the same plan. Example: at most once per day; interval over 6 hours. Applies only to the current plan.
Target Audience	The user group that can enter the operation plan flow, defined by rules and conditions.
Sending Strategy	Sending steps for multiple message types and trigger conditions between them. Example: send SMS if app notification is not delivered within 5 minutes.
Message Content	Content presented to users when sent.
Plan Goal	Measures operation plan effectiveness. After reach, if the user completes the conversion event within the custom period, the goal is achieved.
Send Task	A send task issued when reach conditions are met in an operation plan.
Valid Targets	In send tasks, the valid target count after validity filtering of the plan target audience.
Send Count	In send tasks, the count of successfully created message send tasks.
Delivered Count	In send tasks, the count of messages actually delivered to users. Deliveries after 5 days are not counted.
Click Count	In send tasks, the count of user clicks after delivery. Clicks after 5 days are not counted.
Send User-times	Send count deduplicated by unique user per task ID (if one user is sent via multiple channels in one task, counted as 1).
Delivered User-times	Delivered count deduplicated by unique user per task ID.
Goal Achieved User-times	Goal achievement count deduplicated by unique user per task ID (multiple goal completions by one user in one task count as 1).
Goal Achievement Rate	Cumulative goal achievements / delivered user-times in send tasks.
Delivery Rate	Delivery rate = delivered user-times / send user-times. Data after 5 days is not included.

Message Loss

Term	Meaning
Plan Target - Valid Target	At device ID granularity, loss of plan targets filtered as invalid by reach channel validity rules (255/90-day active filter, uninstalled users, invalid token, etc.).
Valid Target - Send Count	At device ID granularity, Jiguang successfully initiated a service request but failed to create a push task due to push limits, vendor parameter errors, etc.
Send Count - Delivered Count	At device ID granularity, push task created but not delivered due to user offline, message offline period exceeded, etc.
Delivered Count - Click Count	At device ID granularity, message delivered but not opened or navigated due to display failure, callback failure, etc.
Send Failure	At msgid granularity, overall send failure due to parameter errors, insufficient permissions, sensitive word review, etc. Shown in red in message records with failure reason. Failed messages cannot enter message details.