APP PUSH Component

APP PUSH component

The APP PUSH component sends mobile push notifications through the Umeng U-Push platform for promotions and alerts.

Note

Regardless of whether the link starts from the behavioral event component or the target audience component, users who enter the APP PUSH component match their QAID against the following IDs from all data sources:
- iOS: IDFA, DeviceToken, ALIAS
- Android: OAID, IMEI, DeviceToken, ALIAS

Notes:

DeviceToken and AliasID are not preset IDs. Add them as custom IDs in ID type management (field name: DeviceToken or ALIAS). For more information, see Add a custom ID. You can then enter user IDs directly in Quick Audience, upload an ID list as a group, or import a data table and filter to generate a target audience. For more information about how to create an audience, see audience management.
Register on the Umeng U-Push Platform and complete setup by following the Umeng Getting Started Guide:
- To receive push status receipts and analyze marketing results, contact Umeng to activate Umeng Pro.
- To open a specific app page with custom parameters, integrate key-value pairs as described in the Add Key Value Pair Parameters to Messages Guide, then implement the corresponding page routing in your app.
- For Android vendor channel push, configure the channels by following the Manufacturer Channel Integration Guide.
Bind your Umeng PUSH account through Account Authorization. The organization administrator configures the PUSH application. Create PUSH API.
For more information about how to limit the number of times that push messages can be sent to the same user within a specified period of time and the period of time that you can use to do not disturb users, see Fatigue Control.

To configure the APP PUSH component:

Click the APP PUSH component and configure it in the right panel.

Parameter	Description
Step Name	Enter a step name.
PUSH account	Select a bound Umeng PUSH account.
PUSH application	Select a PUSH application. The platform type (iOS or Android) appears after the app name.
Touch ID	Select the ID type to reach users: iOS: IDFA, DeviceToken, Alias Android: OAID, IMEI, DeviceToken, Alias
AliasID type	If AliasID is selected, enter the alias type.
Message Type	If Fatigue Control is enabled, select a message type. Notification: Not subject to fatigue control rules. Promotion: Subject to fatigue control rules. Messages stop after the limit is reached within the configured period.
Notification Title	Enter the notification title.
Notification Content	Enter the notification content. A preview appears on the right. Insert variables to personalize content per user. Click the icon where you want to insert a variable, then configure it in the dialog box. Target audience links: Select a user tag as the variable value. Behavioral event links: Select an event attribute as the variable value. You can also select a user tag as the variable value. The event user's QAID is matched against tag values from all data sources. Note To use tags as variable values with a behavioral event component, purchase a Tablestore instance and activate the feature. Contact the Alibaba Cloud sales manager. This instance can be shared with the Tablestore instance in Tablestore Authorization Configuration. Enter the variable name. Specify whether to send no content or a default value when the property or tag is empty. For example, if the content is "Test Android message ${name}" and the user's event reports the nickname Zhang San, the message is sent as "Test Android Message Zhang San". If no nickname is reported, it is sent as "Test Android Message". Click Insert.
Push Wake	Action when a user taps the notification: Open the app. Open a URL (Android only). Select http:// or https:// from the drop-down list and enter the rest of the URL. Open an in-app page (Android only). Enter the full package name and activity name. Contact your app developer for these values. Custom parameters: Set key-value pairs to open a specific app page. You can set multiple pairs. Do not use "d" or "p" as keys. Total characters across all keys and values must be less than 1,000.
Manufacturer Push	Android only. Routes messages through vendor channels to improve reach rate. Enable the switch and enter the full package name and activity name. Contact your app developer for these values.

Click OK.

Use AliasID

Umeng Setup

Complete these steps on the Umeng platform to use AliasID for push messages:

Call setAlias(alias, alias_type) to bind alias + alias_type to device_token. Documentation: Android: https://developer.umeng.com/docs/67966/detail/98583

iOS: https://developer.umeng.com/docs/67966/detail/66734#h2-u4F7Fu7528u522Bu540D10
To receive push status receipts, contact Umeng to activate Umeng Pro. Then configure the receipt address in the Application Receipt Configuration section of the Umeng backend. The AliasID type must match the Alias_type in the receipt configuration to view receipt data in Quick Audience.

Quick Audience Setup

After completing Umeng setup, follow these steps in Quick Audience:

Create an ID type. Set the ID type code to ALIAS.
Upload ALIAS ID

Import the AliasIDs to send.
Use in automated marketing

Enter the Alias_type in the AliasID type field. The system uses the AliasID + Alias_type binding to locate the target device token.

To receive task receipt data, configure the receipt address in the Umeng backend before sending. The AliasID type must match the Alias_type in the receipt configuration to view receipt data in Quick Audience.
Send Results
- Planned Sends: Number of submitted AliasIDs.
- Actual Sent: Number of AliasIDs actually sent.
- Successful: Number of AliasIDs matched with downstream Umeng AliasIDs.
- Failed: Number of AliasIDs not matched with downstream Umeng AliasIDs.
- No Feedback: No receipts received.
- Displayed: Number of messages displayed on matched devices (per device).
- Opened: Number of messages opened on matched devices (per device).
- Ignored: Number of messages ignored on matched devices (all devices are counted as ignored).