Behavioral user segments

CleverTap builds user segments from recorded events and properties, such as recent purchases, app opens, or inactivity over a set period. A Beam agent reads a user's segment membership when a triggering event occurs, such as a purchase or a support interaction logged elsewhere, and checks it against an approved rule for where that user should sit. Where the rule applies, the agent moves the user into the correct segment or updates a property directly. Users with conflicting or incomplete event data, or segment changes tied to opt-in status, are routed to a person to confirm before anything changes.

Campaign engagement events

CleverTap logs how each user responds to a push, email, or in-app campaign, recording opens, clicks, and dismissals. A Beam agent reads these engagement events after a campaign runs, checking them against an approved rule, such as suppressing further sends to a user who has not engaged across a set number of campaigns. Where the rule applies, the agent updates the user's status so future campaigns exclude or include them accordingly. Users with mixed engagement signals, or those flagged for a required opt-out, are routed to a person before any suppression list is changed.

Journey progression

CleverTap journeys move a user through a sequence of messages based on their behavior, such as completing or skipping a step. A Beam agent monitors a user's position in a journey and checks it against an approved rule, such as advancing or exiting the journey once a specific action happens elsewhere, like a completed purchase. Where the rule applies, the agent updates the user's journey status directly in CleverTap. Requests to redesign a journey's steps or messaging are routed to a person, since the agent only manages progression, not journey content.