# Klaviyo integration for paid acquisition

Hendrik reads Klaviyo profiles, exclusions, events, metrics, campaigns, flows, templates, lists, segments, and performance so you can put lifecycle activity beside paid acquisition and commerce.

## Questions Hendrik can help answer

- Did a lifecycle send change the context for paid acquisition?
- Are repeat purchase or exclusion changes affecting the audience?
- Should a budget choice wait for a lifecycle explanation?

## Illustrative example

### Examine a repeat-purchase spike

Same 21-day USD windows

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Reported purchase value (Meta Ads): US$90,000 → US$112,000
- Flow attributed value (Klaviyo): US$11,000 → US$29,000
- Returning-customer order count (Shopify): 680 → 1,020

### What Hendrik checks

- **Record attribution windows:** Keep the Meta and Klaviyo settings separate.
- **Review flow change:** Check send volume, audience, and template changes.
- **Check customer definition:** Use Shopify’s store definition without assuming person-level linkage.

### What Hendrik sees

Klaviyo flow value and Shopify returning-customer orders rose alongside Meta reported purchase value.

### What to do next

Review the lifecycle change before assigning the performance shift to paid media.

**Limit:** No revenue is deduplicated or causally assigned in this example.

## What Klaviyo contributes

Use Klaviyo with commerce and ad data to see whether a lifecycle change may explain a repeat-purchase or revenue shift before paid media is credited.

## Data Hendrik reads

- **Campaigns and flows:** Lifecycle campaign and flow definitions.
- **Campaign performance:** Performance by configured reporting window.
- **Flow performance:** Daily flow reports.
- **Profiles and segments:** Audience and segment context.
- **Events:** Captured lifecycle events.

## Setup and access

- **Setup:** When enabled, sign in with Klaviyo, select the account and conversion metrics, then choose 1 to 3,650 days of history. The current default is 90 days.
- **Permissions:** Klaviyo read scopes for accounts, campaigns, events, flows, lists, metrics, profiles, segments, and templates.
- **Accounts:** One Klaviyo account.
- **History:** Klaviyo setup defaults to 90 days and accepts 1 to 3,650 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to daily. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** Klaviyo starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** Connecting reads Klaviyo data. It does not send messages or change flows, audiences, or profiles.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

- Confirm the Klaviyo account and message attribution settings.
- Use the same audience and reporting window when comparing campaigns.
- Establish identity coverage before customer-level comparisons.

## Important limits

- Klaviyo attribution follows the provider rules and is not causal attribution.
- Message exposure does not prove a later purchase was caused by the message.
- Profiles cannot be assumed to match commerce customers.

## Provider documentation

- [Klaviyo API](https://developers.klaviyo.com/en/reference/api_overview)

## Start with Klaviyo

[Create a workspace and connect Klaviyo](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-klaviyo&integration=klaviyo)