Events Log reports every Klaviyo event as one row, dated when the event happened, and replaces both of the older raw-event reports with a single report whose personal data sits in one optional column.
- Updated
- October 5, 2026
- Affected
- Events Log
- What to do
- No action required for existing reports. Add Events Log to your Klaviyo extraction to receive raw events, and leave the Event Properties field unselected if you do not want personal data in the table.
Events Log is the raw Klaviyo event stream: one row per event, dated when the event happened. It replaces both Events and Events without PII, which are no longer offered for new extractions.
What a row contains
The event's own identifiers and timestamps, plus the IDs of everything the event is about — the metric, the profile, and the campaign message or flow message it is attributed to. Where the event carries a monetary value, that value and its currency are their own columns, so revenue is reportable without parsing anything.
Everything else Klaviyo attaches to an event arrives in a single Event Properties column as JSON. That is deliberate: the set of properties differs per account and per event type, so there is no fixed list of columns that would suit everyone.
Personal data is confined to one column
Raw Klaviyo events can carry a recipient's email address, and for commerce events a shipping or billing address. All of it arrives inside Event Properties, and that field is not selected by default. Leave it unselected and the report is limited to identifiers and measurements; select it and you get the full event payload.
This is what lets one report do the job the two older ones split between them — there is no longer a separate PII-free variant to choose, only a column to include or leave out.
Getting names instead of IDs
The report carries IDs rather than labels, so it stays narrow and fast. Join it to Metrics Entity for metric names, Profiles Entity for profile attributes, and Campaigns Entity, Campaign Messages Entity, Flows Entity or Flow Messages Entity for campaign and flow names.
Choosing a date range
Raw events are high volume — a single busy day on one account can exceed half a million events — so the default history is shorter than on the older reports, and the maximum is one year. If you need a long history, or a faster daily extraction, use the metric filter to restrict the report to the events you actually report on.
The date on a row is when the event happened, in your account's timezone, which matches how the other Klaviyo performance reports are dated. The original vendor timestamp is kept in its own column if you need the exact instant.