Skip to main content

We offer a subscription service and use Recharge as our subscription platform. This presents a problem when it comes to revenue attribution in Klaviyo. Whenever a subscription order is created in Recharge/Shopify, if that subscriber opened or clicked an email from us within the attribution window, Klaviyo counts it as revenue attributed to that email. This skews all of our reporting very significantly, and it makes it nearly impossible to see how our campaigns and flows are actually performing from a revenue standpoint.


Klaviyo tells me that excluding Recharge customers from Klaviyo’s analytics is a commonly requested feature, but that there is not currently a way to do this outside of creating custom reports that exclude Recharge customers. Unfortunately this would be more of a workaround than a solution, and would require a lot of manual upkeep.

Is anyone else experiencing this issue, and if so, have you found a way to overcome it?

Hi @Sea to Table,

Welcome to the Community and thank you for sharing this and getting the discussion started.

Unfortunately, there is not way via the Shopify Integration to separate out recurring revenue (i.e subscriptions) and a one time order.
The Klaviyo <> ReCharge integration helps in identifying an active customer on subscription, but unfortunately the revenue is still attributed under the Shopify Placed Order revenue. 
Since all the revenue is coming in through a single metric, it will be hard to differentiate between these.
 

When calculating revenue, Klaviyo cannot decipher between Shopify Placed Order metrics that were placed independently of a ReCharge subscription. They all appear as the same type of Shopify Placed Order metrics within Klaviyo. That said, the ability to filter out recurring subscriptions is a widely requested feature, and I have submitted your valuable feedback to our Product Team for future consideration. 

In the meantime, a workaround would be to create a completely separate custom order event that only fires for non-recurring placed orders. Then, you could use that custom event in reporting. This requires knowledge of APIs and custom coding to pass custom placed order events into Klaviyo that exclude ReCharge events. Once Klaviyo has received this information, you could use this custom event as your metric for measuring revenue / conversions. If you want to explore this option, please refer to our guides for sending custom events into Klaviyo: 
 

Guide to Integrating a Standard Ecommerce Platform

Getting Started with Klaviyo APIs

Track and Identify API Reference

How Information Is Exchanged between Klaviyo and Apps

API Overview

 

If you do not have access to a developer, then please consider our robust community of partner agencies to assist with this. You can browse our Klaviyo Agency Directory to decide which option is best suited for you.

 

All the best,

Alex


The same thing happens with Appstle Subscriptions


Was this issue ever resolved? We’re dealing with the same inflated revenue attribution and haven’t been able to find a solution. 

 


Hey @beau_ss,

At present, it’s not possible to filter out certain orders from attribution. As @alex.hong mentioned, this has to do with subscription orders still triggering an order event - which most brands use as their conversion metric. 

Creating your own custom event - in my own experience, has been the most accurate method to distinguishing net new orders versus a recurring subscription order. This way, instead of using the Shopify Placed Order event as your conversion metric, you can use the custom event you created. 

Another method I’ve found some users set up is a reminder flow for users with subscription orders when their order is about to renew. Since there’s a high likelihood users are going to open this reminder email, attribution for the recurring order will fall to this reminder email. You can then subtract the overall attributed revenue by the attributed revenue from that particular flow/email to give you a better idea of how well your emails are performing. 

David

 


Reply