Klaviyo (sample data)

Marketing

Ready to useNo account needed

Klaviyo (sample data) data, published as Klaviyo (sample data) publishes it. Ingest delivers this data to a data warehouse you own as 4 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

What you get

TableEach row is
campaign_metrics
campaign_metrics
Delivery and engagement per campaign: delivered, opens, clicks, unsubscribes, spam complaints, placed orders and attributed revenue.
campaigns
campaigns
Every email and SMS campaign sent: subject line, audience segment, send time and recipients.
flow_metrics_daily
flow_metrics_daily
One row per flow per day: recipients, delivered, opens, clicks, unsubscribes, placed orders and attributed revenue.
flows
flows
Automated email flows (welcome, abandoned cart, browse abandonment, post-purchase, winback) and what triggers them.

How it works

  1. Choose Klaviyo (sample data). The data is public, so there is nothing to sign in to.
  2. Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
  3. Pick a schedule. Daily is the default, and weekly and monthly are there too.
  4. Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

Do I need an account with Klaviyo (sample data)?
No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Klaviyo (sample data) data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?
As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?
No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference

Connector sample_klaviyo, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://2k247ci8d7.execute-api.us-east-1.amazonaws.com/docs

Configuration

No configuration required.

Resources

ResourceStatusPlanWritePrimary keyOverrides
campaign_metrics
Delivery and engagement per campaign: delivered, opens, clicks, unsubscribes, spam complaints, placed orders and attributed revenue.
betafullmergecampaign_id-
campaigns
Every email and SMS campaign sent: subject line, audience segment, send time and recipients.
betafullmergecampaign_id-
flow_metrics_daily
One row per flow per day: recipients, delivered, opens, clicks, unsubscribes, placed orders and attributed revenue.
betafullmergereport_date, flow_id-
flows
Automated email flows (welcome, abandoned cart, browse abandonment, post-purchase, winback) and what triggers them.
betafullmergeflow_id-

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Get Klaviyo (sample data) data into your warehouse

Last updated .