A change to the Events API, starting October 26th

Question

I got this email and im not sure what aggregate only events are. I tried looking around and couldn't get much info on what aggregate only events are. I do grab events and check for clicked email, opened link for campaign emails for a timeframe and process them but that is about it. Can you tell me if this would be effect us?

Hi there,

Starting the week of October 26th, the GET /events endpoint stops returning “aggregate-only” events for your account.

What these are:
Anonymous activity on your site that Klaviyo can’t tie to a person—someone opening a signup form and closing it without submitting, viewing a review, opening the chat widget, or seeing a product recommendation block. Because no profile is attached, these events have never appeared on a profile timeline or been usable for segmentation. They exist only to feed analytics.

Your reporting doesn’t change.
Forms and Reviews analytics, conversion rates, and the dashboards built on them run on separately stored counts, not on these individual records. They keep working exactly as they do today—as do flow triggers and filters, profile timelines, and Bulk Export and data warehouse exports.

What would change is if you pull these records directly from the API, for example, to build your own report of “how many people viewed this form on mobile last week” from raw event rows instead of using Klaviyo’s reporting. If your integration does that, you’ll see fewer events returned for a given date range starting October 26th. That’s expected, not missing data.

If that’s you, contact us support before October 26th and we’ll work with you on a path forward. If your workflow doesn’t rely on these events, no action is needed, please disregard this notice.

The Klaviyo Events and API Teams

GabbyEsposito · Accepted Answer

​@learningGuy123back with an update!Here’s the official breakdown I got:An aggregate-only event is an anonymous interaction that Klaviyo can’t associate with a specific profile. For example, someone may view, click, or close a sign-up form without submitting identifying information.These events can include context such as the form, page URL, device type, and timestamp, but they do not include an email address, phone number, or profile ID. They are used only for account-level reporting, such as total form views, submit rates, and funnel performance.Because they aren’t tied to an individual profile, aggregate-only events do not appear on profile timelines and can’t be used for person-level segmentation or flows.Starting October 26, the GET /events endpoint will no longer return aggregate-only events. This does not change your Klaviyo reporting. Form and Review analytics, conversion rates, and related dashboards will continue to include the aggregate counts they use today.The change only affects integrations that retrieve raw event records directly from the API. If you use those records to build a report, you should expect fewer events in the API response because aggregate-only records will no longer be included.Based on your description, checking campaign email opens and link clicks should not be affected, since those are typically profile-associated events rather than anonymous aggregate-only events. The change would matter only if your process also relies on retrieving aggregate-only records, such as anonymous form activity, from the Events API.I hope this helps clarify the change!And as always, thank you ​@KeviSunshinefor jumping in with such a great, accurate breakdown.

GabbyEsposito · Answer

​@learningGuy123​@KeviSunshinelooking into this. Thanks for identifying

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials