Using Klaviyo with Flows
The Flow triggered on Recharge metric sends customer and order information to Klaviyo about customers who enter your flows associated with a specific Revenue Tool.
This guide explains how you can use this metric to send customers branded notifications about flow events with Klaviyo flows.
- Shopify Checkout Integration
- Migrated Shopify Checkout Integration
Before you start
- Review the Klaviyo overview guide to understand how Klaviyo works with Recharge.
It is recommended you work with a Klaviyo Recharge partner when implementing customizations.
How it works
When creating certain flows you can replace the Recharge notification node and add a Klaviyo node so that notifications are sent from Klaviyo instead of Recharge. You can add the Klaviyo node to your Rewards or Upcoming Order Cross-sell flows.
The Klaviyo node sends the Flow triggered on Recharge metric to Klaviyo so that Klaviyo has the necessary information to create your notifications. This metric contains customer and order information, plus information about the Rewards incentive.
Recharge sends this metric to Klaviyo when the event outlined on the flow canvas before the Klaviyo node in a flow occurs.
The customer, incentive, and order properties that Recharge sends to Klaviyo depend on where you position the Klaviyo node within your canvas when designing an flow. For instance, placing the Klaviyo node before the incentive node in a flow means that incentive event properties won’t be available for segmentation in Klaviyo, as the incentive has not yet occurred. See Flows metrics for a list of available metrics and their related properties.
Use cases
The following use cases highlight how you can use the Flow triggered on Recharge metric to send customers customized and branded notifications.
Use case |
Example |
| Confirmation of cross sell |
Leverage the Klaviyo node and send the Flow triggered on Recharge metric to Klaviyo after a customer successfully adds a cross-sell product to their upcoming order. You can then use this data to automatically send customers polished, branded notifications confirming that the new product has been successfully added to their upcoming shipment. |
| Free gift notification |
Leverage the Klaviyo node and send the Flow triggered on Recharge metric to Klaviyo when you automatically add a free gift to a customer's upcoming order. You can use this data to replace the existing Recharge notification with a highly customized Klaviyo notification to let customers know they’re receiving a free gift. |
Add a Klaviyo node to a flow
Add the Klaviyo node to your flow to send the "Flow triggered on Recharge metric" to Klaviyo. This metric is triggered when the preceding event occurs, specifically when Recharge sends the event properties from Recharge to Klaviyo. Follow the steps below to add the Klaviyo node to your Recharge flow:
- Create a flow in Recharge.
- Click the vertical dot menu on the existing notification node, then select delete to remove the Recharge notification node and send emails only through Klaviyo. This is not required if you send both Recharge and Klaviyo notifications.
- Open the Add a node menu on the left-hand side of the flow canvas.
- Select the Klaviyo notification from the Actions tab, then drag it onto the flow canvas to wherever you want the "flow triggered on Recharge" metric to trigger. You can add one node per flow branch.
- Click the node to edit the properties sent from Recharge to Klaviyo. Add any custom event properties here.
- Save the flow.
Build your flow in Klaviyo after saving the "flow triggered on Recharge" metric.
Video tutorial
Watch the video below to learn how to build a Recharge flow using the Klaviyo node:
Build a Klaviyo email flow using Recharge event metrics
Build your Klaviyo email flow in Klaviyo after you've added the Klaviyo node to your flow in Recharge:
- Create your flow in Recharge, adding the Klaviyo node where relevant.
- Save the flow in Recharge to send a mock metric and corresponding data to Klaviyo automatically under the name Jane Doe. Use this test customer to preview properties in Klaviyo emails.
- Create a new email flow in Klaviyo:
- Use the "Flow triggered on Recharge" metric as the flow trigger.
-
Filter by the flow name to ensure the messages you send apply to the specific flow. You can access the flow ID on the Klaviyo notification node in Recharge.
- If you cannot see the flow ID as an option, use the flow name as the filter. Find the name in your flow settings under Flow title.
- If you cannot see the flow ID as an option, use the flow name as the filter. Find the name in your flow settings under Flow title.
- Optional: You can use any additional properties listed to further segment your customers or add custom event properties to show different emails based on A/B branches or splits.
- Add the Klaviyo email action to the flow, and any other actions. You can preview and test your Klaviyo flow to access event properties.
- Save and activate your Klaviyo flow.
- Navigate back to the Recharge merchant portal and perform a test through your Recharge flow to confirm that the Klaviyo flow triggers as expected.
- Activate your Recharge flow.
All flow-related emails are automatically sent through Klaviyo after activating your Recharge and Klaviyo flows.
Video tutorial
Watch the video below for instructions on customizing your notifications and reviewing your notification metrics:
Considerations
Consider the following when using Klaviyo and Recharge:
Consideration |
Notes |
| Notification timing for upcoming charge events | Recharge sends the upcoming charge events to Klaviyo between 1-4 PM ET. After Recharge sends the upcoming charge events to Klaviyo, Klaviyo handles the notifications, which may result in timing variations compared to Recharge's in-house notifications. |
| Event payload size limits for Klaviyo |
Klaviyo enforces a 100KB payload size limit for events sent through their API. To keep event and customer property syncs reliable, Recharge automatically trims certain data only when an event exceeds this limit.
Most merchants will not see any impact on their Klaviyo data or segmentation due to these limits. |
