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.
Step-by-step walkthrough: Salesforce to Google Ads Offline Conversion Import Breaks Inside Salesforce, Not Inside Google Ads · Salesforce to Meta Offline Conversions: Send Every Stage Through the Conversions API, Not Just the Win · Salesforce to Meta Conversions Not Showing? Troubleshoot Delivery, Matching and Attribution · CRM Offline Conversion Tracking QA Checklist: Prove Each Step Before You Change Bidding · Salesforce Opportunity Attribution: Contact Roles, Repeat Deals and Revenue Coverage
Key points
Connect Salesforce and Meta Ads to Attribi and choose which Opportunity stages mean qualified. Attribi then sends qualified and won Opportunities to Meta through the Conversions API. A qualified Opportunity arrives as a Lead event and a won Opportunity arrives as a Purchase event carrying the Opportunity amount.
There is no file to export and no scheduled report to maintain. Once a day Attribi reads the Opportunities that changed since its last run and works out which ones crossed a stage you care about.
The person is identified with the email and phone number on the contact attached to the Opportunity. Both are SHA-256 hashed before they leave Attribi, and Meta accepts those hashed identifiers on their own, so a deal can be reported even when no Facebook click ID was ever stored in Salesforce.
Full walkthrough: send Salesforce closed-won deals back to Meta AdsSalesforce offline conversion tracking means reporting sales outcomes that happen inside Salesforce, such as a qualified Opportunity or a signed deal, back to the ad platform that produced the lead. It is called offline because the outcome happens after the website visit, in a CRM, where the ad platform's own pixel cannot see it.
Without it, an ad account only knows that a form was submitted. It cannot tell a lead that became a six-figure contract from one that never answered the phone, so every campaign is judged on cost per lead.
With it, each campaign can be read against qualified pipeline and closed revenue. The data already exists in Salesforce. The work is getting it to the ad platform in the format, and with the identifiers, that platform accepts.
Attribi reads Opportunities: the stage, the amount and the contact attached through the Opportunity's contact roles, preferring the primary contact. It uploads a conversion when an Opportunity reaches a stage you mapped as qualified, and again when it is won, with the amount attached on the won event.
Won detection uses your org's own definition of a won stage, so a renamed stage or a second sales process does not stop uploads. Qualified is whatever you pick from your real stage list at connect time.
Two limits are worth knowing before you rely on the numbers. A won Opportunity with a blank or zero amount is recorded but uploads no revenue. Each contact is reported once per stage, so a later renewal or expansion deal for a contact that already has a won deal is not uploaded as a second conversion today. Currency comes from the Opportunity on a multi-currency org and from your org's own currency setting on a single-currency org.
An Opportunity with no contact role has no email or phone to match on, so Attribi records the deal but cannot tie it to a person. If your team creates Opportunities without contacts, add a primary contact to the deals you want counted.
Every ad platform you connect: Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, TikTok Ads and Snapchat Ads. One Salesforce connection feeds all of them, and each upload is independent, so a rejected upload on one platform does not hold back the others.
Meta, LinkedIn, Microsoft, TikTok and Snapchat accept hashed email and phone without further setup. Google Ads accepts them only after you accept its Enhanced Conversions terms inside your Google Ads account, so do that before expecting Salesforce revenue to appear there.
Full walkthrough: Salesforce offline conversions in Google AdsBy the contact's email and phone number, hashed before upload. Attribi does not currently use a click ID stored in Salesforce when it matches revenue from a won Opportunity. Click-level matching comes from the Attribi script, which records the click ID against the visitor on your own domain and keeps it there.
This matters because a click ID stored on a Salesforce Lead is easy to lose when the Lead is converted into a Contact and an Opportunity. Holding it against the visitor, outside Salesforce, means lead conversion cannot break the link.
If you install nothing on your website, qualified and won outcomes still upload on hashed email and phone. Expect lower match rates than a click ID gives, and expect accurate contact emails to matter more than anything else you can tune.
A Professional, Enterprise, Unlimited or Developer org, and a connecting user with the Customize Application permission. You can connect a sandbox first and repeat the same steps in production.
Essentials and Group Edition do not expose the API used to create custom fields. Attribi tells you exactly which fields to create by hand there, and everything else behaves the same once they exist.
Uploads to ad platforms and CRM revenue connections are paid plan features. The pricing page lists what each plan includes.
A CSV upload is a manual job that someone has to remember, format correctly for each ad platform and repeat. Attribi runs the same loop daily without a person in it, applies each platform's own hashing and event format, and records the result of every upload per lead and per platform.
It also does two things an export cannot. It writes first touch, last touch, campaign and journey onto the Salesforce Lead so sales can see where a record came from, and it keeps the multi-touch path so the same closed deal can be read under first touch, last touch, linear and position-based models.
Stages Attribi supports for Salesforce.
Ad platform
Meta Conversions API for CRM: send qualified leads and closed-won revenue from your CRM to Meta server side, with hashed email, phone, and Instant Form lead IDs.
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.
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.
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.
It is recorded but no revenue conversion is uploaded, because there is no figure to send. Attribi only uploads a closed-won conversion when the Opportunity amount is greater than zero. If your team fills in the amount after closing, or tracks value only on line items, make sure the Opportunity amount is populated on the deals you want counted.
Updated
Sign up and connect it from the Connections page.
Start FreeNo credit card · Free up to 500 visitors a month