An event judgment component is used to filter out users who have performed or have not performed a specified behavioral event within a specified period of time and perform subsequent operations.
For example, if a user does not register the APP within 1 day, send a text message to him.
User behavior event data is collected by applications such as apps, mini programs, and web pages and then reported to Quick Audience. For more information, see Event Reporting (New Version) or Event Management (Old Version).
Regardless of whether the link starts from the event judgment component or the target audience component, the user entering the process will use its QAID to match the user ID reported by the event.
To configure a universal filter, perform the following steps:
Click the Event Judgment component and configure it in the panel that appears on the right, as shown in the following figure.

Item
Example value
Triggered Time
Specifies the time to wait before determining whether a user has performed or has not performed a specified behavior event. You can set a relative time or a specified time.
Relative time: After the user finishes executing the previous component, wait for a period of time before judging. The unit can be minutes, hours, or days.
Specified time: Wait until a specific time point, and make a judgment at this time point.
NoteFor the specified time, if the specified time point has passed when the user enters the "Test Target" node, it does not wait and directly determines.
The source of the event.
For Event Reporting (New Version), select an event source type.
For Use Event Management (Old Edition), select the name of the event source channel.
Event Name
Select an event.
You can filter a maximum of eight events at the same time. You can click Add Condition to add an event. Two events support the AND OR OR relationship. You can click the corresponding text on the right side of a condition to switch between them, as shown in the following figure.
Restriction Attributes
Supports setting event property requirements.
Turn on the Limit Attributes switch and configure the required event attributes.
You can click Add Attribute to add an attribute condition. Multiple attribute conditions support the AND OR OR operation. You can click the corresponding text on the right side of a condition to switch between them.
Limit times
Supports the setting that the same user needs to meet the event and property requirements multiple times.
Turn on the Limit Times switch and enter the number of times.
Select behavior
Select Occurs or Not Occurs:
Occurrence: A user who has met the required attributes and times of the event enters the subsequent link.
Not Occurs: Users who do not meet the requirements for events, attributes, and times enter subsequent links, including users who have occurred but whose attributes or times are not met.
NoteWhen there are multiple restricted attributes, if the relationship between the attributes is "and", any attribute is not satisfied as an unsatisfied attribute; if the relationship between the attributes is "or", all attributes are not satisfied as an unsatisfied attribute.

Click OK.