CRM
In an enterprise pipeline the click and the signature can be two quarters apart, and by the time Salesforce shows Closed Won the ad account has long since written the campaign off. Attribi reads your Opportunities on a schedule and turns the ones that reach a qualified or won stage into offline conversions on every ad platform you have connected, with the Opportunity amount and currency attached. It reads your org as it is configured, including the stage names your team invented.
No credit card required · 5-minute setup
A won Opportunity becomes a closed-won conversion carrying its amount and currency. It works even if your team renamed the won stage or runs several sales processes, and you can override which stages count as won if your org does something unusual.
At connect time Attribi lists the Opportunity stages that actually exist in your org and you pick which ones mean qualified. Nothing has to be renamed to match a vendor vocabulary, and no free-text guessing decides whether a deal counted.
Attribi creates 16 custom fields on Lead, then creates and assigns a permission set so the connecting user can actually read and edit them. First touch, last touch, campaign, and journey are written as leads convert.
Attribi ties a won Opportunity back to the person it already knows using the email and phone number on the contact attached to that Opportunity, then hashes both before any upload. Contacts with accurate email addresses match best.
Planned, not live today. Listed so you can see what this integration does not do yet, before you sign up.
A Web-to-Lead form can capture a Google or Meta click ID onto the lead, but Attribi does not use that click ID when it matches revenue from a won Opportunity. Salesforce revenue matching runs on email and phone today.
Not yet available.
Authorize Salesforce from the Connections page against a sandbox or a production org, and choose whether Attribi may create leads or should only enrich records that already exist. You can connect a sandbox first and repeat the same steps in production.
One button creates the 16 custom fields on the Lead object, builds a permission set granting read and edit on each of them, and assigns it to you. The connecting user needs Customize Application; without it Attribi stops and names the fields to create by hand rather than half-finishing.
Pick the stages that mean qualified from your own stage list. Won stages are recognized without configuration, so the only decision left is where mid-funnel starts for your team. From then on the pull runs on a schedule and uploads on its own.
Stages Attribi supports for Salesforce.
CRM
HubSpot ad attribution in both directions: campaign data is written onto the contact your reps already read, and closed deal revenue is pulled back out.
Ad platform
Upload closed-won revenue from your CRM to LinkedIn through the Conversions API, so long B2B sales cycles show up in the campaigns that started them.
Ad platform
Google Ads offline conversion tracking: send qualified leads and closed-won revenue from your CRM, so your account sees CRM-verified outcomes, not just form fills.
Yes. Attribi does not look for a stage literally called Closed Won, it uses your org’s own definition of which stages are won, so renamed stages, custom sales processes, and multiple record types are all handled without configuration. If your org does something genuinely unusual you can also name the won stages explicitly and Attribi will use your list instead.
Not by click ID. When Attribi reads a won Opportunity it matches on the contact’s email and phone number, which are hashed before they reach any ad platform. Meta, LinkedIn, Microsoft, TikTok, and Snapchat all accept those hashed identifiers on their own. Google Ads accepts them only once you have accepted its Enhanced Conversions terms inside your Google Ads account; until you do, Google rejects any upload carrying hashed identifiers, and a Salesforce-only setup has no click ID to fall back on. Match rates on hashed identifiers are lower than a click ID would give in every case. Installing the Attribi script is what recovers click-level matching, because the click ID is then held against the visitor rather than looked for in Salesforce.
Professional, Enterprise, Unlimited, and Developer orgs, where the connecting user has Customize Application. Essentials and Group Edition do not expose the API used to create custom fields, so Attribi cannot build them for you there. It fails loudly with the exact field list to create manually, and once the fields exist everything else behaves identically.
Only as much as you allow. In full mode a converting visitor becomes a lead if Salesforce does not already have one. In attribution only mode Attribi never creates a record: it looks for a match, writes attribution onto it if one exists, and otherwise does nothing. Either way the only fields Attribi writes are the ones it created.
Not for revenue. Qualified and closed-won outcomes are read out of Salesforce and uploaded to your ad platforms whether or not any script is installed, so you can start without asking web engineering for anything. The script is what adds the visit history, the multi-touch path, and click-level matching.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free forever up to 1,000 visitors