Acquisition of Vendor Channel Arrival Receipt

Discontinuing Push Notification Service TPNS

Announcements

Features

SDK for Android

SDK for iOS

SDK for macOS

Release Notes

Overview

Strengths

Use Cases

Global Deployment

Product Introduction

Billing Overview

Purchase Directions

Billing Modes

Free Trial

Payment Overdue

Purchase Guide

Creating Products and Applications

Quick Integration with Android

Quick Integration with iOS

Creating a Push Task

Querying Push Records

Guidelines for Push Testing Methods

Product Restrictions

Getting Started

Troubleshooting Tool

Conversion Funnel

Push Plan

Push Settings

Message Recall

Push Management

Multi-Package Name Push

Notification Tap-to-Redirect

Custom Push Speed

Channel Policies

Message Collapse

Rich Media Notification

Custom Notification

Push to Accounts

Advanced Push Features

Operation Guide 

iOS Badge Feature Practice

Practical Tutorial

API Overview

Signature Authentication (Recommended)

Basic Auth Authentication

Request Structure

Call Method

Push API

Creating a Push Plan

Account Package Upload API

Token Package Upload API

Push APIs

Tag Binding and Unbinding

Deleting All Devices Under Tag

Tag APIs

Account Binding and Unbinding

Account and Device Binding Query

Account APIs

Querying Daily Aggregated Push Statistics

Querying Device Statistics

Querying All Push Information in Specific Period

Querying Push Information for One Task

Querying Push Statistics for a Single Task

Querying Aggregated Statistics for Multiple Tasks

Querying All Push Tasks on the Day by Token

Statistics APIs

User Attribute APIs

Server-Side Error Codes

Server SDKs

API (Java)

API Documentation

SDK Integration

Vendor Channel Integration Guide

Vendor Channels

Android SDK FAQs

Compatibility with Android P

Error Codes

Android Integration Guide

Acquisition of Push Certificate

Push Environment Selection Description

Extension Feature

iOS SDK FAQs

iOS Integration Guide

Client Integration Plugin

Push Certificate Description

macOS Integration Guide

SDK Documentation

Quick Configuration

Advanced Custom Configuration

Resource Tag

Users and Permissions

Service Level Agreement

Service Agreement

Android

Flutter

Others

FAQs

Privacy Policy

Data Processing and Security Agreement

Developer Agreement

Tencent Push Notification Service Policy

Contact Us

Glossary

Tencent Push Notification Service

To help you analyze the full-linkage message push effect, Tencent Push Notification Service supports the display of message arrival receipts for vendor channels. The support for message arrival receipts varies with the vendor channel inside Chinese mainland. The message arrival receipts of certain channels cannot be directly obtained without corresponding configuration.

After successfully configuring the message arrival receipt display feature, you can view the push conversion data in push details in the Tencent Push Notification Service console or obtain the push conversion data through a Tencent Push Notification Service RESTful API.

 The arrival receipt information of vendor channels is for reference only.

Receipt Configuration Guide for the Huawei Channel

After integrating the Huawei channel SDK, you need to enable and configure the message receipt feature on the Huawei Developer Platform so that the arrival receipts of the Huawei channel can be obtained. For configuration details, see 

https://developer.huawei.com/consumer/cn/doc/development/HMS-Guides/push-receipt#h1-1575515478691

. The configuration process is as follows.

https://developer.huawei.com/consumer/cn/service/josp/agc/index.html

Select the parent product name of the application for which the service is to be enabled. The application information page is displayed.

Set the message receipt address. Please view the service access point of your application in the 

Tencent Push Notification Service console

https://console.tencentcloud.com/tpns

 and select the corresponding receipt address for configuration.

 in the addresses with the access ID of your application. For example, if your application uses the Guangzhou service access point, set the receipt address to 

https://stat.tpns.tencent.com/log/statistics/hw/1500016691

Download the HTTPS certificate corresponding to the service access point of your application. Use a text editor to open the certificate file and copy the certificate to the certificate text box.

Configure the callback username and key (optional) for authentication.

, the error message "Failed to test the callback address" will be displayed. Ignore it and click 

Receipt Configuration Guide for the Meizu Channel

After integrating the Meizu channel SDK, you need to create a receipt on the Flyme push platform and activate it in the Tencent Push Notification Service console so that the arrival receipt of the Meizu channel can be obtained. The configuration process is as follows.

You need to complete both the following steps; otherwise, delivery through the Meizu channel may fail.

https://open.flyme.cn

, select the application for which a receipt is to be configured, and click 

. Please view the service access point of your application in the 

 and select the corresponding receipt address for configuration.


For the Guangzhou service access point, both receipt addresses must be entered.

After entering the receipt address, click 

 on the right. If the newly created receipt is correctly displayed in 

 page, select the application for which a receipt is to be activated, and click 

On the configuration management page, click the edit icon in 

On the Meizu official push channel editing page, click 

Receipt Configuration Guide for the HONOR Channel

After integrating the HONOR channel SDK, if you want to activate the HONOR channel arrival receipt, you need to contact the HONOR Push team and provide the following callback address for configuration. For more information, please see 

https://developer.hihonor.com/cn/doc/guides/100372

Please view the service access point of your application in the 

https://stat.tpns.tencent.com/log/statistics/honor/1500016691

tencent cloud