Skip to main content
Solved

Events API alignment to UI

  • October 17, 2024
  • 2 replies
  • 28 views

For various email campaign related metrics basic counts do not align with the Klaviyo UI, when the raw events are pulled directly. We desire the raw events rather then aggregates and it’s a bit disconcerting to find two forum posts almost a year old with the same issue: 


When raw events are pulled we’re able to perfectly align campaign delivery counts, and bounces, however we have fewer clicks and opens than the UI. When we count clicks/opens by distinct profiles the count is sometimes higher and sometimes lower than the UI.

Is there a better method for aligning the raw events to the UI? 

For reference we pull periods of time via format similar to :
`https://a.klaviyo.com/api/events/?filter=greater-than(datetime,2024-10-04T00:00:00Z),less-than(datetime,2024-10-05T00:00:00Z)`

Best answer by saulblum

Check lout the reporting APIs.

https://developers.klaviyo.com/en/reference/reporting_api_overview

 

The Query Metrics Aggregates endpoint

You may be using our Query Metric Aggregates endpoint to export reporting data for campaigns and flows. It’s important to note that data from the Query Metric Aggregates endpoint does not match the data reflected in the Klaviyo UI. While this endpoint allows you to filter and group campaign and flow data based on the time an event occurred, performance in the Klaviyo UI is calculated based on send date. We recommend our Reporting API to achieve this use case, which is built to fetch 1:1 matches of data shown in the Klaviyo UI.

View original
Did this topic or the replies in the thread help you find an answer to your question?

2 replies

Forum|alt.badge.img+7
  • Klaviyo Employee
  • 169 replies
  • Answer
  • October 17, 2024

Check lout the reporting APIs.

https://developers.klaviyo.com/en/reference/reporting_api_overview

 

The Query Metrics Aggregates endpoint

You may be using our Query Metric Aggregates endpoint to export reporting data for campaigns and flows. It’s important to note that data from the Query Metric Aggregates endpoint does not match the data reflected in the Klaviyo UI. While this endpoint allows you to filter and group campaign and flow data based on the time an event occurred, performance in the Klaviyo UI is calculated based on send date. We recommend our Reporting API to achieve this use case, which is built to fetch 1:1 matches of data shown in the Klaviyo UI.


  • Author
  • 1 reply
  • October 17, 2024

Appreciate the response, but I’m not looking to use the aggregate endpoints. Our desire is to use the raw events to allow us to supplement user journeys with data outside of Klaviyo in our Data Warehouse. Right now we’re using the aw /events/ endpoint.