The behavior event component is the first component after the start node. When the user executes the specified behavior event, the process enters.
For example, when a user browses a specified H5 page twice, the user enters the process.
User behavior event data is collected by your apps, mini programs, web pages, and other applications and then reported to Quick Audience, or automatically synchronized from the member mid-end, social interaction, and other modules. For more information, see Event Reporting (New Version) or Event Management (Old Version).
To configure a universal filter, perform the following steps:
The Behavior Events component has been added to the flow as the first component after the Start node. Click the Behavior Events component and configure it in the panel that appears on the right, as shown in the following figure.
Item
Example value
Event source
For Event Reporting (New Version), select an event source type.
For Event Management (Old Version), select the name of the event source channel.
Event name
Select an event.
Limit attributes
Supports setting event property requirements.
Turn on the Limit Attributes switch, and then set the event attribute requirements. For example, in the preceding figure, users are required to browse the specified product page and stay for more than 10 seconds.
You can click Add Attribute to add an attribute requirement. Multiple attribute requirements support the,, or relationship. You can click the corresponding text on the left to switch between them.
Limit times
Supports setting the same user to meet the event and property requirements multiple times before entering the process.
Turn on the Limit Times switch and enter the number of times.
Activity Participation Restrictions
Single participation: The same user can enter the process only once.
Multiple participation: The same user can enter the process up to Y times in X days, and restart the calculation after X days.
Click OK.