Hey hey, we missed some metric data related to the “Placed Order” event that we need to basically re-sync. We’re integrated via custom API, and we don’t see a way to do this without completely removing the event + details. However, we have flows set up that are triggered via that event that we don’t want to lose. How do we essentially overwrite existing metrics under that event without completely removing/re-uploading?
Any thoughts?
Best answer by saulblum
View original
+7
Hi
For the most part, Klaviyo is pretty flexible with events and event properties. If you’re just using the API, you can send whatever properties you want for the event.
Can you explain more about how you’re setting up the event? Are you working with a Shopify integration, for example?
Best,
Kevin.
Hey
We’re on a custom site. The issue is we’ve already synced up historical data, and we don’t see a way to be able to just overwrite those events so we can include the data we missed.
Thanks
+7
Hey
I don’t think this is possible... Check out this similar thread:
Hey
Do you have any other ideas as to how we can accomplish getting that missing data associated with the event? We’re not totally live yet, so we’d really like to make sure we’re totally good to go before final launch.
If the account isn’t live yet, your best bet is to delete the Placed Order metric entirely and redo any historical imports with the correct event properties. You can’t delete or edit events already associated with profiles.
If you have flows triggered on the metric, you should be able to re-setup the flows’ triggering metrics after you re-import and recreate the events. (Even though the new metric is called Placed Order, it’s possible the internal IDs would be different meaning it’s actually a new metric.)
Hey
Hey
Not sure, tbh. Kind of an edge case, to have profiles going through a flow when the underlying triggering metric for the flow is changed. If it is a new metric (even with the same name, but different ID), it’s possible any emails remaining to be sent in the flow might fail, if the underlying {{ event }} object isn’t valid anymore.
So, yes, #1 you need to rethink how you are thinking about Klaviyo as a data storage device. It is not a typical database where you insert/update/delete records, at least on the event side. But the fact that there is old erroneous data isn’t important as you can make a flow that ignores these.
#2 if the even name is wrong just resubmit using the right event name. You can also contact Klaviyo CS and request that all data under a certain event name is wiped out. If the data in the event is wrong just resubmit the events with the right data and have your flows/reports ignore any event before the second import.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
