Integrations · MarketingConnect Klaviyo to Well
Attribute Klaviyo campaign, subscriber, and event to revenue in your CRM, with channel and cohort breakdown ready.
What Well pulls from Klaviyo
Klaviyo feeds campaign, subscriber, event into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Klaviyo’s access.
| From Klaviyo | In Well | Relation | |
|---|---|---|---|
| Campaign | Outreach record | Becomes | |
| Subscriber | Person | Resolves to | |
| Event | Engagement signal | Feeds |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Klaviyo → Well
What Well does with your Klaviyo connection
Connect
Connect Klaviyo over OAuth (MCP DCR): Well registers a client through Klaviyo's OAuth Dynamic Client Registration and you approve on Klaviyo's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings campaign, subscriber, and event in from Klaviyo on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Klaviyo entity into outreach record, person, and engagement signal, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Klaviyo lands in the workspace as outreach record, person, and engagement signal you can search, chart, and automate.
Questions Klaviyo unlocks
Ask in plain language. Well answers from your connected Klaviyo connection, resolved against the rest of your stack.
Ask anything about your Klaviyo connection
Ask about your Klaviyo connection…
Connect Klaviyo in three steps
- 01
Authorise Klaviyo via MCP
From Well's Connections panel, search for Klaviyo and click Connect. Well discovers Klaviyo's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Klaviyo's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.klaviyo.com/mcp
- 02
Map your entities
Well's MCP client discovers campaign, subscriber, and event from Klaviyo that Klaviyo's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Klaviyo records. Because Klaviyo ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Klaviyo records happens in the background.
How Klaviyo stays secure with Well
Well connects to Klaviyo's MCP server (mcp.klaviyo.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Klaviyo secret. Tokens are scoped to the campaign, subscriber, and event Klaviyo exposes and refreshed server-side. Reads only, Well cannot modify or delete Klaviyo records.
- granted
Read Klaviyo records
Resources the Klaviyo MCP server exposes, scoped by your OAuth approval.
- granted
Resolve campaign, subscriber, and event across your stack
Match identifiers in Klaviyo against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Klaviyo records
Not granted; Klaviyo is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Klaviyo passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Klaviyo and Well
From Well, open Connections, find Klaviyo, and click Connect. Well discovers the OAuth metadata at mcp.klaviyo.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Klaviyo's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in campaign, subscriber, and event from Klaviyo and reshapes each entity into your workspace: campaign becomes outreach record; subscriber becomes person. Every record arrives with the source identifier preserved, so Klaviyo stays the source of truth while Well lets you query the data alongside the rest of your stack.
Well attributes each Klaviyo campaign to the customers it acquired, joining campaign spend and engagement records to deal stages and invoiced revenue. Blended CAC, channel-level payback, and cohort behaviour are queryable without a separate attribution stack.
Every workspace outreach record built from Klaviyo carries the source campaign identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Klaviyo record; from Klaviyo, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well combines live Klaviyo events with periodic reconciliation reads of campaign, subscriber, and event. New rows appear within seconds when Klaviyo pushes them; periodic reads catch anything a push missed. The first connect backfills history from Klaviyo in the background.
Open Connections > Klaviyo in Well and click Disconnect. Well calls Klaviyo's token revocation endpoint and stops calling Klaviyo immediately on its side; provider-side propagation to Klaviyo's admin panel varies by provider. The campaign, subscriber, and event Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Klaviyo records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Klaviyo
More in Marketing
AirOps
Connect AirOps to Well to sync campaign data and marketing analytics.
Bitly
Connect Bitly to Well to sync campaign data and marketing analytics.
Supermetrics
Connect Supermetrics to Well to sync campaign data and marketing analytics.
Windsor.ai
Connect Windsor.ai to Well to sync campaign data and marketing analytics.
Popular cross-category
Ready to connect Klaviyo?
Connect once. Every campaign, subscriber, event from Klaviyo becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.