Integrations · Analytics

Connect Aura to Well

Name: Aura entities in Well
Creator: Well

Combine Aura session, visitor, and page view with the CRM, payment, and product signals already in your workspace.

What Well pulls from Aura

Aura feeds session, visitor, page view into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Aura’s access.

From Aura	In Well	Relation
Session	Engagement record	Becomes
Visitor	Person	Resolves to
Page view	Behavior signal	Feeds

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Aura → Well

What Well does with your Aura connection

Connect

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

Sync

Well brings session, visitor, and page view in from Aura 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 Aura entity into engagement record, person, and behavior signal, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Aura lands in the workspace as engagement record, person, and behavior signal you can search, chart, and automate.

Questions Aura unlocks

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

Ask Well

Ask anything about your Aura connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Aura connection…

Connect Aura in three steps

01
Authorise Aura via MCP
From Well's Connections panel, search for Aura and click Connect. Well discovers Aura's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Aura's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.auraintelligence.com/mcp
02
Map your entities
Well's MCP client discovers session, visitor, and page view from Aura that Aura'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 Aura records. Because Aura 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 Aura records happens in the background.

How Aura stays secure with Well

Well connects to Aura's MCP server (mcp.auraintelligence.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 Aura secret. Tokens are scoped to the session, visitor, and page view Aura exposes and refreshed server-side. Reads only, Well cannot modify or delete Aura records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.auraintelligence.com/mcp

Read Aura records
Resources the Aura MCP server exposes, scoped by your OAuth approval.
granted
Resolve session, visitor, and page view across your stack
Match identifiers in Aura against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Aura records
Not granted; Aura is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Aura passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

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

Frequently asked questions about Aura and Well

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

Well brings in session, visitor, and page view from Aura and reshapes each entity into your workspace: session becomes engagement record; visitor becomes person. Every record arrives with the source identifier preserved, so Aura stays the source of truth while Well lets you query the data alongside the rest of your stack.

Each Aura metric or event is joined to the customer it represents using identifier overlap with your CRM. Asking "what's the engagement profile of our top-20 ACV customers in Aura" returns the metric breakdown by cohort, joined to the deal and revenue records, without manual segment exports.

Every workspace engagement record built from Aura carries the source session identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Aura record; from Aura, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

Well combines live Aura events with periodic reconciliation reads of session, visitor, and page view. New rows appear within seconds when Aura pushes them; periodic reads catch anything a push missed. The first connect backfills history from Aura in the background.

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

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