You can collect and report the data of user behavior events (including order events) on your apps, mini programs, web pages, and other applications to Quick Audience in real time. The Membership Platform and Social Interaction modules also report related user behavior events to Quick Audience. These user behavior event data will participate in real-time ID Mapping to obtain the unified identity QAID of users, and then can be used for automated marketing. In addition, if the storage of reported data is enabled for an event, the data reported by the event will be stored in the analysis source and become the user behavior table and order detail table, which can be used for audience filtering, generation of AIPL/RFM models, custom tags, and so on.
Behavioral events such as:
The user registers or logs in on your App. The key data includes the user's membership ID, the mobile phone number or associated WeChat account number used by the user for registration, the time when the behavior occurred, and the App name.
The user purchases through WeChat applet. The key data includes the user's OpenID, UnionID, order number, time of occurrence, order status, WeChat applet AppID, purchase commodity code, quantity, amount, payment method, etc.
Users register Membership Platform, purchase goods, use coupons and so on through the membership module.
This topic describes the new version of the real-time event reporting method. You can use the old version of the real-time event reporting method. The old version does not allow event data to be involved in ID mapping to obtain QAIDs. The old version does not allow event data to be stored in analysis sources. The old version of the real-time event reporting method can be used only for automated marketing started with behavioral events. For more information, see Event Management (Old Version).
Event reporting method
Quick Audience supports the following event reporting methods:
Quick Tracking: collects and reports events by using Alibaba Cloud Quick Tracking. This method is applicable only to apps, mini programs, and web pages (including H5 apps). Quick Audience is connected to Quick Tracking. Applications can use the SDK provided by Quick Tracking to collect and report events.
NoteQuick Audience of the standalone deployment edition does not support Quick Tracking reports.
Quick Tracking is available only in the China (Zhangjiakou) and China (Shanghai) regions. If your Quick Audience is located in China (Shenzhen), you cannot use Quick Tracking to report events to Quick Audience.
Self-directed access: You can use a self-developed program to track application events, convert the event data to an event model defined by Quick Audience, and then report the event data by using the event reporting API provided by Quick Audience.
All event reporting methods support enabling /disabling storage.
Order event description
Order events are a special type of behavioral events that focus on the behavior of users related to the purchase of goods.
The current system provides three standardized order events for independent access and membership platform: purchase of goods, refund of goods, and cancellation of orders. For more information, see Event Hub. Reported order event data can be used as behavioral data for automated marketing; if storage is enabled, it becomes an order schedule after storage.
If you do not follow the standardized order event model, but report order events based on the general behavior event model, the reported order event data becomes a user behavior table after it is stored.
Quick Tracking Report Process
Purchase a Tablestore instance in the same region as your Quick Audience instance and authorize Quick Audience to access it. For more information, see Tablestore Authorization Configuration.
For more information about how to purchase a Quick Tracking that is deployed in the same region as your Quick Audience instance and connect to Quick Tracking in the Quick Tracking console, see Quick Tracking Purchase and Connection.
Configure organizations, applications, events, and properties in the Quick Tracking console. For more information, see Configure Quick Tracking Application.
ID Type Management. Specify the user ID types supported by Quick Audience and the ID mapping policy.
QT Event Authorization is performed to synchronize events from the Quick Tracking application to the Event List in the specified workspace of Quick Audience.
If you need to store the reported event data in the analysis source and become a user behavior table for later use, turn on the event storage switch in the Event List.
Use the SDK reference provided by Quick Tracking to develop a program for collecting and reporting data based on the event model, and add your apps, mini programs, and web applications.
The program developed in the previous step will automatically collect and report data when the user executes the corresponding behavior event in your application.
After the data is received by Quick Audience, it will participate in real-time ID mapping to obtain the user's QAID. If the storage is enabled, it will be stored in the analysis source.
Autonomous access reporting process
Purchase a Tablestore instance in the same region as your Quick Audience instance and authorize Quick Audience to access it. For more information, see Tablestore authorization configuration.
ID Type Management. Set the user ID types supported by Quick Audience and the ID mapping policy.
For more information about how to define an event model based on your business requirements, see Event Management.
If you need to store the reported event data in the analysis source and become a user behavior table for later use, turn on the event storage switch in the Event List.
You can develop a tracking program to collect complete event model data and add the program to applications such as apps, mini programs, and web pages.
Use the API provided by Quick Audience to develop a program for reporting data based on the event model and add it to the same application. For more information, see Event Reporting API Specification.
When the user executes the corresponding behavior event in your application and is collected by your tracking program, the program developed in the previous step will automatically report the data.
After the data is received by Quick Audience, it will participate in real-time ID mapping to obtain the user's QAID. If the storage is enabled, it will be stored in the analysis source.