Your Zap says "Success," so why can't Google Ads see the jobs you closed?
Plenty of junk removal, moving and fence companies wire their CRM to Google Ads and Meta with Zapier, then find the conversion column empty or quietly doubled. A Zap can only pass along what your CRM stored, and most CRMs never saved the ad click ID. Fixed means every won job leaves Zapier with a click ID, a dollar value and an event ID Meta can deduplicate, and a failed run gets noticed that week.
Free30 minutesNo obligation
Zapier · what breaks
What goes wrong when Zapier carries your conversions
- 01
The Zap runs fine, and Google still records nothing
Zapier's Send Offline Conversion step needs an identifier Google can match to a click. If your form never wrote the GCLID into the CRM, the Zap has nothing reliable to send, and bidding never learns which ads brought in your best jobs.
- 02
Meta counts every lead twice
A Pixel on your thank-you page fires Lead, then a Zap sends Lead again through Zapier's Facebook Conversions app. Meta only merges the pair when the event name and event ID match within 48 hours. Without a shared ID, Ads Manager shows twice the leads, cost per lead looks half what it is, and delivery optimizes toward a false signal.
- 03
Estimates get reported as sales
Most Zaps start on "new contact" or "new deal" because that's the easiest trigger to pick. A painting estimate that never closes then reaches Google as a conversion, so bidding chases quote-shoppers, while the job you won may never fire, because Zapier only triggers on updated records when that trigger supports updates.
- 04
Failed runs nobody reads
Held and stopped runs sit in Zap history, which Zapier only guarantees for 60 days. The Free plan has no autoreplay and polls every 15 minutes, so a broken step can starve your campaigns for weeks.
Zapier · the fix
What changes — Zapier
Won jobs land in Google Ads against the click that paid for them
Each conversion carries the GCLID saved on the lead, the exact conversion action name Google Ads expects, and the real job value from your CRM.
One Meta lead per real lead
The browser Pixel and the Zap share an event ID, so Meta keeps one and drops the copy.
A failed Zap gets caught the same week
Errors and held runs are routed to a person, and a monthly reconciliation compares Zap history with your closed jobs.
Zapier · architecture
What Zapier actually lets you do
Zapier never touches your website. It moves records between apps, so everything here starts with what your CRM or form already saved.
- 1
Google Ads: Send Offline Conversion
Takes a conversion name, a time and an identifier source, with optional value and currency. Zapier also lists Customer Match list actions that run on Google's Data Manager API, which Zapier marks as being beta tested by Google.
- 2
Facebook Conversions: four event actions
Send Lead Event, Send Purchase Event, Send Funnel Event and Send Other Event post to Meta's Conversions API. We confirm in the Zap editor which fields, such as event ID and click ID, each one exposes.
- 3
Google Analytics 4 measurement events
Zapier's GA4 app lists a Send Measurement Events for an Application action. We confirm in the Zap editor whether it fits your web property before relying on it for won jobs.
- 4
Webhooks by Zapier
Catch Hook triggers when your CRM posts to a Zapier URL, so the Zap starts as the event happens instead of waiting for polling. Zapier lists webhooks on paid plans only.
- 5
Polling, filters and replay depend on your plan
Polling runs every 15 minutes on Free, 2 on Professional and 1 on Team. Free Zaps are two-step, with no Filters, Paths or autoreplay.
Zapier · diagnose
Where Zapier conversion tracking breaks, in diagnostic order
We start at the CRM record, because a Zap can't send a click ID that was never saved.
- 01
Open three recent ad leads in the CRM
Is a GCLID or fbclid on each one? If not, the fix is at the form, not in Zapier.
- 02
Read Zap history for errors, held and stopped runs
Inside Zapier's 60-day window, by step.
- 03
Check what the trigger fires on
New record, stage change or won deal, and whether it catches updates at all.
- 04
Count Meta events on one test lead
Pixel plus Zap, and whether they share an event ID.
- 05
Match the Google conversion action
The name in the Zap must match Google Ads exactly, and Google advises waiting 4 to 6 hours after creating a new action before uploading.
- 06
Check value and currency
Blank or fixed values make every job look the same to bidding.
Zapier · prove
The QA evidence — Zapier
Run on a real test lead from an ad-tagged URL, carried to won in your CRM. Zapier's sample data may not match live runs.
Source of truth
Your CRM's won and paid jobs, matched one for one to the successful runs in Zap history
- Test lead from an ad-tagged link, with the GCLID visible on the CRM record.
- Exactly one Meta Lead event in Events Manager, with Pixel and server sharing the event ID.
- The offline conversion visible in Google Ads after Google's 24 to 48 hours of processing.
- A spam lead and an existing customer stopped by the Filter step.
- Closed jobs reconciled against Zap history and both ad platforms for a full month.
- Rerun after 30 days, and again whenever someone renames or reorders the CRM's pipeline stages, since that silently changes what the Zap trigger sees.
Zapier · free audit
What we check in the free audit
- Open three recent ad leads in the CRM
- Read Zap history for errors, held and stopped runs
- Check what the trigger fires on
- Count Meta events on one test lead
- Match the Google conversion action
- Check value and currency
Checked against
Your CRM's won and paid jobs, matched one for one to the successful runs in Zap history
Free30 minutesNo obligation
Zapier · when not to buy
When you don't need us for Zapier
Sometimes the honest answer is that the Zap isn't the problem, or isn't needed.
- If your CRM already syncs conversions to Google Ads and Meta natively and the numbers match your jobs, adding a Zap would only create duplicates.
- If a phone repair shop takes payment at the counter and keeps no CRM, there's no record for a Zap to read; a call or store-visit signal may tell bidding enough.
- If a swim school or dance studio closes a few enrollments a month from ads, a monthly manual upload to Google Ads can be enough.
- If the Zap's only fault is a misspelled conversion action name, you can correct it in five minutes, and we'll tell you so on the call.
Zapier · what we deliver
The event map we run through Zapier
Click ID stored on the lead
GCLID, fbclid and UTMs written from hidden form fields into the CRM record the Zap reads.
Qualified lead
Fires on the CRM stage change, not on record creation, and goes to Meta as a Lead event and to Google as an offline conversion.
Estimate or job booked
Sent as a funnel event so Meta sees progress without treating it as revenue.
Job won or paid
The money conversion, with value and currency from the invoice or deal amount.
Spam, tests and existing customers
Stopped by a Filter step before any ad platform hears about them.
Cancellations
Zapier's Google Ads app lists no adjustment action, so cancelled jobs are held back before sending and anything already sent is corrected outside Zapier.
Written guarantee
95%+ tracking accuracy
Measured against Your CRM's won and paid jobs, matched one for one to the successful runs in Zap history. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Zapier questions, answered
Yes. Zapier's Google Ads app has a Send Offline Conversion action that takes a conversion name, a time and an identifier, plus optional value and currency. It only matches to your ads when the CRM record holds a GCLID or another identifier Google accepts, which we confirm in the Zap editor.
Google says imported conversions can take 24 to 48 hours to show in reports, so wait first. If they still don't appear, the usual causes are a conversion action name that doesn't match exactly, a brand-new action uploaded to too soon, or no click ID on the record.
No. The Zap sends what happens in your CRM, like qualified leads and won jobs, while the Pixel sees what happens on your site. When both send the same event, they need a matching event ID or Meta counts it twice.
Rarely. Free Zaps are limited to two steps with no Filters, Paths, webhooks or autoreplay, so spam leads go straight to Google and Meta and a failed send isn't retried automatically.
Usually both. Zapier suits CRM events that happen days after the click, like a won fence job; a first-party server container handles form fills and call clicks on your site as they happen.
More on Zapier
- Enhanced ConversionsEnhanced Conversions enrich the conversions that already fire. First we make sur…
- Meta CAPIA one-click CAPI integration sends thin events. That's why your Event Match Qual…
- Cross-Domain TrackingYour checkout provider is the best performing traffic source in your GA4 account…
RELATED GUIDES
Booking tools beside Zapier, and what their bookings feed
- boberdooboberdoo conversion tracking that counts sold leads, not form fills
- SteerSteer conversion tracking: which ads actually brought cars into your bays?
- SalesRabbitYour rep drops a sale pin in SalesRabbit. Your ads never hear about it.
- LeadPerfectionYour ads say leads. LeadPerfection says who sat and who signed. We connect the two.
- Followup CRMYour contracts close in Followup CRM. Your ads never find out.
- Builder PrimeYour rep marks the job Sold in Builder Prime. Google Ads never finds out.
- improveit 360improveit 360 conversion tracking: the window job sells at the kitchen table, and your ads never hear about it
- LeadSquaredLeadSquared for healthcare: show Google and Meta which ads become booked consults
Free · 30 min
Find out what your Zaps are really telling Google and Meta
WhatsAppFree30 minutesNo obligation
