What is a data-based trigger?

You know that moment when a subscriber upgrades to a higher plan, hits their 500th loyalty point, or changes their shipping address to a new city? None of those are button clicks or email opens. They're changes in who that person is. And that's exactly what a data-based trigger watches for.

A data-based trigger fires an automated email when a field in your customer data changes or crosses a condition you've defined. It's not about what someone did on your website. It's about what's now true about them.

Here are the most common types you'll run into:

• Field value changes. A customer updates their location, plan tier, or profile preferences. Think: someone at captain@deepcurrent.io switches their delivery address from New York to California, and a "Welcome to the West Coast" flow kicks off automatically.
• Threshold reached. A spending total, point balance, or usage count hits a number you care about. "You've just reached Gold status" is a classic threshold trigger.
• Segment entry or exit. When updated data pushes someone into (or out of) a defined segment, the trigger fires. A subscriber who hasn't bought in 90 days crosses into your "at risk" segment and gets a win-back email.
• Calculated field triggers. Derived values like customer lifetime value or an engagement score cross a threshold. These usually live in your CRM or CDP and sync to your ESP on a schedule.

The practical difference between this and an action-based trigger is subtle but important. An action trigger responds to something someone did (clicked a link, abandoned a cart). A data trigger responds to something that became true about them. The same person might trigger both on the same day, for completely different reasons.

To actually build one, you need three things. First, the data field has to exist somewhere your ESP can read it (your CRM, a CDP like Braze, or a custom field in Klaviyo or ActiveCampaign). Second, that data has to update in near-real-time, or at least on a frequent sync, so the trigger fires when it should. Third, you define the condition: field equals X, value exceeds Y, or segment membership changes.

The part people underestimate is data freshness. If your CRM only syncs once a day, your "you've reached Gold status" email might land 23 hours late. That timing gap can make an otherwise great email feel off.

If you're not sure which trigger type fits your use case, the full trigger type overview is a good place to start sorting it out.