The pattern that maps a specific observed event (cart add, page view threshold, content download, support contact) to a downstream activation, with rules for debouncing, eligibility, and contextual variation. The simplest activation primitive in the stack, and the one most often implemented as a one-off integration that calcifies into the architecture before it can be generalized.
The capability a stack needs to run this pattern, and the vendors that provide it, on Martech Stack Builder.
Recognize tenure and usage milestones with a touch that reads as personal rather than as a template with a date merged in
Warn the customer before the overage, the roaming charge, or the plan-mismatch cost lands on the bill, so the conversation is about what to do next rather than about why the bill is what it is
Recover the buy-online-pickup-in-store orders that the customer placed and never collected, with the cross-system identity and the in-store inventory signal that the recovery has to coordinate around
Follow up with shoppers who viewed products but never added to cart, filtering out the low-intent browsers so the sequence does not dilute itself
Recover the abandon that happened on the phone and the purchase that continues on the laptop, as one customer rather than two
Surface adjacent products in the rhythm of how the original item is actually used, instead of dumping every cross-sell into one email
Surface contextual conversion prompts at the moments most likely to convert the willing-to-pay player, without breaking the free experience for everyone else who is the reason the game has an audience at all
Catch the customer just short of the next tier and give them a real reason to cross it, anchored on their current balance rather than a guess
Advance the onboarding sequence on what the user actually did in the product, not on a fixed timer that ignores their progress
Time the reorder reminder to the customer's own consumption cadence, not a category-wide average that is wrong for most of them
Fire a sales-owned outreach when the product-usage pattern signals real buying intent, with the orchestration between product analytics, CRM, and sales-engagement that keeps the message credible
Match the content sequencing to the long consideration cycle the traveller is actually on, with the price-sensitive decision moment at the end where the booking either happens or moves to a competitor
A three-message email sequence triggered by abandonment, gated by consent and channel eligibility