Visit to deal, in one data layer your agents can query.

The Source pixel records every visit. Your CRM, calendar and ad platforms add the rest. Source puts it on one path and serves it to your agents over MCP.

Free up to 100K events a month. No credit card.
PixelSessions, page views, UTMs, ad click ids
CRMContacts, stages, deals
CalendarBooked meetings
Ad platformsSpend, clicks, conversions
↓
Source data layer
Every touch on one path, with six attribution models on each row.
↓
ClaudeChatGPTCursorClaude Code
api.source.app/mcp

How attribution works in Source

The same path your dashboard uses, from first visit to closed deal. Your agent reads it directly.

01

The pixel records every visit

Page views, sessions, referrers, UTM parameters and ad click ids, linked to the person once they sign up.

02

Integrations add the rest

CRM stages, booked meetings, ad spend and revenue sync from the tools you already use.

03

Every touch lands on one path

Each session gets one of 22 channels, including traffic from AI assistants as its own channel.

04

Six models score each touch

First touch, last touch, position based, linear and two time decay models, all on the same rows.

What Source tracks on each path

View-through, outbound, organic search and multi-touch credit, all on the same row-level data your agent queries.

View-through conversions

Source credits the ad a buyer saw but never clicked when that buyer later books a meeting or closes a deal. View-through sits next to click-through on the same path, so you can compare the two.

Outbound campaign tracking

Source records the UTMs and referrer on every visit, so tagged links in your outbound sequences land on the same path as ads and content. Add calls and meetings as offline touches, then ask which sequences sourced pipeline.

Organic keyword searches

Source pulls organic queries from Google Search Console and estimates which query brought in each contact, with a confidence score. See which searches turn into meetings and deals.

Multi-touch attribution

Every touch carries a weight for six models: first touch, last touch, linear, position based, and linear and exponential time decay. Switch models to see how credit moves between channels.

One ledger, from visit to deal

Sessions, touches, funnel stages, ad spend and revenue sit in tables your agent can query with SQL. A few of them:

fact_​session_​attribution

One row per touch, with a weight for each of the six models.

dim_​session

Every session with channel, campaign, UTMs and landing page.

dim_​contact

One row per contact, with conversion date and funnel stage.

fact_​funnel_​event

Contacts entering each funnel stage, by date.

fact_​campaign

Daily spend, clicks and conversions per paid campaign.

fact_​revenue

Payments tied to the contact who made them.

agg_​visit_​days

Daily visits per channel, bots excluded.

agg_​customer_​metrics_​monthly

Monthly churn, ARPU and LTV.

Paid campaign tables carry both the ad platform's conversions and the conversions Source tracked, so your agent can show where a platform overcounts.

Six models on every touch

Each row of fact_session_attribution carries a weight for every model, so your agent can compare them on the same data.

First touchfirst_touch_weight
Last touchlast_touch_weight
Position basedposition_based_weight
Linearlinear_weight
Time decay, exponentialtime_decay_exp_weight
Time decay, lineartime_decay_linear_weight
Credit by channel, first touch vs linearCopy
SELECT a.channel,
       ROUND(SUM(a.first_touch_weight), 1) AS first_touch,
       ROUND(SUM(a.linear_weight), 1)      AS linear
FROM fact_session_attribution a
JOIN dim_contact c USING (contact_id)
WHERE c.conversion_date >= TIMESTAMP(DATE_SUB(CURRENT_DATE(), INTERVAL 89 DAY))
  AND COALESCE(a.bot_risk, 0) = 0
GROUP BY a.channel
ORDER BY linear DESC
Example query against the published schema.

Works in the agent you already use

Source is a remote MCP server. Sign in with OAuth, or send a read-only API key as a Bearer token.

https://api.source.app/mcp
ClaudeAdd Source from the Connectors Directory, or add the URL as a custom connector.
ChatGPTAdd Source as a connector with the MCP URL.
CursorAdd the URL to ~/.cursor/mcp.json and sign in.
Claude Codeclaude mcp add --transport http source https://api.source.app/mcp

Eight tools, all read-only

askrun_sqldescribe_datalist_websitesconfigure_funnelget_pixel_installation_guideget_funnel_configuration_guidefeedback

See what each tool does

One snippet for every page

The pixel records page views, sessions, referrers, UTM parameters and ad click ids, and links visitors to the people who sign up.

1

In the head of every page

Put it in the shared layout so no page is missed, including sign-up pages.

2

Loads asynchronously

It does not block rendering. Single-page apps need nothing extra.

3

Or let your agent do it

get_pixel_installation_guide returns the snippet and steps for your site.

Source pixelCopy
<!-- Start Source Pixel Snippet -->
<script>!function(e,s,t,n,c,i,o,r,u){e[c] || ((o = e[c] = function () { o.process ? o.process.apply(o, arguments) : o.queue.push(arguments) }).queue = [], o.t = +new Date, (r = s.createElement(t)).async = 1, r.src = "https://pixel.source.app/versions/3/sourcepixel.min.js?t=" + 864e5 * Math.ceil(new Date / 864e5), (u = s.getElementsByTagName(t)[0]).parentNode.insertBefore(r, u))}(window,document,"script",0,"sourcePixel"),sourcePixel("init","YOUR_WEBSITE_ID"),sourcePixel("event","pageload")</script>
<!-- End Source Pixel Snippet -->
Replace YOUR_WEBSITE_ID with the id from your Source dashboard.

Enterprise-grade security

Source has completed a SOC 2 Type II examination and is ISO 27001 certified. You can request our latest SOC 2 report under NDA.

AICPA SOC 2 seal for service organizationsSOC 2 Type IIExamination completed
ISO 27001 certification markISO 27001Certified
Read our security overview
Encrypted

Data is encrypted in transit with TLS and at rest. It is never sold or used to train external models.

OAuth for MCP

Clients sign in with OAuth 2.1 and PKCE. Revoke a connection any time in Settings, then API keys, then Connected apps.

Scoped queries

Query tools are read-only and limited to the websites you approve. Only org admins can save a funnel.

Access controls

Single sign-on, role-based access and audit logs. Export or delete your data at any time.

Give your agents the attribution data they need.