Klaviyo logo

Email & SMS integration

Klaviyo reporting & dashboards

Turn Klaviyo campaigns and flows into governed email reporting tied to revenue.

What you can do with Klaviyo in Maven

Maven connects Klaviyo and models campaign and flow performance into governed email metrics. Track sends, open and click rates, unsubscribes, and attributed revenue, break results down by campaign, list, or subject line, and report email beside the Shopify revenue it generates.

What you can measure

54 Klaviyo metrics you can use consistently

Maven keeps Klaviyo numbers consistent across dashboards, reports, and answers so the team is not debating which spreadsheet is right.

Email Attributed Orders

Orders attributed to the send by the email platform.

Email Attributed Revenue

Revenue attributed to the send by the email platform.

Email Bounces

Bounced emails from connected email send performance rows

Click Rate

Unique clicks divided by emails delivered

Email Clicks

Email clicks including repeat clicks at send grain

Open Rate

Unique opens divided by emails delivered

Email Opens

Email opens including repeat opens at send grain

Email Replies

Replies received from connected email send performance rows.

Email Spam Reports

Spam or abuse reports from connected email send performance rows.

Show all 54 metrics

Unique Clicks

Unique recipients or profiles that clicked at send grain

Unique Opens

Unique recipients or profiles that opened at send grain

Email Unsubscribes

Unsubscribes from connected email send performance rows

Emails Delivered

Emails delivered by connected email platforms at send grain

Emails Sent

Emails sent by connected email platforms at send grain

Iterable Conversions

Conversions reported by Iterable

Iterable Message Bounces

Message bounces reported by Iterable

Iterable Message Clicks

Message clicks reported by Iterable

Iterable Message Opens

Message opens reported by Iterable

Iterable Messages Sent

Messages sent by Iterable

Iterable Revenue

Revenue attributed by Iterable

Iterable SMS Bounces

SMS bounces reported by Iterable

Iterable Unsubscribes

Unsubscribes reported by Iterable

Message Complaints

Message Dropped

Message Ecommerce Spent

Message Processed

Message Purchases

Push Message Bounces

Push bounces across connected messaging platforms

Push Message Opens

Push opens across connected messaging platforms

Push Messages Sent

Push messages sent across connected messaging platforms

Message Recipient Count

SMS Messages Received

SMS messages received across connected messaging platforms

SMS Messages Sent

SMS messages sent across connected messaging platforms

Message Unsubscribe Event Count

SMS Attributed Orders

Orders attributed to SMS sends

SMS Attributed Revenue

Revenue attributed to SMS sends

SMS Bounces

SMS message bounces across connected messaging platforms

SMS Clicks

SMS message clicks across connected messaging platforms

SMS Delivered

SMS messages delivered across connected messaging platforms

SMS Unsubscribes

SMS unsubscribes across connected messaging platforms

Message Attributed Orders

Orders attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email and SMS platforms report attributed ecommerce orders; Iterable rows use Iterable purchases.

Message Attributed Revenue

Revenue attributed to the send by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.

Message Bounces

Bounced messages at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.

Message Clicks

Clicks including repeat clicks at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.

Message Conversions

Conversions reported by the messaging platform. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Definitions differ by provider: Iterable email rows carry Iterable custom conversion events, while email-platform and SMS-platform rows carry attributed orders (equal to message_attributed_orders). Filter platform = iterable for Iterable conversions.

Message Opens

Opens including repeat opens at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email opens are pixel opens (inflated by privacy proxies such as Apple MPP); push opens are app opens from a notification; SMS rows carry no opens. Do not compare open counts across channels; filter channel = email for email opens.

Message Replies

Replies received from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate replies.

Message Spam Reports

Spam or abuse reports (complaints) from connected send performance rows. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Iterable complaints are reported as spam reports; SMS and push rows carry none.

Unique Clicks

Unique recipients or profiles that clicked at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. SMS-platform rows report no unique clicks and carry total clicks instead (unique_clicks = clicks), and Iterable rows are 0; filter channel = email for true email unique clicks.

Unique Opens

Unique recipients or profiles that opened at send grain. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Only email-platform rows populate unique opens (Iterable, SMS and push rows are 0), so the total equals email unique opens.

Message Unsubscribes

Unsubscribes attributed to sends across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Counts unsubscribers, not unsubscribe events (see message_unsubscribe_event_count).

Messages Delivered

Messages delivered at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Email-platform and SMS-platform rows report native delivered counts; Iterable email, SMS and push rows derive delivered as sent minus bounces.

Messages Received

Inbound SMS messages received across connected messaging platforms. Only SMS rows populate this measure. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider.

Messages Sent

Messages sent at send grain across email, SMS and push. channel (email|sms|push) and platform are dimensions: filter or group by them for a single channel or provider. Filter channel = email for emails sent.

Questions you can ask

Just ask Maven about Klaviyo

Maven’s agent answers in plain language with the right metric definitions applied automatically. These are real, verified questions it can run today.

How many emails did we send and what was the unique open count last month by platform?

Show bounces by campaign type

How much email attributed revenue did we drive by platform?

Agency report templates

Agency templates that use Klaviyo

Each template is one prompt in Claude or ChatGPT, with a full sample on fictional data you can page through.

Connection and sync

What Maven pulls from Klaviyo

You connect Klaviyo with API credentials from the Klaviyo account. Maven stores them encrypted. The first Klaviyo sync pulls the most recent 30 days so the workspace fills quickly. A follow-up backfill then adds older history, up to 12 months in total. After that, each scheduled sync re-reads the last 3 days, so late changes are picked up.

Profiles

Klaviyo customer profiles.

Fields: account name, email, phone number, created, updated, subscriptions json

Global exclusions

Suppressed profiles from Klaviyo global exclusions.

Fields: account name, email, suppression json

Events

Klaviyo events with included metric/attribution context.

Fields: account name, datetime, metric name, event properties json

Events detailed

Detailed Klaviyo events with included relationship payloads.

Fields: account name, datetime, metric name, attributions json

Email templates

Klaviyo email templates.

Fields: account name, name, created, updated

Campaigns

Klaviyo campaign entities.

Fields: account name, campaign name, channel, status, archived, updated at

Campaigns detailed

Klaviyo campaigns with recipient estimates and messages.

Fields: account name, estimated recipient count, campaign messages json

Flows

Klaviyo automation flow entities.

Fields: account name, flow name, status, archived, updated

Metrics

Klaviyo metric/event definitions.

Fields: account name, metric name, integration name, updated

Lists

Klaviyo lists.

Fields: account name, list name, updated

Lists detailed

Klaviyo lists with profile counts.

Fields: account name, list name, profile count

Campaign values reports

Klaviyo campaign reporting values by conversion metric and period.

Fields: account name, send channel, opens, clicks, conversions, conversion value, recipients

Flow series reports

Klaviyo flow reporting series by conversion metric and period.

Fields: account name, send channel, opens, clicks, conversions, conversion value, recipients

How it works

Connect Klaviyo to a client’s workspace

No SQL or warehouse setup. Connect the source, then build the client’s report by asking Claude or ChatGPT.

Step 1

Connect Klaviyo

In the client’s workspace, open Sources, add Klaviyo and choose the account to sync. If you don’t have access to the account, send the client a connect link where the platform supports one.

Step 2

Maven syncs and models the data

Maven pulls the client’s Klaviyo data (3 objects) and models it into documented tables. No SQL, warehouse or pipeline setup.

Step 3

Report, ask and automate

Build the client’s report or deck by asking Claude or ChatGPT through the MCP, set alerts on what matters, and publish to the client’s portal once you approve it.

Works well with

Report Klaviyo alongside the rest of your stack

FAQ

Klaviyo reporting questions

What Klaviyo metrics can I report on in Maven?

Maven exposes 54 governed Klaviyo metrics, including Email Attributed Orders, Email Attributed Revenue, Email Bounces, Click Rate, Email Clicks and Open Rate — each defined once so it means the same thing in every report.

What can I break Klaviyo performance down by?

You can break Klaviyo metrics down by Channel, Account, Campaign type, Subject line, Title, Sender, Email list and Campaign, and more.

Can I combine Klaviyo with other data sources?

Yes. Klaviyo sits in the same client workspace as sources like Shopify, Facebook Ads, Google Ads and HubSpot, so one report or question can use them together.

How often does Klaviyo data sync to Maven?

Maven syncs Klaviyo automatically: a fast first source pull after connecting, then scheduled refreshes that keep reports current. The last successful sync time is always visible, so you know the source data is fresh before it feeds a trusted reporting workflow.

Is my Klaviyo data secure with Maven?

Yes. Maven connects to Klaviyo over its official OAuth flow — no password sharing — stores access tokens encrypted, and pulls read-only reporting data into a governed warehouse you control.

Start your 14-day trial

Set up your first client, build their report by asking Claude or ChatGPT, and publish it to their portal.

  • Free for 14 days, no credit card
  • Your first client workspace and portal
  • Every report template, ready to clone
Start a 14-day trial

Nothing is charged unless you subscribe.

Prefer a walkthrough? Book a demo on one of your own clients.