Term | Description |
SDKAppID (Application ID) | A unique identifier automatically generated when an application is created. The Push Service uses SDKAppID to distinguish different applications. Data between different SDKAppIDs are not interoperable. |
Client Key (appKey) | A client authentication key used to verify the client's identity during push service registration. |
Self-built Push Channel | A long-connection message push channel built by the Instant Messaging (IM) push service, offering global coverage, high connectivity, reliability, and security. |
Manufacturer Push Channel | System-level push channels provided by mobile device vendors: Android: Xiaomi, Huawei, Honor, OPPO, vivo, Meizu, NIO, Google FCM. iOS: APNs (Apple Push Notification service). |
Development Platform | Supports major client platforms and popular frameworks including Android, iOS, HarmonyOS, and more. For details, see the development platform introduction. |
Online Push | Pushes online messages to users through Chat's self-built push channel when the app is running in the foreground or its process is active. |
Offline Push | Pushes offline message notifications to users through manufacturer push channels when the app process is terminated by the system or user. |
Registration ID | The unique identifier of a terminal device on the push service platform. Automatically generated after successfully calling the registerPush API. This ID changes if the app is uninstalled and reinstalled. |
Term | Description |
All Users Push | Sends messages to all reachable users in the app. Ideal for important announcements, marketing campaigns, and routine operations. For details, see All Users/Tag Push API. |
Tag Push | Sends messages to user groups filtered by tags or attributes (such as gender, region, interests, etc.). Useful for targeted engagement, coupon distribution, and daily operations. For details, see All Users/Tag Push API. |
Single Push | Directly targets a batch of user IDs for message delivery. Suitable for small-scale or repeated batch push scenarios. For details, see Single Push API. |
Chat Message Push | In instant messaging scenarios (one-on-one chats, group chats, or communities), when users receive IM messages while offline, these messages are delivered via offline push notifications. Clicking the notification opens the IM chat interface. Requires integration with Tencent Cloud Instant Messaging (IM) service. For details, see Integrate Chat Offline Push. |
Audio/Video Call Message Push | In 1-on-1 or multi-party audio/video call scenarios, offline users are notified via offline push, supporting both Notification and VoIP styles. Requires integration with Tencent Cloud TRTC TUICallKit. For details, see TUICallKit Component Introduction. |
Platform | |||||||
Supported | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
Term | Description |
Push Strategy | Two push strategies are available: • Online push only (PushFlag = 1): Sends online pushes via the self-built push channel when users are online. No push notifications are sent when users are offline. • Online and offline push (PushFlag = 0): Sends online pushes via the self-built push channel when users are online, and offline pushes via manufacturer push channels when users are offline. For details on offline channels, |
Enables users to customize the badge style and count displayed on the app icon for push messages. | |
Allows custom ringtones to be set for push messages. | |
Allows customization of the page or action triggered when a user taps a push message. | |
Enables customization of the small icon displayed with push notifications. | |
Intelligent Multilingual Push | Supports configuring multiple language versions for the same push message. The backend automatically delivers the appropriate language based on the user's device settings. |
Provides callbacks for All Users, Tag, Single, and other push types to help you control app functionality and workflows with precision. | |
Allows recall of All Users/Tag push messages. For example, if a message contains incorrect content that could negatively affect users, you can promptly recall it. |
Term | Description |
Push Record | Query details of recent push events; records generated via console tools or server-side APIs are available. |
Message Link | View the complete message delivery path, message details, and device information for a specific user in a push event. |
Push Conversion Funnel | Displays funnel metrics for recent push tasks, including sendable count, sent count, delivered count, and click count, to help you quickly assess conversion performance. |
Push Loss Analysis | Analyzes message loss or undelivered cases during transmission. By calculating loss rates at each stage, you can identify bottlenecks and optimize push strategies to improve delivery rates. |
Term | Description |
Available Send Quantity | The total number of valid devices eligible for push delivery after filtering the target audience for a push task. |
Sent Quantity | The total number of valid devices successfully sent via self-built push channels and manufacturer push channels. |
Reached Quantity | The total number of receipts successfully received by terminal devices after delivery via self-built push channels and manufacturer push channels. |
Click Quantity | The total number of receipts clicked by users after a successful push display, reflecting user responsiveness to the push. |
Actual Send Rate | Measures the success rate of push task delivery, reflecting the push system's ability to send messages to push channels. Formula: (Sent Quantity / Available Send Quantity) × 100%. |
Reach Rate | Measures the success rate of push messages reaching terminal devices, reflecting the push channel's ability to deliver messages. Formula: (Reached Quantity / Sent Quantity) × 100%. |
Click-Through Rate | Measures user willingness to click on push messages, reflecting the attractiveness of push content and user engagement. Formula: (Click Quantity / Reached Quantity) × 100%. |
Feedback