Quick Audience:User Marketing Overview

Features

The user marketing module includes three parts:

• Marketing Management:

  • Campaign management: covers marketing planning and execution, linking audiences and tasks to help you manage the full campaign lifecycle. Quick BI professional reports can be embedded into campaign pages for analysis.

  • Material management: upload and centrally manage images, videos, audio, and Lottie files as marketing materials. Materials uploaded during task creation are also saved to the material library.

  • Short link management: compresses long URLs into short URLs to save character space in SMS messages.

• Touch Marketing:

  • SMS: integrates with the Alibaba Cloud SMS Platform and third-party SMS platforms to send scheduled or instant SMS messages to audiences.

  • Lingyang SuperSMS: sends card-style text messages to audiences on a scheduled or instant basis.

    Note

    No registration on other platforms is required. Purchase SMS allowance through Alibaba Cloud Sales to start using Lingyang SuperSMS.

  • Email: integrates with the Alibaba Cloud Email Platform to send scheduled or instant emails to audiences.

  • WeChat: connects to the WeChat Official Account for content management.

  • PUSH: integrates with the Umeng U-Push Platform to send scheduled or instant messages to audiences.

  • Webhook: connects to your first-party systems (such as CRM) or third-party systems for audience marketing.

• Advertising Marketing:

  • Push audiences to Data Bank and Damengpan to build omnichannel consumer data assets for your brand.

  • Push the audience to U-Oplus, Ocean Engine, Tencent Advertising, and Baidu Marketing for advertising and marketing on those platforms.

ID types and encryption methods supported by each channel

When a marketing task requires user IDs, the system queries associated ID types through the QAID of each audience member. Because some users may not have the required ID type imported, the audience count and actual send count may differ.

Each marketing channel supports the following ID types and encryption methods:

• SMS: mobile phone number (original /AES).

• Lingyang SuperSMS: Mobile phone number (original /AES/MD5/SHA256).

• Email: Email (sic /AES).

• Umeng U-Push:

  • iOS applications: IDFA (original text /AES) and DeviceToken (original text /AES).

  • Android applications: IMEI (original /AES), OAID (original /AES), and DeviceToken (original /AES).

  Note

  You can use DeviceToken only after you add DeviceToken as a custom ID in the ID Type Management section.

• Webhook: The supported ID types depend on the configurations of your webhook and the connected system or third-party system.

  The ID encryption method supports the original /AES/MD5/SHA256, but QuickAudience does not decrypt the MD5 or SHA256 encrypted ID. To use the ID, your system or third-party system must support MD5 or SHA256 decryption.

• Data bank: mobile phone number, email address, MAC address, IMEI, IDFA, IMSI, OAID, Taobao ID, and Taobao nickname.

  Before the push, the ID is encrypted by using the MD5 or SHA256 encryption method that you select.

• Damengpan: mobile phone number, email address, IMEI, IDFA, Taobao ID, and Taobao nickname.

  Before push, the ID is encrypted by using the MD5 or SHA256 encryption method that you select. The SHA256 encryption method supports only push mobile phone numbers.

• U-Oplus: IMEI (original /AES/SHA256), IDFA (original /AES/SHA256), mobile phone number (original /AES/SHA256).

• Ocean engine: IMEI (original /AES/MD5), IDFA (original /AES/MD5), mobile phone number (original /AES/SHA256), OAID (original /AES/MD5).

• Tencent advertising: IMEI (original /AES/MD5), IDFA (original /AES/MD5), mobile phone number (original /AES/MD5/SHA256), OAID (original /AES/MD5).

• Baidu Marketing: IMEI (original /AES/MD5), IDFA (original /AES/MD5), OAID (original /AES/MD5), mobile phone number (AES/MD5).

For all channels listed above:

• AES-encrypted IDs are decrypted before Quick Audience sends the marketing task or push to the channel, and the plaintext ID is sent.

• MD5/SHA256-encrypted IDs remain encrypted when Quick Audience sends the marketing task or push to the channel. The receiving channel decrypts them as needed.

Procedure

The following outlines the general workflow of the user marketing module. For channel-specific details, see the documentation for each channel.

1. For more information about how to develop marketing plans and create marketing activities, see Marketing Campaign Documentation.

   You can perform lifecycle management and embed relevant Quick BI reports for data analysis at different stages of a marketing activity based on the progress of the activity.

2. You can create a marketing object as a group of people. You can filter out audience by using data tables, RFM models, or AIPL models, or upload a list of marketing object IDs as audience. For more information, see Audience Management.

3. You must purchase user marketing feature packs for some channels. For more information, see Sales List and Billing Guide.

4. For more information about how to configure accounts for WeChat Official Account, Umeng PUSH, Data Bank, Damengpan, U-Oplus, Ocean Engine, Tencent Advertising, and Baidu Marketing, see Account Authorization.

5. For Alibaba Cloud SMS, third-party SMS, Alibaba Cloud email, and Umeng Push, the organization administrator configures the corresponding API operations. For more information, see API Management.

6. For SMS messages, emails, WeChat messages, and Umeng push messages, you can control the frequency of sending marketing messages to a single user. This prevents excessive interruptions to users and causes dissatisfaction or complaints. For more information, see Fatigue Control.

7. For more information about how to manage SMS, Lingyang SuperSMS, email, and WeChat templates, manage SMS signatures, short messages, Webhook management, images, videos, audios, and Lottie materials, see the template management and other documentations of various channels, Webhook Management and Material management.

8. For more information about creating marketing tasks for each channel, see the Creating tasks for each channel documentation.

9. After the task is executed:

   • View the execution of tasks. Some channels support saving users in the specified receiving status as a audience. For more information, see the task management documentation for each channel.

   • For more information about the statistics and analysis of the sending, reading, exposure, number of clicks, and spending, see the marketing effect analysis document of each channel.

FAQ