Hi @Cali, welcome to the community,
This may not be the best approach, but one to consider if you can’t figure out a workaround.
Is it possible to load your POS order data as “Orders” into Shopify which then subsequently gets pulled into Klaviyo as a Shopify metric?
Shopify’s API let’s you put orders into its system here:
Hi @retention - That’s an interesting workaround thanks for the suggestion. However we would ideally like to keep the POS metrics distinct so we can measure revenue separately by channel, so I’m hoping to find a solution which allows us to aggregate CLV across metrics.
Hi @Cali , one way to do this would be to use the Klaviyo APIs to poll both metrics you want to combine, relay them to a new, combined metric, and use that metric for calculating CLV. The relevant APIs would be https://developers.klaviyo.com/en/reference/get_events and https://developers.klaviyo.com/en/reference/create_event.
I work at Klaviyo and am currently working on an initiative we’re calling Klaviyo Code. We’re working to integrate a product we acquired, napkin.io, into Klaviyo. One of the use cases we’ve identified is just the one you’re facing.
Would you be interested in discussing Klaviyo Code and how it could help with your use case? If so, I’ll send you a DM with details.
Hi @ezra - Thanks for the reply. That sounds like a cool idea. Definitely keen to explore Klaviyo Code further so any further details you can provide would be appreciated. Thanks!
@Cali,
I think even webhooks can help here but the most important thing is how will you be using CLV? Where will you be reporting on it and how do you expect to use it in Klaviyo?
The reason I'm asking is depending on what you'll be doing it can also make sense to have an external database (i.e. bigQuery) that has this data in it. For POS I can imagine you won't always have email address in there (which is the unique key in Klaviyo) and have that database push data back in Klaviyo.
As for the webhooks, why not have a new property called “combined CLV” that adds (or deducts) revenue on a placed order. I've not tested this but could be an in between solution.
{
"token": "your-api-code",
"properties": {
"$email": "{{ person.email }}",
"Combined CLV": {{ person|lookup:'Combined CLV'|default:0|add:'{{event.revenue}}'}}
}
}
Omar Lovert // Polaris Growth // Klaviyo Master Platinum Partner
We help with e-commerce growth through CRO, Klaviyo and CVO
@Omar - We plan to use combined CLV in Klaviyo to drive loyalty segmentation. In this case we have a loyalty program which is based on lifetime spend across both POS and eComm - currently it is a very manual process of working out which tier people belong in - so we’re looking to automate that.
Will look into the webhooks idea thanks - that could be a good solution.
@Cali - this week we’ve just done what you’re planning. We’ve created a separate metric that is meant to be omni channel. We’ve added orderSource
(store, shopify, magento, etc) and OrderChannel
(ecommerce, in-store, etc) so we could know what system the order came from and how it was handled.