Google Analytics 4 + Klaviyo

Did website activity and Klaviyo activity change together?

Connect Google Analytics 4 and Klaviyo to Hendrik. Compare GA4 observed lifecycle traffic and events with Klaviyo message and flow reporting while preserving both attribution systems.

Start with this stackBook a founder demo

See Hendrik at work

Google Analytics 4 + Klaviyo review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC.

MetricPreviousCurrent
Google Analytics 4reported purchase events (count, 28 days)1,4201,230
Klaviyoflow-attributed orders (count, 28 days)310420
Google Analytics 4GA4 paid sessions (configured channel group, consecutive 28-day periods)16,80015,300

What Hendrik checks

  1. Traffic measurement

    Check GA4 property, timezone, consent coverage, source definition, and event configuration before comparing sessions or transactions.

  2. Message and audience definition

    Check Klaviyo attribution setting, send volume, audience, exclusions, flow changes, and message window before interpreting attributed value.

  3. Explain the divergence

    Google Analytics 4: reported purchase events (count, 28 days) changed from 1,420 to 1,230. Klaviyo: flow-attributed orders (count, 28 days) changed from 310 to 420. Compare the timing and definitions before attributing one change to the other.

About this example Synthetic data · Illustrative analysis · Changes require your approval.

How Hendrik handles your data

Want Hendrik to answer this with your data?

Start with this stackBook a founder demo

One analysis, different integrations

What each integration adds

Connect your stack

Set up each integration in one workspace.

  1. Create your Hendrik account. Choose a workspace for your business.
  2. Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
  3. Ask your first question. Hendrik uses the available data and tells you when a comparison needs more history or more data.
Requirements and data limits

What you need

  • Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
  • Connected GA4 property with comparable acquisition and event reporting.
  • Connected Klaviyo account with the relevant message, flow, and attribution definitions.
  • Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

Keep these differences in mind

  • GA4 events and attribution do not automatically establish a paid order, payment, or campaign relationship.
  • Message attribution is observational and does not show that exposure caused a store, payment, or subscription outcome.
  • GA4 events and Klaviyo attributed value are not deduplicated or causal credit.

Your data. Your next step.

Put Hendrik to work on your stack.

Create your account, choose your workspace and connect your data.

Start with this stackBook a founder demo
See plans and pricing