How to Send Salesforce Pipeline Stages to Google Ads and Meta
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "BlogPosting",
"headline": "How to Send Salesforce Pipeline Stages to Google Ads and Meta",
"url": "https://mattkundodigitalmarketing.com/blog/salesforce-pipeline-stages-google-ads-meta/",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://mattkundodigitalmarketing.com/blog/salesforce-pipeline-stages-google-ads-meta/"
},
"author": {
"@type": "Person",
"name": "Matt Kundo",
"jobTitle": "Founder and Growth Marketing Manager",
"worksFor": {
"@type": "Organization",
"name": "Matt Kundo Digital Marketing"
},
"knowsAbout": [
"Search engine optimization",
"Generative engine optimization",
"AI search visibility",
"Digital marketing"
]
},
"description": "Send Salesforce opportunity stages to Google Ads with Data Manager and to Meta via the Conversions API. Steps, a verification checklist and dated costs.",
"publisher": {
"@type": "Organization",
"name": "Matt Kundo Digital Marketing",
"url": "https://mattkundodigitalmarketing.com/"
},
"datePublished": "2026-11-16",
"dateModified": "2026-11-16",
"image": "https://mattkundodigitalmarketing.com/assets/blog/salesforce-pipeline-stages-google-ads-meta/hero.jpg"
},
{
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Can one tool send Salesforce opportunity stages to both Google Ads and Meta?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Not through one native setup. Google's direct connection only feeds Google Ads, and Meta's app only feeds Meta. Zapier is the closest shared layer: Google lists it as a third-party route in Data Manager, and Meta documents a Zapier implementation for its CRM integration."
}
},
{
"@type": "Question",
"name": "Does the old Salesforce integration in Google Ads still work?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Google ended support for the legacy Salesforce integration on May 31, 2025, and in most cases migrated existing conversion actions to Data Manager automatically. If you still see a \"Salesforce\" tab under Goals, Google's upgrade FAQ walks through the manual migration."
}
},
{
"@type": "Question",
"name": "Should I use GCLID import or enhanced conversions for leads?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Use enhanced conversions for leads where you can. Google calls GCLID-based offline conversion import a legacy feature, and enhanced conversions for leads can match on GCLID, email or phone. Map every identifier you have."
}
},
{
"@type": "Question",
"name": "How long can my sales cycle be?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Google's GCLID import needs the click-to-conversion cycle to be under 90 days. Meta needs each event's event_time to be within 7 days of when you send it, and it recommends optimizing toward a stage that happens within 28 days of lead generation. If your typical deal takes six months to close, bid on an earlier rung such as opportunity created and keep Closed Won for reporting."
}
},
{
"@type": "Question",
"name": "Does Meta's Salesforce app send opportunity stages?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Partly. Meta's developer guide maps Opportunity StageName to event names, but only for Opportunities created by converting a Lead, and the app is built for Meta lead ad leads. Meta's Help Center frames the app around lead stages and says the feature may not be available to every account yet."
}
}
]
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://mattkundodigitalmarketing.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Blog",
"item": "https://mattkundodigitalmarketing.com/blog/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Salesforce stages to Google Ads and Meta",
"item": "https://mattkundodigitalmarketing.com/blog/salesforce-pipeline-stages-google-ads-meta/"
}
]
}
]
} To send Salesforce pipeline stages to Google Ads, connect Salesforce in Google Ads Data Manager and create one conversion action for each Opportunity stage you care about. Meta takes stage changes through its Conversions API, and the route that works depends on where your leads start. That's the Salesforce Google Ads integration in two sentences, and it fits inside the wider measurement setup I cover in my guide to Google Analytics 4.
This guide is built from the platforms' own documentation, and each step links to the page it comes from. I read every page on November 11, 2026. Vendor menus move, so if a label below has changed, the linked page is the source of truth.
Key takeaways
- Google ended support for its legacy Salesforce integration on May 31, 2025. The current route is the Salesforce connection in Google Ads Data Manager, which reads the Lead, Opportunity and Order objects.
- Google can turn a field change into a conversion, for example "when the Opportunity field Stage becomes Closed Won", and it takes the conversion time from Salesforce field history.
- Meta's Conversion Leads app for Salesforce is built for leads from Meta lead ads (instant forms). Demo requests from your own website go through the standard Conversions API instead.
- No single native setup sends opportunity stages to both platforms. Zapier is the closest shared layer, and both Google and Meta document it.
- The connectors cost little. The real costs are the Salesforce edition you need for API access and the hours it takes to capture click IDs cleanly.
Why send pipeline stages instead of form fills?
Sending pipeline stages means the ad platforms learn from leads your sales team accepted, not from every form submission. Google's Smart Bidding and Meta's delivery system optimize toward whatever conversion you report. If a demo request from a student counts the same as one from a VP of Sales, the algorithm buys more of whichever is cheaper.
Take a B2B SaaS funnel as an illustration. A company runs Google Search and Meta campaigns to two offers, a demo request and a free trial. Marketing scores leads into MQLs, sales development accepts some of them as SQLs, and account executives open opportunities for the ones with budget and timing. Suppose 1 in 5 demo requests becomes an opportunity. Then four out of five conversions the ad platforms learn from never turn into pipeline.
Sending the SQL and opportunity stages back gives both platforms a signal that tracks pipeline. It also gives you campaign reporting that matches the numbers your sales leader sees in Salesforce.
How does the data flow from Salesforce to the ad platforms?
The data flow is a chain. An ad click leaves an identifier on your site, your form writes it to a Salesforce Lead, the identifier follows the Lead into an Opportunity, and a scheduled job sends each stage change back to the platform with that identifier attached.

Google Ads Data Manager is Google's point-and-click tool for bringing customer data from outside Google, Salesforce included, into Google Ads. For Google Ads, the chain runs like this. Auto-tagging adds a gclid parameter to the landing page URL. A script on your site stores it and fills a hidden field on the form. Web-to-Lead, or your form tool, writes it to a custom GCLID field on the Lead along with the email address. When the Lead converts, a field mapping copies the GCLID onto the Opportunity. Field history records when the Stage field changed. Data Manager reads those changes on a schedule and imports each one as a conversion tied to the original click.
The Meta Conversions API is Meta's server-to-server channel for events, so a stage change in Salesforce can reach Meta without a browser involved. For Meta, the identifiers differ. Leads from Meta lead ads carry a Meta Lead ID. Leads from your website carry the fbc and fbp browser values plus an email address. A Salesforce app, Salesforce Data 360 or your own code then posts each stage change to the Conversions API as a server event.
Which Salesforce stages should you send?
Send two or three stages, not every stage. Before a stage becomes a conversion action, I run it through a four-part check I call the Stage Fit Test: volume, lag, window and timestamp.
- Volume: The stage has to happen often enough for bidding to learn from it. A stage that fires twice a month is a reporting metric, not a bidding signal.
- Lag: Measure the median days from ad click to the stage. A shorter lag means the platform learns faster.
- Window: The stage has to land inside the platform's limits. Google's GCLID import needs a click-to-conversion cycle under 90 days. Meta recommends that the stage you optimize toward for conversion leads happens within 28 days of lead generation.
- Timestamp: Salesforce has to record when the stage changed, which means field history tracking on Lead Status and Opportunity Stage.

For the illustrative SaaS funnel, a three-rung ladder could look like this:
| Rung | Salesforce object and field | Example event condition | Role in the ad account |
|---|---|---|---|
| Qualified lead | Lead, Status | Status becomes "Sales Accepted" | Fast, higher-volume signal |
| Opportunity created | Opportunity, Stage | Stage becomes "Discovery" | Pipeline signal for bidding |
| Closed won | Opportunity, Stage and Amount | Stage becomes "Closed Won", value from Amount | Revenue reporting and value-based bidding |

The conversions are only as clean as the stages behind them. If reps skip stages, or use "Discovery" to mean three different things, the conversion action inherits that mess. It's the same stage-definition problem in every CRM. Here's a CRM build for a B2B sales team, with deal stages that match the real sales process, done in HubSpot rather than Salesforce.
How do you send Salesforce stages to Google Ads?
You send Salesforce stages to Google Ads by preparing Salesforce, capturing the click ID on your forms, connecting Salesforce in Data Manager and creating one conversion action per stage. Google's Salesforce integration setup guide is the primary source for each step below.
Step 1: Check your edition, permissions and API access
The Data Manager connection needs a Salesforce login that meets Google's minimum permissions, plus the ability to enable API access, create custom fields and turn on field history tracking, according to Google's Salesforce data source requirements. Google suggests a System Administrator login for the easiest setup. Data Manager doesn't support Salesforce sandbox environments, so plan to test in production with a test lead.
Check API access before anything else. Salesforce's Sales Cloud pricing page lists the Web Services API as an additional $25 per user per month on suites that don't include it. Confirm your edition with your Salesforce admin before you scope the work.
Step 2: Add GCLID fields and turn on field history
Create a custom field named GCLID on both the Lead object and the Opportunity object. Google specifies the field name in capital letters, a length of 255 characters, and read-only access so users can't overwrite it. Map Lead.GCLID to Opportunity.GCLID so the value survives lead conversion.
Then enable field history tracking for Lead Status and Opportunity Stage. Data Manager takes each conversion's time from that history, so without it there's no timestamp to import.
Step 3: Capture the click ID and email on every form
Turn on auto-tagging in Google Ads so every click carries a gclid. Add GCLID as a hidden field on your Web-to-Lead form, then add Google's capture script to every page of the site. The script stores the gclid in the browser for 90 days and fills the hidden field when the form loads. Google notes that the form has to sit on the same domain as your landing pages for the script to work.
If leads pass through another tool on the way in, such as a marketing automation platform or a meeting scheduler, that tool has to pass the GCLID through to Salesforce. This is where most setups leak. Collect a business email on the form too, because enhanced conversions for leads can match on email and phone as well as GCLID.
Step 4: Connect Salesforce in Data Manager
In Google Ads, go to Tools, then Data manager, then + Connect Product. Search for Salesforce, choose Direct connection and click Authorize to sign in, as described in Google's legacy integration upgrade FAQ. Select Conversions as the use case and accept the customer data terms.
Data Manager needs a separate connection for each Salesforce object. If your stages span the Lead and Opportunity objects, you'll set up two connections and apply filters within each one.
Step 5: Create one conversion action per stage
Under the connection's Usage section, click + Add conversion action and define a custom event. Pick the object, then filter on the field change, such as Stage becomes Closed Won. Google names the action after the condition, for example "When the Opportunity field "Stage" becomes "Closed Won"".
On the revenue rung, map the Opportunity Amount field to conversion value. If you don't map a value, Google counts each conversion as 1. Choose enhanced conversions for leads when Google offers it. Google's own documentation is direct about the older method: "Offline conversion import is a legacy feature, and it doesn't have the durability features that enhanced conversions for leads offers." Map every identifier you have, which means GCLID, email and phone.
Step 6: Schedule it daily and choose which stage bids
Google recommends running Salesforce integrations on a daily schedule. I'd keep new stage actions as secondary conversion goals while you compare their counts against Salesforce reports. Once the numbers line up, make the stage you want to optimize toward primary and leave the others as secondary for reporting.
How do you send Salesforce stages to Meta?
You send Salesforce stages to Meta through the Conversions API, and the right route depends on where the lead started. Leads from Meta lead ads can use Meta's Salesforce app. Website demo requests need a standard Conversions API setup, built with Salesforce Data 360, a middleware tool or your own code.
| Route | Best fit | What it needs | Main limit |
|---|---|---|---|
| Meta Conversion Leads app for Salesforce | Leads from Meta lead ads (instant forms) | Meta leads synced into Salesforce with the Meta Lead ID or customer information | Opportunity events only for Opportunities converted from a Lead, no historical records, and Meta says it may not be available to every account yet |
| Salesforce Data 360 Meta Conversions API activation | Teams already licensing Data 360 | A Data 360 license with Ad Audiences entitlements | License cost and setup inside Data 360 |
| Middleware or a custom Conversions API build | Website demo and trial leads | fbc and fbp captured at form submit, an email address, and a job that posts stage changes | You own the code, the hashing and the error handling |
If your leads come from Meta lead ads
Meta's Help Center article on connecting Sales Cloud describes sending lead record change events and lead lifecycle stages. It requires Meta leads to already be in Salesforce with the Meta Lead ID or customer information. Meta's developer guide for the Salesforce app maps Lead Status and Opportunity StageName to event names.
Two limits matter for a B2B sales team. Opportunities created directly, rather than from a converted Lead, don't send events. Records created before setup aren't backfilled.
If your demo requests come from your website
Meta ties its conversion leads optimization to instant forms, so website leads go through the standard Conversions API. Capture the fbc and fbp values when the form is submitted and store them on the Lead next to the email. Meta's fbc and fbp guidance says to send those values unhashed. Email must be trimmed, lowercased and SHA-256 hashed, per Meta's customer information parameters.
Then post each stage change as a server event. Meta rejects an event_time more than 7 days old, so a daily job is the slowest cadence that holds up. If you use Zapier, its Salesforce "Updated Field on Record" trigger can watch the Stage field, and Meta documents a Zapier implementation for its CRM integration. If you're still deciding whether a server-side build is worth it at your stage, I walked through that call in is server-side tracking worth it for a growth-stage company.
What does a stage event have to carry?
A stage event needs an event name, the time the stage changed, an action source and customer information to match on. For the Conversion Leads integration, the route built for leads from Meta lead ads, Meta's payload specification asks for these fields:
event_nameset to the CRM stage, such as "Marketing Qualified Lead" or "Sales Opportunity".event_timein Unix seconds for when the stage changed, no more than 7 days before upload.action_sourceset to "system_generated".custom_datawithevent_sourceset to "crm" andlead_event_sourceset to the name of your CRM.user_datawith the 15 to 17 digit Meta Lead ID, or hashed email and phone when you don't have it.
Meta also asks for uploads at least once a day, and it wants every status change sent, not just the latest snapshot of each record. Those values belong to the Conversion Leads integration, so for website leads on the standard Conversions API, check action_source and the other fields against Meta's server event parameters before you reuse them. LinkedIn runs its own version of this pipeline, which I covered in the LinkedIn Conversions API decision guide.
How do you verify the integration is working?
Verify with a test lead before you trust any number in either ad account. Google's setup guide includes a test path, and the checklist below follows it.
- Load your site with ?gclid=test on the URL, submit a lead form, and confirm the Salesforce Lead's GCLID field shows "test".
- Convert that Lead to an Opportunity and confirm the Opportunity's GCLID field also shows "test". Repeat for every form on the site.
- Wait 4 to 6 hours after creating a new conversion action before the first import, or Google may return an error.
- Click Run Now on the integration, then open View data integration and read the Rows imported and Rows with errors columns.
- Allow up to 24 hours for a successful import to show as a conversion. The first import only looks back 14 days, and a row from a non-Google campaign imports without becoming a conversion.
- In Meta Events Manager, send a test stage change and check that the event arrives with the stage name you expect.
- Once a week for the first month, compare each conversion action's count with a Salesforce report on the same stage and date range.
What usually breaks?
Most failures come from a click ID that never reaches the Opportunity. These are the failure points the Google and Meta documentation points to.
- The GCLID drops out in a middle system, such as a scheduler or marketing automation tool that doesn't pass hidden fields.
- Reps create Opportunities directly instead of converting the Lead, so the GCLID never copies over and Meta's app sends nothing.
- Field history tracking isn't on for Stage, so there's no change timestamp to import.
- The deal closes more than 90 days after the click, which puts it outside Google's GCLID import.
- A failed row isn't retried. Google states that "If a Salesforce event fails in import, it won't retry and import the event again automatically," so check the error column after every change.
- Someone renames a stage in Salesforce and the event filter stops matching.
- Meta events arrive more than 7 days after the stage change and get rejected, often because a batch job was paused.
- The fbc or fbp value gets hashed along with the email, which breaks the match on Meta's side.
What does it cost?
The connectors cost little or nothing. Your Salesforce edition and the build hours are the real line items. I read the prices below on each vendor's page on November 11, 2026.
| Item | Price as listed | Source |
|---|---|---|
| Google Ads Data Manager, direct Salesforce connection | No separate fee in Google's setup guide, which notes the Zapier route "may charge a fee" | Google Ads Help |
| Salesforce Pro Suite | $100 per user per month, billed annually, with the Web Services API listed as an additional $25 per user per month | Salesforce Sales Cloud pricing |
| Salesforce Core | $195 per user per month, billed annually | Salesforce Sales Cloud pricing |
| Zapier Professional | From $19.99 per month. "Salesforce is a premium app on Zapier," so it needs a paid plan | Zapier pricing, Zapier Help |
| Salesforce Data 360 | Consumption-based credits, quoted by Salesforce, and the Meta activation needs Ad Audiences entitlements | Salesforce Data 360 pricing |
| Custom Conversions API build | Engineering time and hosting | Meta Conversions API for CRM |
For a B2B SaaS company already on a Salesforce edition with API access, the Google side can run on the direct connection with no separate connector fee. The Meta side is where the budget goes, either into Data 360 or into build hours.
Where should you start?
Start with Google. The direct Data Manager connection has no separate fee, it reads Opportunity stages natively, and it gives you a clean count to check Meta against later. Get the GCLID onto the Opportunity, send one pipeline rung, and run the test lead. Then pick the Meta route that matches where your leads come from. If you'd rather hand off the plumbing, that's the measurement and attribution work I do.
Frequently asked questions
Can one tool send Salesforce opportunity stages to both Google Ads and Meta?
Not through one native setup. Google's direct connection only feeds Google Ads, and Meta's app only feeds Meta. Zapier is the closest shared layer: Google lists it as a third-party route in Data Manager, and Meta documents a Zapier implementation for its CRM integration.
Does the old Salesforce integration in Google Ads still work?
No. Google ended support for the legacy Salesforce integration on May 31, 2025, and in most cases migrated existing conversion actions to Data Manager automatically. If you still see a "Salesforce" tab under Goals, Google's upgrade FAQ walks through the manual migration.
Should I use GCLID import or enhanced conversions for leads?
Use enhanced conversions for leads where you can. Google calls GCLID-based offline conversion import a legacy feature, and enhanced conversions for leads can match on GCLID, email or phone. Map every identifier you have.
How long can my sales cycle be?
Google's GCLID import needs the click-to-conversion cycle to be under 90 days. Meta needs each event's event_time to be within 7 days of when you send it, and it recommends optimizing toward a stage that happens within 28 days of lead generation. If your typical deal takes six months to close, bid on an earlier rung such as opportunity created and keep Closed Won for reporting.
Does Meta's Salesforce app send opportunity stages?
Partly. Meta's developer guide maps Opportunity StageName to event names, but only for Opportunities created by converting a Lead, and the app is built for Meta lead ad leads. Meta's Help Center frames the app around lead stages and says the feature may not be available to every account yet.
{
"url": "https://mattkundodigitalmarketing.com/blog/salesforce-pipeline-stages-google-ads-meta/",
"ai_url": "https://mattkundodigitalmarketing.com/ai/blog/salesforce-pipeline-stages-google-ads-meta/",
"content_type": "sub-page",
"topic_cluster": "none",
"categories": ["Analytics and tracking"],
"published": "Nov 16, 2026",
"canonical": "https://mattkundodigitalmarketing.com/blog/salesforce-pipeline-stages-google-ads-meta/",
"llms_txt": "https://mattkundodigitalmarketing.com/llms.txt"
}