Source connector

Klaviyo connector

Klaviyo integration for databases, warehouses and BI tools

E-commerce marketing automation with email and SMS. Datrise captures Klaviyo entities such as profiles, segments, flows, campaigns, and attributed revenue, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Klaviyo API (revision 2026-07-15) authenticates with OAuth 2.0, API key, incremental runs key on updated, and Klaviyo caps calls at tiered per endpoint from XS (1 req/s burst, 15/min steady) to XL (350 req/s burst, 3,500/min steady); most list endpoints sit in the S-M tiers (3-10 req/s burst, 60-150/min steady).

Of the 5 objects, 5 sync as upserts keyed on the primary key and 0 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `klaviyo_profiles`) with a schema derived from the Klaviyo API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Klaviyo pipeline page, and join the waitlist to get the Klaviyo connector (Marketing) with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Klaviyo data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
profiles	klaviyo_profiles	Upsert by primary key, incremental on updated-at
segments	klaviyo_segments	Upsert by primary key, incremental on updated-at
flows	klaviyo_flows	Upsert by primary key, incremental on updated-at
campaigns	klaviyo_campaigns	Upsert by primary key, incremental on updated-at
attributed revenue	klaviyo_attributed_revenue	Upsert by primary key, incremental on updated-at

Klaviyo API: setup facts for the connector

Verified against the vendor documentation on 2026-09-02. Unknown values are left blank rather than guessed.

API	Klaviyo API (revision 2026-07-15)
Authentication	OAuth 2.0, API key — Server-side integrations send a private key (prefixed `pk_`) in an `Authorization: Klaviyo-API-Key ...` header, while OAuth 2.0 is required for App Marketplace integrations and unlocks higher rate-limit tiers.
Pagination	cursor — JSON:API-style `page[cursor]` pagination with `page[size]` (default 20, max 100).
Rate limit	tiered per endpoint from XS (1 req/s burst, 15/min steady) to XL (350 req/s burst, 3,500/min steady); most list endpoints sit in the S-M tiers (3-10 req/s burst, 60-150/min steady)
Incremental cursor	updated — Profiles, events and most list endpoints accept `filter=greater-than(updated,'<timestamp>')` (also `created`) for incremental pulls.
Webhooks	Yes — Webhooks (Developer Portal, topic-based)
Bulk export	Yes — Bulk Export Job API (events beta/invite-only; profiles by list or segment)
Deletes detectable	No

Official API reference

What bites when replicating Klaviyo

The Profiles API has no deleted-profile feed or tombstone record: a GDPR-erased profile simply stops appearing in list/get responses, so a connector can only infer a delete by diffing the full ID set between syncs.
Rate limits are set per endpoint and tier (from XS at 1 req/s burst to XL at 350 req/s burst), so the same connector code can hit `429` on one object type well before another even though both use the same API key.
The Event Bulk Export Job endpoint is beta and invite-only (allow-listed API keys/OAuth apps only) and caps each job's date range at 90 days, so a full historical events backfill must be chunked into 90-day windows and isn't available to every account.
`page[size]` tops out at 100 records, and `filter=greater-than(updated,...)` on profiles only reflects direct profile-field changes, not every subscription or suppression timestamp, which live in nested `subscriptions.*` filters instead.

Compare this against every other documented API

Popular destinations for Klaviyo

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Klaviyo connector FAQ

What Klaviyo data does the connector extract?: 5 objects: profiles, segments, flows, campaigns and attributed revenue. Each lands in its own table with types preserved; history-style objects (0) load as append-only streams.
Is the Klaviyo integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Klaviyo data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Klaviyo → destination pair has its own page with the object-to-table mapping.

Related Marketing sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Klaviyo pipeline with guided onboarding

Join the waitlist to get priority access for Klaviyo integrations with guided setup, schema-aware mapping, and production-grade incremental sync.