Configure Quick Tracking (QT) to send event data to your Quick Audience workspace.
The Event Reporting Overview covers the full Quick Tracking data collection and reporting process.
Step 1: Purchase Quick Tracking
Purchase Quick Tracking in the same region as your Quick Audience instance.
Identify your region by the browser endpoint. Public cloud endpoints:
-
Zhangjiakou: quicka.aliyun.com
-
Shanghai: quicka-shanghai.aliyun.com
-
Shenzhen: quicka-shenzhen.aliyun.com
Quick Tracking is available only in Zhangjiakou and Shanghai. If your Quick Audience instance is in Shenzhen, Quick Tracking cannot report events.
Step 2: Connect Quick Tracking to Quick Audience
Enter your Quick Audience system information in the Quick Tracking console to link the two services.
Purchase Quick Tracking in the same region as your Quick Audience instance (Step 1).
To configure the connection:
-
Log on to the Quick Tracking console and go to Management Console > System Integration.
-
Turn on the Quick Audience Data Exchange switch.
-
Click Edit Configuration and enter the following parameters.
Parameter
Description
AccessKey ID
Your Quick Audience organization ID.
In Quick Audience, go to Management Center > Tenant Management > Organization Settings and copy the AccessKey ID.
OpenAPI URL
The Quick Audience OpenAPI endpoint for your region.
Public cloud endpoints:
-
Zhangjiakou: quicka.aliyun.com
-
Shanghai: quicka-shanghai.aliyun.com
-
-
Click Save.
Step 3: Configure a Quick Tracking application
A Quick Tracking application collects and reports event data. You define which events and properties to collect. Three types are supported: mobile apps, websites, and mini programs.
Configure the application, organizations, events, and properties in the Quick Tracking console. Each QT organization maps to one QA workspace, with data isolated between organizations. The Collection Management Overview has detailed steps.
Quick Tracking events are either system-preset or custom:
-
Custom event requirements:
-
To use reported data in automated marketing, add the External Business ID property to the event. Set the encoding to outBizId and value type to Text. Include this property when reporting event data.
For transaction-related events, report the order ID as the outBizId. For coupon-related events, report the coupon ID as the outBizId.
-
Event encodings must not conflict with existing events in the target Quick Audience workspace. Conflicting encodings may cause Quick Audience to reject the data.
-
-
For system-preset events:
-
System-preset events do not currently have the External Business ID property, so their data cannot be used for automated marketing at this time.
-
To use system-preset event data for automated marketing, create a corresponding custom event instead.
-
Step 4: Associate a workspace with a Quick Tracking application
An organization administrator authorizes a Quick Tracking application's events for a workspace.
One Quick Tracking application can be authorized for multiple workspaces.
To authorize applications:
-
Log on to the Quick Audience console. Switch to the V4 version, click the
icon in the upper-right corner, and choose Tenant Management > QT Event Authorization.
-
Click Edit for the target workspace.
-
Select one or more Quick Tracking applications to authorize.
ImportantData is isolated between QT organizations and QA workspaces. Maintain a one-to-one mapping: authorize applications from one QT organization to one QA workspace.
If two QT organizations share an event encoding and both are authorized to the same workspace, the later event's metadata overwrites the earlier one. A one-to-one mapping prevents this conflict.
-
Click Confirm.
After authorization, events sync to the Event Center page. The event source shows Quick Tracking. The data ingestion method shows - until data arrives.
