Google Ads has a Salesforce connector. Why build something custom?

Use the native connector if it fits. It works on opportunity stages keyed on a gclid stored in Salesforce. Custom bridges earn their keep when leads come in without a gclid, when you also advertise on Meta and Microsoft, or when the revenue you care about lives in custom objects.

Does my Salesforce edition have API access?

API access depends on your edition. Enterprise and above include it; some lower editions need an add-on. We check this on the first call.

The click ID is on the lead, but the revenue is on the opportunity. How does that work?

When a lead converts, we follow it to the contact and opportunity it became, so the opportunity's stage and amount can be sent with the original click ID.

Integrations · CRM

Salesforce to Google Ads and Meta: bid on closed-won, not form fills.

Salesforce knows which leads your team closed and for how much. We send that back to your ad platforms so they find more of them.

What we pull from Salesforce

● Leads and contacts with lead source
● Opportunities, stages, amounts, and close dates
● Stored click IDs on the lead record
● Converted-lead relationships (lead → contact → opportunity)
● Accounts and custom fields for segmentation

Where it goes

Google Ads Offline conversions with revenue, enhanced conversions, Customer Match lists
Meta (Facebook + Instagram) Conversions API events with revenue, custom audiences, lookalike seeds
Microsoft Ads Offline conversions keyed on msclkid or hashed email and phone

The Salesforce attribution gap

The click happens on a lead. The revenue happens on an opportunity weeks later, often after the lead has been converted, merged, or reassigned. Somewhere in that journey the original ad click gets lost, and the ad platforms never learn which campaigns produced revenue.

What we build

Capture. Click IDs and hashed contact info stored on the Salesforce lead from every web form and booking tool. See click IDs explained.
Follow the lead. Converted leads traced to their contact and opportunity, so the click ID follows the money.
Stage conversions. Opportunity stage changes (qualified, proposal, closed-won) sent as conversions with the opportunity amount or a predicted value for early stages.
Every platform. Google through the Data Manager API, Meta through the Conversions API, and Microsoft offline conversions, from one pipeline.
Audiences. Customers excluded from prospecting campaigns, closed-won accounts as lookalike seeds.

Built for small teams on big software

Plenty of 10- and 20-person companies run Salesforce without a Salesforce admin, let alone a data engineer. That’s the gap we fill: someone who understands both the Salesforce data model and how ad platforms learn, and can wire the two together without a six-month project.

Questions we get

Google Ads has a Salesforce connector. Why build something custom?: Use the native connector if it fits. It works on opportunity stages keyed on a gclid stored in Salesforce. Custom bridges earn their keep when leads come in without a gclid, when you also advertise on Meta and Microsoft, or when the revenue you care about lives in custom objects.
Does my Salesforce edition have API access?: API access depends on your edition. Enterprise and above include it; some lower editions need an add-on. We check this on the first call.
The click ID is on the lead, but the revenue is on the opportunity. How does that work?: When a lead converts, we follow it to the contact and opportunity it became, so the opportunity's stage and amount can be sent with the original click ID.

How the pieces work

Guide

Running ads off Salesforce data?

Tell us what you use and where you advertise. We'll tell you what's possible and what it takes.

Talk to us