Klaviyo + Recharge

Did Klaviyo activity move with renewals or cancellations?

Connect Klaviyo and Recharge to Hendrik. Check whether a Klaviyo lifecycle change coincides with Recharge subscription, charge, or plan movement.

See Hendrik at work

Klaviyo + Recharge 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
Klaviyoflow-attributed orders (count, 28 days)310420
Rechargesuccessful renewals (count, 28 days)1,080980

What Hendrik checks

  1. Message and audience definition

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

  2. Subscription and charge timing

    Check Recharge subscription state, successful charges, plan changes, and order overlap with Shopify before comparing totals.

  3. Explain the divergence

    Klaviyo: flow-attributed orders (count, 28 days) changed from 310 to 420. Recharge: successful renewals (count, 28 days) changed from 1,080 to 980. 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?

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 Klaviyo account with the relevant message, flow, and attribution definitions.
  • Connected Recharge account with comparable subscription, renewal, and cancellation 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

  • Message attribution is observational and does not show that exposure caused a store, payment, or subscription outcome.
  • Subscription outcomes can overlap commerce and payment records; no campaign cohort or customer match is assumed.
  • Message exposure does not prove a subscription outcome.

Your data. Your next step.

Put Hendrik to work on your stack.

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

See plans and pricing