Klaviyo V2 FAQ
Klaviyo V2 is a powerful integration built by Recharge that lets you utilize Klaviyo to automate your marketing campaigns. With the use of Recharge metrics and customer properties, you can now send notifications from Klaviyo to your subscription customers.
Klaviyo V2 can be used on its own, or you may want to consider adding Recharge Quick Actions to your flows and campaigns if you are a Shopify merchant. These URLs let your customers interact with their subscriptions outside of the customer portal. See Recharge Quick Actions to learn more.
For more help, see troubleshooting Klaviyo and troubleshooting Quick Actions.
Are one-time products included in the active subscriber property?
No, the active subscriber property considers an active subscriber to be any customer with one or more subscriptions. Purchasing a one-time product does not count towards a subscription, so customers who check out with these products are not considered active subscribers.
Is it possible to pass line item properties to Klaviyo?
Line item properties for a subscription are passed from Recharge to Klaviyo via the API for the following metrics:
- Order (prepaid) upcoming on Recharge
- Order upcoming on ReCharge
- Started Checkout
Line item properties are not passed for the “Subscription started on ReCharge”, “Subscription expired on ReCharge”, or “Subscription cancelled on ReCharge” metrics, as the subscription object is not passed for these events.
For emails using metrics where line item properties aren’t passed, you can customize your notifications to include specific if variables/conditional statements that include specific product images or details depending on the customer’s order, however, this workaround is outside of our scope of support.
When are metric properties used versus customer profile properties?
Metric properties are used to create trigger splits in Klaviyo. Customer profile properties are used to create conditional splits.
Do any events update custom properties?
Yes, the skipped, unskipped, and swapped events all update customer properties for the customer.
The swapped event only works at the product level at this time, where product swaps are tracked but not variant swaps.
