Integrations · Marketing

Connect Supermetrics to Well

Attribute Supermetrics metric, data source, and channel to revenue in your CRM, with channel and cohort breakdown ready.

What Well pulls from Supermetrics

Supermetrics feeds metric, data source, channel into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Supermetrics’s access.

From SupermetricsIn Well
Metric
Dashboard signal
Data source
Workspace context
Channel
Category
Supermetrics logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Supermetrics → Well

What Well does with your Supermetrics connection

Connect

Connect Supermetrics over OAuth (MCP DCR): Well registers a client through Supermetrics's OAuth Dynamic Client Registration and you approve on Supermetrics's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings metric, data source, and channel in from Supermetrics 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 Supermetrics entity into dashboard signal, workspace context, and category, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Supermetrics lands in the workspace as dashboard signal, workspace context, and category you can search, chart, and automate.

Questions Supermetrics unlocks

Ask in plain language. Well answers from your connected Supermetrics connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Supermetrics connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Supermetrics connection…

Connect Supermetrics in three steps

  1. 01

    Authorise Supermetrics via MCP

    From Well's Connections panel, search for Supermetrics and click Connect. Well discovers Supermetrics's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Supermetrics's side. No client credentials to paste.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.supermetrics.com/mcp
  2. 02

    Map your entities

    Well's MCP client discovers metric, data source, and channel from Supermetrics that Supermetrics'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
  3. 03

    Use the data

    Ask questions in conversation, build records tables, or let agents act on Supermetrics records. Because Supermetrics 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 Supermetrics records happens in the background.

How Supermetrics stays secure with Well

Well connects to Supermetrics's MCP server (mcp.supermetrics.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 Supermetrics secret. Tokens are scoped to the metric, data source, and channel Supermetrics exposes and refreshed server-side. Reads only, Well cannot modify or delete Supermetrics records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.supermetrics.com/mcp
  • Read Supermetrics records

    Resources the Supermetrics MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve metric, data source, and channel across your stack

    Match identifiers in Supermetrics against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Supermetrics records

    Not granted; Supermetrics is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Supermetrics passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or Supermetrics’s admin panel.

Frequently asked questions about Supermetrics and Well

From Well, open Connections, find Supermetrics, and click Connect. Well discovers the OAuth metadata at mcp.supermetrics.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 Supermetrics's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in metric, data source, and channel from Supermetrics and reshapes each entity into your workspace: metric becomes dashboard signal; data source becomes workspace context. Every record arrives with the source identifier preserved, so Supermetrics stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each Supermetrics campaign carries its spend, audience, and engagement records into Well. Joined to CRM deals and invoiced revenue, "blended CAC for the Q2 LinkedIn push" and "payback by channel" become queryable in conversation. The attribution stops being a separate worksheet.

Each Supermetrics metric is scored against the candidate dashboard signals in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely dashboard signal prefilled and the Supermetrics source attached.

Well combines live Supermetrics events with periodic reconciliation reads of metric, data source, and channel. New rows appear within seconds when Supermetrics pushes them; periodic reads catch anything a push missed. The first connect backfills history from Supermetrics in the background.

Open Connections > Supermetrics in Well and click Disconnect. Well calls Supermetrics's token revocation endpoint and stops calling Supermetrics immediately on its side; provider-side propagation to Supermetrics's admin panel varies by provider. The metric, data source, and channel Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Supermetrics 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.

Supermetrics logo

Ready to connect Supermetrics?

Connect once. Every metric, data source, channel from Supermetrics becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.