Historical Attribution and API Order Events

Forum|Forum|1 year ago
March 20, 2025
4 replies
188 views

Will the historical attribution updates that took place this month be reflected in the order-level event data coming from the Klaviyo events API?

They don’t appear to be yet. If I query the order events for a given period a year ago, the returned orders still have the same number of included attributions that they did before we changed the attribution settings.

This is causing over-attribution for historical data that does not match the in platform historical reporting.

Seeing this across all accounts, let me know if there’s a workaround, thanks!

Best answer by Byrne C

Hey @brendanuye,

That’s a great question. I reached out to our engineering team and they confirmed that right now, the Query Metric Aggregates endpoint will return conversions based on the past attribution windows, back when those conversion occurred. It will not currently reflect your current attribution settings that were retroactively applied within Klaviyo. We recognize that this causes an inconsistency in our reporting tools, and we’re working to adjust these endpoints to reflect the attribution settings that are currently applied in your account.

For now, we recommend using the Query Campaign Values and Query Flow Values endpoints (or any of the endpoints in the Reporting section of our API docs, as that’ll show you conversions based on your up-to-date attribution window.

Let me know if you have any questions.

-Byrne

Byrne CAnswer

Community Manager

Hey @brendanuye,

That’s a great question. I reached out to our engineering team and they confirmed that right now, the Query Metric Aggregates endpoint will return conversions based on the past attribution windows, back when those conversion occurred. It will not currently reflect your current attribution settings that were retroactively applied within Klaviyo. We recognize that this causes an inconsistency in our reporting tools, and we’re working to adjust these endpoints to reflect the attribution settings that are currently applied in your account.

For now, we recommend using the Query Campaign Values and Query Flow Values endpoints (or any of the endpoints in the Reporting section of our API docs, as that’ll show you conversions based on your up-to-date attribution window.

Let me know if you have any questions.

-Byrne

B

brendanuyeAuthor

Contributor II

Appreciate for the clarification here @Byrne C.

Just to confirm, the query metric aggregates by attribution channel will be reflective of the current attribution settings moving forward though? Same with the order-level included attributions via the Events API?

Thanks!

O

Ojuade Peace

Problem Solver III

The attribution updates in Klaviyo typically affect future data and won't retroactively apply to historical data in the API. This is why your past order events still show the old attribution numbers.

Workaround:

1. Manually adjust attribution for historical data in reports or exports.

2. Use updated in-platform reporting for accurate attribution.

3. Contact Klaviyo support if you need help syncing past data with new attribution settings.

Let me know if you need more details!

Byrne C

Community Manager

@brendanuye,

Currently, the Query Metric Aggregates endpoint will show the conversions based on the attribution window that was on your account when that attribution occurred. So if 6 months ago, you had a 10 day attribution window, and you’re using Query Metric Aggregates to look into conversions from 6 months ago, it’ll look at a 10 day attribution window, NOT your current attribution window. We’re working to change this in future versions of this endpoint, but that’s not out quite yet.

Our Reporting API endpoints do show you conversion data based on your current attribution windows. I see you’re asking about the Events API as well. Those API calls are used to pull in event data, and aren’t going to show you conversions. Were you referring to something else?

-Byrne

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials