Currently, we have integrated Klaviyo and Shopify to be able to see the track the events through our website.
Now that we have iOS app, we want to be able to track similar events from the app and aiming to see them landing on the same metric, which is setup for website (i.e. via Shopify Integration).
But, we are seeing that despite the iOS app using the same event name as Shopify integration is using (for example, Placed Order), we are seeing that the events from the iOS app are being considered as a part of a separate metric.
The iOS app is sending tracking events to Klaviyo through tracking API - documented here.
Can you please clarify on how the iOS app should send the events so that the events appear in the existing metric for Shopify?
Welcome to the Community! Thanks for sharing your question with us!
Definitely understand the confusion here, would love to clear that up! Although a custom event has a similar name as an in-house integration, they will never be ‘grouped together’ or be merged into the original or existing ‘placed order’ event because they are inherently different. It won’t fall under your Shopify’s ‘Placed Order’ Event because essentially it’s not the event, although it is meant to mimic or be similar to it. Essentially, when the custom event is pushed to Klaviyo, Klaviyo sees it as an API source. Whereas with our in-house integrations, their source is essentially set to those platforms.
To gain more insight into this, I’d check out our developer documentation on tracking custom events.
Welcome to the Community! Thanks for sharing your question with us!
Definitely understand the confusion here, would love to clear that up! Although a custom event has a similar name as an in-house integration, they will never be ‘grouped together’ or be merged into the original or existing ‘placed order’ event because they are inherently different. It won’t fall under your Shopify’s ‘Placed Order’ Event because essentially it’s not the event, although it is meant to mimic or be similar to it. Essentially, when the custom event is pushed to Klaviyo, Klaviyo sees it as an API source. Whereas with our in-house integrations, their source is essentially set to those platforms.
To gain more insight into this, I’d check out our developer documentation on tracking custom events.