Integrations · MarketingConnect Bitly to Well
Attribute Bitly shortened link, click event, and campaign tag to revenue in your CRM, with channel and cohort breakdown ready.
What Well pulls from Bitly
Bitly feeds shortened link, click event, campaign tag into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Bitly’s access.
| From Bitly | In Well | Relation | |
|---|---|---|---|
| Shortened link | Tracked URL | Becomes | |
| Click event | Engagement record | Captures as | |
| Campaign tag | Attribution input | Feeds |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Bitly → Well
What Well does with your Bitly connection
Connect
Connect Bitly over OAuth (MCP DCR): Well registers a client through Bitly's OAuth Dynamic Client Registration and you approve on Bitly's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings shortened link, click event, and campaign tag in from Bitly 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 Bitly entity into tracked URL, engagement record, and attribution input, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Bitly lands in the workspace as tracked URL, engagement record, and attribution input you can search, chart, and automate.
Questions Bitly unlocks
Ask in plain language. Well answers from your connected Bitly connection, resolved against the rest of your stack.
Ask anything about your Bitly connection
Ask about your Bitly connection…
Connect Bitly in three steps
- 01
Authorise Bitly via MCP
From Well's Connections panel, search for Bitly and click Connect. Well discovers Bitly's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Bitly's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapi-ssl.bitly.com/v4/mcp
- 02
Map your entities
Well's MCP client discovers shortened link, click event, and campaign tag from Bitly that Bitly'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 Bitly records. Because Bitly 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 Bitly records happens in the background.
How Bitly stays secure with Well
Well connects to Bitly's MCP server (api-ssl.bitly.com/v4/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Bitly secret. Tokens are scoped to the shortened link, click event, and campaign tag Bitly exposes and refreshed server-side. Reads only, Well cannot modify or delete Bitly records.
- granted
Read Bitly records
Resources the Bitly MCP server exposes, scoped by your OAuth approval.
- granted
Resolve shortened link, click event, and campaign tag across your stack
Match identifiers in Bitly against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Bitly records
Not granted; Bitly is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Bitly passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Bitly and Well
From Well, open Connections, find Bitly, and click Connect. Well discovers the OAuth metadata at api-ssl.bitly.com/v4/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Bitly's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in shortened link, click event, and campaign tag from Bitly and reshapes each entity into your workspace: shortened link becomes tracked URL; click event becomes engagement record. Every record arrives with the source identifier preserved, so Bitly stays the source of truth while Well lets you query the data alongside the rest of your stack.
Bitly audience segments resolve to the workspace customer entities they target. A campaign aimed at "enterprise tier US" links to the actual enterprise-tier US customer entities in your CRM, so engagement-to-deal-stage joining happens without manual cohort matching.
Yes. Bitly campaign tags are indexed in your workspace as attribution input, so questions like "show me last week's campaign tags from Bitly" return them with the original Bitly link, the workspace context, and any related records (counterparty, period, attached document) joined inline.
Well combines live Bitly events with periodic reconciliation reads of shortened link, click event, and campaign tag. New rows appear within seconds when Bitly pushes them; periodic reads catch anything a push missed. The first connect backfills history from Bitly in the background.
Open Connections > Bitly in Well and click Disconnect. Well calls Bitly's token revocation endpoint and stops calling Bitly immediately on its side; provider-side propagation to Bitly's admin panel varies by provider. The shortened link, click event, and campaign tag Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Bitly 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 Bitly
More in Marketing
AirOps
Connect AirOps to Well to sync campaign data and marketing analytics.
Klaviyo
Connect Klaviyo 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 Bitly?
Connect once. Every shortened link, click event, campaign tag from Bitly becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.