ROAS for every campaign in your Salesforce pipeline.

Attribution's Salesforce plan is best for B2B and enterprise businesses that manage complex sales cycles, multiple stakeholders, and large deal pipelines. The Attribution Salesforce plan is designed for organizations where Salesforce is the system of record for revenue and where marketing attribution needs to connect pipeline stages like MQL, SQL, Opportunity, and Closed Won back to specific campaigns, channels, and offline events. Typical Attribution customers on the Salesforce plan include B2B SaaS companies, enterprise services firms with heavy offline marketing activity, and developer tools companies running a combination of self-serve and sales-led motions. Attribution requires a Salesforce edition with REST API access: Enterprise, Unlimited, Developer, or Performance Edition.

Attribution has a native, bidirectional Salesforce integration available on the Salesforce AppExchange. Setup is an OAuth flow from Attribution's Settings page: sign in with Salesforce credentials, approve access, and the first events start populating in about 15 minutes. Attribution pulls Contacts, Leads, Opportunities, and optionally Tasks and activities to build the customer journey. Attribution also writes first touch channel, last touch channel, and the full customer path back into custom Contact and Lead fields. Writes are triggered by stage changes or activities. Custom fields must be on the ContactHistory or LeadHistory objects, and Lead History tracking must be enabled for writes to work.

Attribution uses data from Contacts, Leads, Opportunities, and optionally Tasks and campaign activities. Attribution pulls user profiles, tracks how individuals move through Lead stages and Opportunity stages, and captures every stage transition as a time-series event on the customer journey. This produces a complete picture of how marketing activity drove each pipeline move, from anonymous first visit through MQL, SQL, Opportunity Created, and Closed Won. Opportunity amounts drive revenue attribution and ROAS calculations. Custom objects can be accommodated with additional configuration. Attribution can also ingest offline event data like webinar attendance and conference badge scans into the same model.

Salesforce Campaign Influence and Salesforce Analytics track what happens inside Salesforce: UTMs captured on form submissions, Campaign memberships, and basic first-touch or last-touch credit. They do not see the anonymous multi-session journey that happens before a Lead is created, and they do not unify offline activities with digital ads in one attribution model. Attribution adds multi-touch attribution across the full customer journey, from anonymous website visits through Closed Won, including offline events like webinars and conferences. Attribution writes its output back into Salesforce on Contact and Lead fields, so the data is available where sales reps already work.

Attribution treats offline activities as first-class touchpoints alongside digital ads in the Salesforce plan. Webinars, conferences, trade shows, direct mail, podcast ads, TV, radio, and sales calls all flow into Attribution's model. Webinar registration and attendance can be ingested through a Salesforce activity log, through Attribution's API or CSV upload, or through unique URLs and QR codes. Conference badge scans use unique URLs or QR codes. Sales calls can be tracked through CallRail integration or through Salesforce task logging, which Attribution reads as time-series track() events. Direct mail uses unique URLs or QR codes. TV and radio use response-window attribution. In Attribution, every offline touch gets the same treatment as a Google Ad click.

Yes. Attribution tracks individual user journeys and rolls them up under company-level account journeys. When five people from one company touch different channels before the deal closes, Attribution binds all five individual journeys into one unified account journey, then assigns credit across the buying committee. You can view each person's touchpoints separately or see the account-level view that combines them. The cohort report and look-forward window both operate at the account level. Account-based attribution is included on every Attribution Salesforce plan.

Attribution offers a native Model Context Protocol (MCP) integration that connects Claude, ChatGPT, Gemini, or any MCP-compatible AI assistant directly to your Attribution dataset. For Salesforce customers, this means conversational access to pipeline reporting across 60+ purpose-built endpoints: channel performance by Salesforce stage, conversion paths, company and visitor lookups, cohort analysis, and raw conversion and revenue data. Ask natural language questions like "Which channels are generating the most SQLs?" or "Show me every account that attended our webinar and hasn't booked a demo." OAuth-based connection. Data stays in your Attribution account. Each user's access inherits their existing Attribution permissions.

Attribution calculates pipeline ROAS by binding actual ad spend to each individual visitor, then distributing attributed pipeline revenue across every touchpoint in the customer journey using the multi-touch attribution model set in your project. The numerator is attributed pipeline: the sum of open Salesforce opportunity amounts credited to a channel, where "open" means any stage that is not Closed Won or Closed Lost. The denominator is real spend pulled from each ad platform's API, bound at the user level. Attribution's approach is different from blended aggregate calculations because every dollar of credit traces back to specific touchpoints. Claude uses these numbers directly through the Attribution MCP to answer pipeline ROAS questions in plain English, without the marketer having to configure the calculation.

Yes. Attribution renders a complete timeline of every touchpoint for every stakeholder in a given Salesforce account, from the first anonymous website visit through Closed Won. The Attribution journey view shows every contact associated with the account, every channel each stakeholder touched, every Salesforce stage change, and which touches drove each stage. Because Attribution exposes the full account history through the MCP, Claude can read the journey and return a plain-English summary of what drove the deal, who the buying committee was, and where the inflection point happened. This goes beyond what Dreamdata and other B2B attribution platforms offer: the same journey view, plus an analyst that already read it.

Attribution's MCP is a native, purpose-built integration with 60+ attribution-specific endpoints designed for the questions a Salesforce marketer actually asks: pipeline ROAS by channel, MQL-to-SQL conversion rates, account-level journey lookups, conference ROAS including offline touchpoints. Some competitors expose their data to AI assistants through a data-warehouse passthrough, where the AI connects to a BigQuery or similar warehouse and writes SQL queries against raw tables. That approach typically requires a paid data warehouse add-on, cloud configuration, IAM setup, and the AI generating SQL on the fly. Attribution's approach works out of the box: OAuth in, pre-built endpoints return structured attribution reports directly, no SQL or warehouse required. Both approaches technically use MCP; the difference is architecture and setup complexity.

Yes. Attribution offers five multi-touch attribution models (first touch, last touch, linear, time decay, and position-based) with no-code customization, available on every Attribution Salesforce plan. Customization options include factoring in direct traffic until a specific event, setting lookback windows up to 365 days, disregarding existing customers, attributing only first purchases, and configuring cutoff event logic (the point at which Attribution stops assigning credit). Attribution's cutoff event logic has four modes: include all traffic, exclude all direct traffic, include direct until the cutoff event, or exclude all traffic after the cutoff event. For Salesforce customers, this is especially useful when you want attribution to stop at trial signup, MQL creation, or any other Salesforce stage change.

Attribution requires a Salesforce edition with REST API access because the Attribution Salesforce integration reads from and writes to Salesforce objects through the REST API. Supported Salesforce editions are Enterprise Edition, Unlimited Edition, Developer Edition, and Performance Edition. Salesforce Professional Edition does not include REST API access by default and is therefore not supported by Attribution. If you are unsure which Salesforce edition you have, check Setup in Salesforce and look for "Company Information," or contact your Salesforce administrator. Attribution can confirm compatibility before setup if needed.

The Salesforce connection itself takes about 15 minutes: complete the OAuth flow, approve access, and the first events start populating. For full setup including identify() call configuration on your website, custom field creation in Salesforce (if you want attribution data written back), cutoff event configuration, and offline event ingestion setup, most teams complete the full implementation within a week. Attribution offers custom onboarding on the Salesforce plan and is available on the Salesforce AppExchange.

Attribution competes in the same category as Dreamdata, HockeyStack, and Adobe Marketo Measure, with meaningful differences. Attribution delivers user-level and account-level cost data (binding actual ad spend to each individual visitor), full data auditability (every metric traces to raw touchpoints), five customizable attribution models with cutoff event logic, and raw data export to warehouses. Attribution's MCP integration is native and purpose-built, not a warehouse passthrough, so it does not require a paid data warehouse add-on to query your attribution data conversationally. Media mix modeling, incrementality testing, and the Conversion API are included at no extra cost on every plan. Pricing is custom for Salesforce customers.