Klaviyo UI vs Catchr Klaviyo Connector: why numbers differ & how to compare

Quick summary

• Catchr reads Klaviyo’s API.

• The Klaviyo UI can show different totals than the API due to different data sources or different aggregations.

• To verify numbers, compare the Catchr connector data vs a Klaviyo export for the same period. If still off, check timezone settings.

Why the UI can differ

• Source: UI may use precomputed/internal tables, while API/export uses raw event data.

• Aggregation: UI can group/attribute/deduplicate differently than API/export.

How to compare correctly (monthly)

1. In Klaviyo, run a data export for the month (e.g., 1–31 July) with the same metrics.

2. In Catchr, query the same month and same metrics (no breakdown) and match filters.

3. Compare the values. They should match the export (minor rounding aside).

Need campaign/flow attribution? Export by Campaign Name or Flow Name and compare to connector queries forced at that level (see our “Placed Order” article).

If the connector data differs from the export data, check the timezone:

Make sure the timezone matches Klaviyo’s account timezone everywhere:

• Google Sheets add‑on: query options → timezone

• Power BI: query options → timezone

• Catchr API: query options → timezone

• Looker Studio: data source connection → timezone