Behavior event component
The behavior event component triggers the marketing canvas flow when a user performs a specified action. Place it immediately after the start node.
For example, a user enters the flow after browsing a specified H5 page twice.
Behavior event data is collected by your apps, mini programs, or web pages and reported to Quick Audience, or synchronized from modules such as Member Hub and Social Interaction. Configure event reporting through Event reporting (new version) or Event management (old version).
Procedure:
-
Click the behavior event component in the flow to open the configuration panel on the right.
Parameters
Description
Event Source
-
Event reporting (new): select an event source type.
-
Event management (old version): select the event source channel name.
Event Name
Select the target event.
Restriction Attributes
Filters the event by property conditions.
Turn on Limit Attributes and configure attribute conditions. Example: total purchase amount greater than 10,000 and recipient city is Hangzhou.
Click Add Attribute to add conditions. Multiple conditions support AND or OR logic — click the connector text on the left to switch.
Event Aging: Select a time attribute field to determine event validity. For example, if the time attribute value is V1, the current time is V2, and the relative trigger time is set to 30 minutes before:
When V1 falls within V2−30 minutes: the marketing canvas processes the event normally.
When V1 falls outside V2−30 minutes: the marketing canvas ignores this event.
Limit times
Requires a user to meet the event and property conditions a specified number of times before entering the flow.
Turn on Limit Times and enter the required count.
Activity Participation Restrictions
-
Single participation: each user can enter the flow only once.
-
Multiple participation: each user can enter the flow up to Y times within X days. The count resets after X days.
Event judgment component
Matches between events
-
Based on user ID
-
Based on a specified attribute of the current event
Select "based on a specified attribute of the current event" when a single user has multiple business records that require separate marketing (for example, multiple unpaid orders). Configure the attribute that represents the order ID. The system matches subsequent event judgments by comparing this attribute value with the order ID in the payment event — only matched records proceed to downstream nodes. If the attribute value is empty in a reported event, the event does not trigger the marketing automation. If the same user reports an event multiple times with the same attribute value, the event is processed only once. To process repeated events independently, select "Based on user ID" instead.
-
-
Click OK.