Judgment Condition-Event Judgment Component

Updated at:
Copy as MD

The event judgment component filters users based on whether they performed a specified behavioral event within a given time period, and routes them to different subsequent actions.

For example, you can send a text message to a user who does not register the app within one day.

Note
  • Behavioral event data is collected by 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).

  • Whether the workflow starts from the event judgment component or the target audience component, users entering the workflow are matched by their QAID against the user ID reported by the event.

To configure the event judgment component, perform the following steps:

  1. Click the Event Judgment component and configure it in the panel that appears on the right, as shown in the following figure.

    image

    Item

    Example value

    Triggered Time

    The time to wait before checking whether a user has performed a specified behavioral event. You can set a relative time or a specified time.

    • Relative time: After the previous component finishes, the system waits for a specified duration before checking. The unit can be minutes, hours, or days.

    • Specified time: The system waits until a specific point in time to check.

    • Note

      If the specified time has already passed when the user enters the "Test Target" node, the system checks immediately without waiting.

    The source of the event

    Event Name

    Select an event.

    You can filter up to eight events at a time. Click Add Condition to add an event. Multiple events support the AND or OR relationship. Click the operator text on the right side of a condition to switch between them.

    Restriction Attributes

    Set event property requirements for filtering.

    Turn on the Limit Attributes switch and configure the required event attributes.

    Click Add Attribute to add an attribute condition. Multiple attribute conditions support the AND or OR operation. Click the operator text on the right side of a condition to switch between them.

    Limit times

    Require the same user to meet the event and property conditions a specified number of times.

    Turn on the Limit Times switch and enter the number of times.

    Select behavior

    Select Occurs or Not Occurs:

    • Occurrence: Users who have met the event requirements for attributes and frequency enter the subsequent workflow branch.

    • Not Occurs: Users who do not meet the event, attribute, or frequency requirements enter the subsequent workflow branch. This includes users who triggered the event but did not meet the attribute or frequency criteria.

    Note

    When multiple attributes are restricted: if the relationship is "and", failing any single attribute counts as unsatisfied; if the relationship is "or", all attributes must fail for the condition to be unsatisfied.

    image

  2. Click OK.