Ordergroove has recently released an updated, revamped version of our Klaviyo integration using Klaviyo's current APIs. Klaviyo is going to deprecate their previous APIs, storeowners will need to migrate to our new Klaviyo integration before then to continue using the platform.
Check your integration version
There are currently two versions of Ordergroove's integration with Klaviyo; legacy will stop functioning when Klaviyo deprecates the old APIs.
Not sure which integration you are using? If you have any flows that are using metrics called "OG [Event Name]", those are from the legacy integration. Metrics that follow "ordergroove.[event name]" are from the new integration.
Please note that it's possible to have both integrations sending data into your Klaviyo account, and you may have some flows set up with the legacy metrics and others that use the new metrics.
Step 1 - Install the new Klaviyo Integration
Install the new Klaviyo integration and add your unique Klaviyo API key to the Ordergroove integration. We go through the steps and permissions necessary in Klaviyo integration overview.
Step 2 - Update your Flows
Follow the steps below to update any flows that use metrics from the legacy Klaviyo integration. Each legacy flow needs to be cloned, and have the variables updated.
Default Event Mappings from Klaviyo V1 to V2
note: your Klaviyo v1 metrics may be different than what is listed here.
| Klaviyo v1 Metric | Klaviyo v2 Metric |
| OG Order Reminder | ordergroove.order.reminder |
| OG Subscription Started | ordergroove.subscriber.subscriptions_created |
| OG Subscription Canceled | ordergroove.subscription.cancel where cancel_reason does not equal item discontinued |
| OG Product Discontinued | ordergroove.subscription.cancel where cancel_reason equals item discontinued |
| OG Subscription Reactivated | ordergroove.subscription.reactivate |
| OG CC Expiration Warning | ordergroove.order.credit_card_expiration_warning |
| OG Product Discontinued - Replaced | ordergroove.subscription.sku_swap |
| OG OOS 1 Day | ordergroove.item.out_of_stock where days_since_first_attempt = 1 |
| OG OOS 15 Day | ordergroove.item.out_of_stock where days_since_first_attempt = 15 |
| OG OOS 30 Day | ordergroove.item.out_of_stock where days_since_first_attempt = 30 |
| OG CC Expired | ordergroove.order.reject where rejected_code is in 500,120 |
| OG Order Declined Payment | ordergroove.order.reject where rejected_code is in 110,140,100,130,160 |
| OG Order Declined | ordergroove.order.reject where rejected_code is not set or not in 500,120,110,140,100,130,160 |
Clone the flow
You can't update a flow's trigger after it's created, so we have to clone the flow before we update it.
- Log in to Klaviyo.
- Go to Flows, locate the flow you want to update, click the 3 dots menu over to the right, and select Clone.
- Give your cloned flow a name, and select an appropriate trigger.
- Note: You currently have both legacy and new installed, so you will see two similarly named triggers. Here's one example: OG Order Reminder and ordergroove.order.reminder. Select the trigger that starts with ordergroove. - these are the new triggers in the new Klaviyo integratoin.
- Click Clone Flow.
Update the variables
With your flow cloned, now we need to update the variables.
- Open up the cloned flow.
- Select the first email or SMS message and click Edit.
- Each of the variables needs to get replaced - anything between curly brackets {{ }}. To view the new variables, click Preview & test. Scroll down in the sidebar to view all of the new variables. Take a look at the image below for an example.
- Note: If you're working on a template that can display multiple items, such as subscription products, you will need to add a repeat rule to display all of the individual items. You can learn more in Step 4 of How to build an Order Reminder flow in Klaviyo and Klaviyo's documentation.
- Click Preview and test to double-check that the variables display correctly. If everything looks correct hit Save.
- Open up and edit the remaining Email and SMS messages to replace the variables.
Step 3 - Disable Legacy Klaviyo
When you have the new Klaviyo integration installed and your flows converted over to the new events, the last step is to let Ordergroove know.
Reach out to your Success Manager or send us an email, and we'll disable the legacy Klaviyo integration. If you leave both active, your customers will receive a second duplicate email for every flow they trigger.
Additional Support
If you have any questions or want a second set of eyes on your work, please reach out to your Success Manager or Ordergroove support and we'll be happy to help.