Clarification around the 3 hr SLA for the events API

We recently got the notice around the new guarantees around the events API:

We are reaching out regarding an upcoming change to Klaviyo’s events APIs. Starting on July 31, 2025 Klaviyo will be updating the attribution data freshness on our events APIs to a 3-hour SLA for improved system performance and data accuracy. If you are leveraging attribution data from these affected APIs, we recommend you update your usage of the events APIs to reflect the updated attribution data freshness prior to the cutover date to avoid any disruption to your integration.

The affected endpoints are:
Get Events
Get Event

We had a few follow-up questions about this:

Do you know if attribution data even on prior versions of the API might be stale when retrieving event data?
How do these changes impact the webhook API endpoints, if at all?
Do you know if opens/clicks also have a certain window of time where they also lack attribution data with regards to the source email?

Thank you!

Page 1 / 1

Two more clarification questions:

If webhooks are impacted by the changes, will we receive a second event when attribution is added later? If not, what is the best way to retrieve that attribution later?
We rely on event_id to uniquely identify events, but that identifier includes an ID associated with attribution. Does this mean the event_id will change when attribution is later attached?

Hey @deezium,

Happy to answer these questions for you!

This change will be applied to all revision versions of the Get Events and Get Event APIs.
Are you referring to webhooks in flows? If so, these changes will not affect those webhooks, because only POST requests can be added as webhooks in flows.

Reaching out to our engineers so I can provide more clarity on the rest.

Hi again @deezium,

I have more info for you regarding your questions!

To reiterate, these changes will affect every API revision universally, and there will be no concept of stale attribution data.

There is no change to how clicks and opens are associated with a message, this will only impact data persisted in $attribution for conversion metrics (ex. Placed Order)

Attribution data is not available via webhooks and the best way to access this data at a later data is via the events APIs.

Does the above make sense? Let me know if I can answer any follow-up questions.

Reply

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials

Scanning file for viruses.

This file cannot be downloaded