Custom Klaviyo Segments

Level up your email communication with personalized messages based on specific subscription behavior. Using the events that Ordergroove sends to Klaviyo, you can set up custom segments like customers who skipped an order or only subscribers who receive their third order

In this guide we'll go through setting up a segment with Ordergroove data, and an overview of popular flows.

 


Using Ordergroove Data in Segments

Ordergroove automatically adds subscriber and subscription events to two segment categories:

  • What someone has done (or not done)
  • Properties about someone

All of our events start with Ordergroove.[event], for example:

  • ordergroove.subscriber.create
  • ordergroove.order.skip_order

CleanShot 2024-03-21 at 17.12.08@2x_clean.png


Using Specific Products

Right now, you can not create segments around specific products, SKUs, or product IDs in your Klaviyo flows without a workaround. Klaviyo only accepts top-level properties, and elements like product ID are nested in items_subset.

Klaviyo published a workaround with webhooks. Note: This is outside of Ordergroove support and will require a developer or technical resource from your team to implement.


Popular Klaviyo Flows

All Subscribers

Surprise and delight your active subscribers with exclusive releases, sneak peeks, or sales.

Backfilling Data

You will need to manually backfill subscriber status to use this flow after you set up your Klaviyo integration. Take a look at How to backfill subscriber status for instructions.

You can use subscriber status to create a segment with all current subscribers:

  • Properties about someone
  • ordergroove_subscriber_status
  • equals
  • Active

CleanShot 2024-03-28 at 14.54.06@2x.png

Customers who have skipped shipments

Reduce churn by encouraging frequent skippers to modify quantity or frequency instead of skipping another shipment.

We can use subscriber status and order - skip order to find customers who have recently skipped shipments. In this example it's all customers who have skipped one or more shipments in 30 days, but you can adjust the amount of skips and the date range in order.skip_order:

  1. ordergroove_subscriber_status
    • Properties about someone
    • ordergroove_subscriber_status
    • equals
    • Active
  2. and
  3. ordergroove.order.skip_order
    • What someone has done (or not done)
    • ordergroove.order.skip_order
    • at least once
    • in the last
    • 30
    • days

CleanShot 2024-03-28 at 16.31.54.png

When a subscriber hits X orders (Nth Order)

Build customer loyalty by sending out milestone emails when they hit a certain threshold.

We can build a segment based on successful orders to make a segment that automatically adds subscribers who hit a specific # of orders. For example, you might want to send a loyalty email after a subscriber receives their third shipment.

Two things to keep in mind when following this template:

  • This will count the total number of orders, not a specific product.
  • We set a date limit to rule out subscribers who have been in the program for a while and are already past the order threshold. 

Here's how to set it up:

  1. ordergroove_subscriber_status
    • Properties about someone
    • ordergroove_subscriber_status
    • equals
    • Active
  2. and
  3. ordergroove.order.success
    • What someone has done (or not done)
    • ordergroove.order.success
    • is at least
    • 3
    • after
    • 01/01/2024
  4. and
  5. ordergroove.subscription.create
    • What someone has done (or not done)
    • ordergroove.subscription.create
    • at least once
    • after 
    • 01/01/2024

Active Ordergroove Subscribers to a specific product

You can set up a segment that captures subscribers to specific products.

Limitations:

- This segment will not find subscribers who have reactivated a previously canceled subscription

Here's how to set it up:

  1. ordergroove_subscriber_status
    • Properties about someone
    • ordergroove_subscriber_status
    • equals
    • Active
  2. and
  3. ordergroove.subscription.create
    • What someone has done (or not done)
    • ordergroove.subscription.create
    • equals
    • 1
    • for all time
    • Filter: product_name 
    • is in
    • <select products>
  4. and
  5. ordergroove.subscription.cancel
    • What someone has done (or not done)
    • ordergroove.subscription.cancel
    • equals
    • 0
    • for all time
    • Filter: product_name 
    • is in
    • <select products>

 

CleanShot 2024-11-06 at 14.42.25.png