This article will cover how to view the raw event data Klaviyo receives from integrations or API calls. This can be useful if you want to verify the data Klaviyo records along with a given event, or simply review this data to better understand what's being recorded.
Finding Raw Metric Data
To view raw metric or event data, go to the Metrics tab in Klaviyo and find the metric you're interested in. Next, click on the second icon to view the activity feed for that metric.
While viewing the activity feed, click on the timestamp for any event to display the event's raw data in an Event Details pane.
Picking Your View
There are two views here in the event details pane: the "pretty" view and the JSON view
The "pretty" view contains a collapsible tree with data sorted alphabetically, making it easy to browse and find the property you're interested in.
The JSON view allows you to view and copy a JSON version of the event data.
Now that you retrieved data from the Activity Details, it’s important to understand the meaning behind the two timestamps included in this information. The two times are often but not always identical.
The first timestamp refers to the time the event is first triggered. For example, if the trigger for a flow is Checkout Started, then this timestamp details exactly when the checkout occurs on your ecommerce site. The second timestamp is the time in which the event appears in Klaviyo. Usually, these timestamps are the same or seconds apart, as shown below:
Depending on your integration, the time it takes for Klaviyo to receive this information from the other source can lead to a delay. An example of this type of instance is displayed below:
In this example, the first timestamp is the same, and the second timestamp states exactly when Klaviyo registers the event from your integration. If you’re interested in learning how frequently your integration syncs, head to our article, How Often Integrations Sync.
Understanding timestamps is vital to ensuring that your emails are timely and relevant. It's important to take any delay in event syncing into consideration when planning your marketing strategy, especially when creating flows. For an abandoned cart flow, if a customer begins a checkout and then completes their purchase, this event data may take an hour (as is the case for WooCommerce) for Klaviyo to register that they completed a purchase. If you set your first flow email to send out a half-hour after the Checkout Started event and we have not received confirmation that the checkout was completed, this customer may receive the abandoned cart flow email by mistake.
In general, if you have an integration with a sync delay, we recommend that you set your flow emails to send an hour (or later) after a trigger event to avoid unintended consequences. This is best practice, with the exception of a welcome series which often sends immediately after someone subscribes and would not be affected negatively by a time delay.