V4.2.0 Version Guide
V4.2.0 supports custom user ID types and policies for ID Mapping. This version also introduces three new types of custom tags and two new components for Automated Marketing.
Release time
Updates
This release includes updates for V4 only.
V4 updates
ID Mapping:
The system uses the ID Mapping process to identify users and consolidate user data across different source channels and ID types. For more information about the logic of ID Mapping, see ID Mapping and User Unique Identifier QAID.
This version allows administrators to add and manage user ID types supported by Quick Audience and configure policies that determine which IDs participate in ID Mapping. For more information, see Identity Field Management.
User Insights:
User Tag now includes three new types of custom tags:
Loyalty Tags: Based on data from the user behavior table and order details table, these tags use the time of a user's last or first behavior, the number of days since that behavior, or the total number of days with behavior as the tag value. Examples include the time of or number of days since the last purchase or visit, and the total number of spending or active days.
Purchasing Power Tags: Based on data from the user behavior table and order details table, these tags use statistical values of a user's order amount, order count, or interaction behaviors as the tag value. Examples include the total purchase amount, number of items purchased, or number of orders in the last year, and the average, maximum, or minimum order amount.
User Stage Tags: Filter users based on your required user segmentation logic, similar to Audience Filter. This process identifies users who meet different conditions and assigns them distinct segmentation tags. For example, you can filter for users with a total purchase amount of ≥ 1000 who are interested in food and assign them the "Marketing Priority 1" tag. You can also filter for users with a total purchase amount between 100 and 999 who belong to Audience A and assign them the "Marketing Priority 2" tag.
Automatic snapshot generation is supported when an audience is automatically updated. For more information, see Updates and Snapshots. You can copy the snapshot table name to query the snapshot table. For more information, see Snapshot Management.
You can embed reports created in Quick BI into the marketing campaign page in Quick Audience for visual analytics of campaign data. For more information about how to embed reports, see Embed Quick BI Reports.
User Marketing:
SMS Marketing now supports ingesting and managing user replies received from third-party SMS platforms. For more information, see Message Reply. You must first enable the mobile originated message receiving feature when you Create a Third-party SMS Platform API. The third-party SMS platform API must also include a text message reply query API.
The PUSH task in private marketing, and the WeChat Official Account Message Component and APP PUSH Component in Automated Marketing all support inserting variables into content. This enables you to send targeted content based on the tags or behavior event properties of recipient users.
Automated Marketing upgrades:
New component types: The Push to Kafka component is used to push user IDs to Kafka. The A/B Test component is used to compare the effectiveness of different plans.
The campaign configuration canvas now includes Undo and Redo buttons. It also supports copying and pasting components and their subsequent paths. For more information about these operations, see Create Automated Marketing Campaign.
Marketing campaigns now support version management. Editing a campaign may create a new version. For more information, see Edit a Campaign.
For the Text SMS and Digital SMS components, you can save users from successful or failed sends as an audience on the action analysis page. For more information, see View Campaign Execution Status.