Skip to content

Core Concepts

Events and flows

How Cadence sends events to your marketing platform and how you set up flows to deliver messages to customers.

Cadence does not send emails or SMS directly. Instead, it sends events to your connected marketing platform, and your flows (automations) in that platform send the actual messages. This doc explains the event model and what you need to set up in your marketing tool.

The event model

When a customer has an active prediction, Cadence sends a single event to your marketing platform:

Event name: cadence_prediction

Key property: prediction_type — tells your flow which type of prediction triggered the event.

prediction_type value Prediction
due_to_replenish Replenishment
about_to_lapse Lapse prevention
primed_for_cross_sell Cross-sell
primed_for_subscription Subscription upsell

Event properties

Each event includes properties your flows can use for personalization:

Property Description
prediction_type One of the four values above
product_name Name of the primary product
product_url URL to the product page
cart_url Pre-built ConvertCart link for this prediction
customer_email Customer’s email address
customer_first_name Customer’s first name

Additional properties may include product image URLs, prices, discount information, and subscription details depending on the prediction type.

Setting up flows in your marketing platform

You need to create one or more flows/automations in your marketing platform that trigger when the cadence_prediction event is received. Most stores create separate flows per prediction type.

Create four flows, one per prediction type:

  1. Replenishment flow — triggered when prediction_type equals due_to_replenish
  2. Lapse prevention flow — triggered when prediction_type equals about_to_lapse
  3. Cross-sell flow — triggered when prediction_type equals primed_for_cross_sell
  4. Subscription upsell flow — triggered when prediction_type equals primed_for_subscription

Each flow should:

  • Use the event properties for personalization (product name, customer name, cart URL)
  • Include the cart_url as the primary CTA link (this opens ConvertCart)
  • Be set to Live (not draft) before your store goes live

Platform-specific setup

Platform Where to create flows Trigger type
Klaviyo Flows → Create flow → Metric trigger Metric: cadence_prediction
Omnisend Automation → Create automation → Custom event trigger Event: cadence_prediction
Attentive Journeys → Create journey → Custom event trigger Event: cadence_prediction
Postscript Automations → Create automation → Event trigger Event: cadence_prediction

See the Integrations section for detailed setup instructions per platform.

Profile properties

In addition to events, Cadence syncs profile properties to your marketing platform for each customer. These properties are prefixed with cadence_ and update daily.

Common profile properties include:

Property Description
cadence_due_to_replenish Whether the customer has an active replenishment prediction
cadence_about_to_lapse Whether the customer has an active lapse prediction
cadence_replenishment_cart_url ConvertCart link for replenishment
cadence_replenishment_product_name Product name for replenishment
cadence_lapse_cart_url ConvertCart link for lapse prevention
cadence_cross_sell_cart_url ConvertCart link for cross-sell

Profile properties enable you to:

  • Segment customers in your marketing platform (e.g., “all customers due to replenish”)
  • Personalize campaigns using dynamic content blocks
  • Power LiveBlock in email templates (see LiveBlock)

Profile sync begins when your store is enabled and runs daily alongside event delivery.

Event delivery timing

Events are delivered once per day at your configured event delivery time (set in Settings). All active predictions for all customers are sent in a single batch at this time.

Default delivery time is configured during enablement. You can change it in Settings → Event delivery time.

Events are not sent in real-time — they batch daily. This means a customer who becomes eligible for a prediction today will receive the event at the next delivery window.

Multiple marketing platforms

If you have multiple marketing platforms connected (e.g., Klaviyo for email and Attentive for SMS), events are delivered to all connected platforms. You can run parallel flows in each platform — email flows in Klaviyo and SMS journeys in Attentive, both triggered by the same cadence_prediction event.

What Cadence does not do

  • Cadence does not create flows for you — you build them in your marketing platform
  • Cadence does not design your email templates — you control all creative
  • Cadence does not manage send frequency beyond the daily batch — your flow logic controls how often a customer receives messages

Where to go next