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.
The same path your dashboard uses, from first visit to closed deal. Your agent reads it directly.
Page views, sessions, referrers, UTM parameters and ad click ids, linked to the person once they sign up.
CRM stages, booked meetings, ad spend and revenue sync from the tools you already use.
Each session gets one of 22 channels, including traffic from AI assistants as its own channel.
First touch, last touch, position based, linear and two time decay models, all on the same rows.
Plug in your CRM, ad platforms and calendar. Stages, meetings, spend and revenue flow into Source and meet the visits that came before them.
View-through, outbound, organic search and multi-touch credit, all on the same row-level data your agent queries.
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.
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.
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.
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.
Sessions, touches, funnel stages, ad spend and revenue sit in tables your agent can query with SQL. A few of them:
One row per touch, with a weight for each of the six models.
Every session with channel, campaign, UTMs and landing page.
One row per contact, with conversion date and funnel stage.
Contacts entering each funnel stage, by date.
Daily spend, clicks and conversions per paid campaign.
Payments tied to the contact who made them.
Daily visits per channel, bots excluded.
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.
Each row of fact_session_attribution carries a weight for every model, so your agent can compare them on the same data.
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
Source is a remote MCP server. Sign in with OAuth, or send a read-only API key as a Bearer token.
The pixel records page views, sessions, referrers, UTM parameters and ad click ids, and links visitors to the people who sign up.
Put it in the shared layout so no page is missed, including sign-up pages.
It does not block rendering. Single-page apps need nothing extra.
get_pixel_installation_guide returns the snippet and steps for your site.
<!-- 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 -->Source has completed a SOC 2 Type II examination and is ISO 27001 certified. You can request our latest SOC 2 report under NDA.
SOC 2 Type IIExamination completed
ISO 27001CertifiedData is encrypted in transit with TLS and at rest. It is never sold or used to train external models.
Clients sign in with OAuth 2.1 and PKCE. Revoke a connection any time in Settings, then API keys, then Connected apps.
Query tools are read-only and limited to the websites you approve. Only org admins can save a funnel.
Single sign-on, role-based access and audit logs. Export or delete your data at any time.