Introduction to the Event Hub

Event model

A complete behavior event that you collect and report consists of the following data:

• Event ID: The unique identifier for an event. This is required.

• User ID: This is required.

• Event properties: An event can have several properties, such as the time of occurrence, channel, product, and quantity.

  • Property ID: The unique identifier for a property. This is required.

  • Property value: The value can be text, a number, or a time. This is required.

  Note

  For standardized order events, the product information property in the model is an array. This array contains items such as product name, product ID, unit price, and quantity purchased.

You can configure the event ID and event properties when you define an event.

Event details

Go to Workspace > Configuration Management > Data Access Management > Event Hub. The event list appears as shown in the following figure.

The left navigation pane displays event groups, including an Unassigned group and any custom groups you create. By default, all groups are shown. For more information about event grouping, see Event grouping.

The list on the right displays the events and includes information such as event ID, event type, event source, data ingestion method, and storage status.

Search for events by name or ID, or filter by event type, event source, or last modified time.

Create a custom event

If the system-predefined events do not meet your needs, you can create custom events:

• If you use the custom ingestion method, you can create custom events for the current workspace in Quick Audience.

• If you use the Quick Tracking method, first configure the application and its events in the Quick Tracking console as described in the Event Reporting Overview. Then, synchronize the configured events to the current Quick Audience workspace through QT event authorization.

To create a custom event in Quick Audience using the custom ingestion method:

1. Go to Workspace > Configuration Management > Data Access Management > Event Hub.

2. Click Create Event in the upper-right corner to open the event configuration page.

3. Configure the parameters as described in the following table.

   

   Parameter	Description
   Event name	Enter a name for the event.
   Event ID	Enter an ID for the event. The event ID must be unique within the current workspace. The event ID is required when you report event data and is used to uniquely identify an event.
   Event properties	An event can have several properties, such as the time of occurrence, channel, product, and quantity. When you create a custom event, two predefined properties are included by default: Event occurrence time: The property ID is occur_time, the type is time, and it is required by default. Event occurrence channel: The property ID is occur_channel, the type is text, and it is required by default. You can click Edit for a predefined property to change whether it is required. The name, ID, and value type cannot be modified. You can also add other properties. Click Create Property to open a dialog box where you can configure the property name, property ID, value type (text, number, or time), and whether it is required. You can Edit or Delete new properties. All settings, including the name and ID, can be modified. Important To use the reported data in Automated Marketing, add an External Business ID property to the event. Set the property ID to outBizId and the value type to Text. When you report event data, this property must be included for the data to be used in Automated Marketing. We recommend that you report the order ID as the outBizId for transaction-related events and the coupon ID as the outBizId for coupon-related events.

   

4. After you configure the event, click Save.

5. Batch import events:

   • Only standard Excel and CSV files are supported.

   • You can upload up to 1,000 events in a single file.

   • If an event ID in the uploaded file already exists, the event is updated with the latest content from the file. If an event ID does not exist, a new event is created based on the content in the file.

   • The event source for batch-imported events is set to "Custom Ingestion" by default.

As shown in the following figure, the created custom event is added to the event list, and its event source is displayed as Custom Ingestion.

Enable or disable storage

You can enable data storage for Quick Tracking events and custom ingestion events. Storage is enabled by default for Membership Hub events and Social Interaction events, but you can disable it. You cannot disable storage for order events from the Membership Hub.

After you enable storage, reported event data is stored in the analysis source. Normal behavior event data is saved to a user behavior table, and order event data is saved to an order details table. You can use this data for audience segmentation, AIPL/RFM dataset generation, and custom tag creation.

In the event list, turn the Storage switch on to enable storage. Turn the switch off to stop storing new data. Existing data is not deleted.

After you enable storage, event data received by Quick Audience is forwarded as follows:

1. After the data is received, it is temporarily stored in the Tablestore instance specified in the Tablestore Authorization Configuration. A real-time ID Mapping is performed in Tablestore to obtain the unified user identity, QAID.

   Note

   • Event data goes through this step regardless of whether storage is enabled. After this step, the event data can be used for Automated Marketing.

   • Data is temporarily stored in the Tablestore instance for two days and then automatically deleted.

2. The data, along with the QAID, is synchronized to the MaxCompute compute source in the early morning of the next day. It is then imported into the user behavior table in the Analysis Source Configuration.

   In the same workspace, Quick Tracking events, custom ingestion events, Membership Hub events, and Social Interaction events are stored in different user behavior tables.

   For more information about the data format of the user behavior table, see User Behavior Table Requirements. The behavior type field stores the event name, and the property and metric field names match the event property names.

   Note

   • Because MaxCompute limits a table to a maximum of 1,200 columns, and QAID and event name each occupy one column, any event properties beyond the 1,198-property limit are stored in a new table.

   • Stored event data cannot be deleted.

View an event

Click View to open the event details page, which shows the event configuration and the automated marketing campaigns that use it.

Edit an event

You can edit custom ingestion events and standardized order events for custom ingestion (with event IDs pay_order, refund_order, and cancel_order).

Click Edit to open the editing page for a custom ingestion event, as shown below. After editing, click Save.

You can:

• Modify the event name.

• Add new properties.

• Change whether predefined and non-predefined properties are required. For order events, you cannot change whether predefined properties are required.

• Modify the names of non-predefined properties.

• Delete non-predefined properties. You can only delete non-predefined properties that are not used by any marketing campaigns.

Delete an event

You can delete custom ingestion events that have not been used in any marketing campaigns.

• Single deletion: Click Delete and confirm the deletion to delete the event.

• Batch deletion: Select the events to delete from the list, click Batch Delete at the bottom of the list, and confirm the deletion to delete the events.

Event grouping

You can create groups for events to manage them by category.

Enhanced Message Unsubscription

Background: Compiles a list of users who unsubscribe after receiving card or digital messages, enabling you to switch to a more suitable contact method. Returned information includes the SMS signature, unsubscribed mobile number, and unsubscribe time.

1. In the upper-right corner of the page, click "Organization Management", click "Organization Settings", and then select the workspaces to receive unsubscribe events for SMS signatures.

2. Click "Configuration Management" > "Event Hub".

3. Click the "Storage" switch to enable storage.

4. You can set up corresponding marketing policies in Automated Marketing.

FAQ