FieldPulse is full of booked jobs. Your ads can't see any of them.
Your Booking Portal sits on your site as an iframe, so Google Ads and Meta lose the homeowner the moment they pick a service. Calls answered by Operator AI and chats booked by Chat AI go straight onto your schedule without your website knowing. We tie FieldPulse's jobs and paid invoices back to the ad click, so Google and Meta learn which campaigns bring work that gets paid.
Free30 minutesNo obligation
FieldPulse · what breaks
What goes wrong when FieldPulse runs your bookings
- 01
"Google says zero conversions, but the schedule is full"
The Booking Portal is an iframe pasted from FieldPulse, so the form runs on FieldPulse's page inside yours. GA4 and the Meta Pixel see the page load, then nothing, and Smart Bidding throttles the campaigns that are booking jobs.
- 02
"The Google Ads phone line says 'Google' and that's it"
Engage can stamp a lead source on every call to a given number. But one static number per channel carries no click ID, so you can't tell which keyword rang the phone, and Google Ads never hears that the call became a water heater install.
- 03
"The AI books jobs our ads never get credit for"
Operator AI picks up the calls Engage forwards to it, usually the ones your office would miss, and Chat AI books from a widget on your site. Both write a tagged customer and job straight into FieldPulse. Your ads paid for that work, and no conversion fires anywhere.
- 04
"We're counting requests that never turn into work"
With auto-scheduling off, a booking is just a row in the Requests tab, and FieldPulse's confirmation email says it's under review. Counting every submit as a sale trains bidding on tire-kickers and out-of-area requests.
FieldPulse · the fix
What changes — FieldPulse
Paid jobs credited to the ad that started them
Invoices that reach Paid in FieldPulse go to Google Ads and Meta at the invoice total, matched to the original click.
Every booking path counted once
Portal, chat and phone bookings each report through one server-side owner, with a shared event ID so nothing doubles.
Bidding stops learning from junk
Marketplace leads, existing customers and unreviewed requests stay out of the primary conversion your campaigns optimize toward.
FieldPulse · architecture
What FieldPulse actually lets you hook into
FieldPulse's help center documents no Google Ads, GA4, Tag Manager or Meta Pixel setting. These are the hooks it does document.
- 1
Booking Portal iframe and link
Embedded with iframe code from Company Settings, or sent as a link. It supports custom fields; we confirm whether one can be prefilled with a click ID before relying on it.
- 2
Developer API
Key issued by FieldPulse Support. Documented uses include sending website lead data into FieldPulse and pushing custom-field data, which is where click IDs live.
- 3
Outbound webhooks
Job, estimate and invoice events, including created, status changes, reschedules and invoices marked Paid with the total. FieldPulse Support sets them up.
- 4
Zapier
Six triggers and seven actions, including New Customer, pipeline and job workflow statuses, and Create Lead. Good for alerts; we don't use it as the conversion feed.
- 5
Lead sources and tags
Engage lines can auto-assign a lead source, Angi and Thumbtack set their own, and the AI add-ons tag their records. We use these to label and exclude, not to attribute.
FieldPulse · diagnose
Where FieldPulse tracking breaks, in diagnostic order
Start at the iframe, because that's where most FieldPulse accounts lose the ad click before anything else can go wrong.
- 01
Submit a test booking from an ad-tagged URL
Then open the customer record and check whether any click ID or UTM arrived.
- 02
Check the Automatically Schedule setting
On means every submit becomes a scheduled job; off means requests wait for review. Your conversion point depends on which.
- 03
Trace the Engage numbers on your site and ads
Which lines carry which lead source, and whether any call reaches an ad platform.
- 04
Count Operator AI and Chat AI jobs
Filter by their generated tags and compare with what your ads reported that week.
- 05
Find marketplace and repeat-customer leakage
Angi, Thumbtack and email-matched existing customers should never count as new ad conversions.
FieldPulse · prove
The QA evidence — FieldPulse
Run on your live website and your real FieldPulse account. Operator AI's Test Mode creates no records, so the phone path is proven with a real forwarded call.
Source of truth
FieldPulse invoices marked Paid, with invoice total, customer lead source and the job created from the original request
- One Booking Portal request from an ad-tagged URL, with the click ID confirmed on the FieldPulse customer.
- One Chat AI booking and one forwarded Engage call traced to their tagged jobs.
- Exactly one conversion per paid invoice in Google Ads and Meta, with a shared event ID.
- Conversion value equal to the FieldPulse invoice total.
- An Angi or Thumbtack lead confirmed absent from ad conversions.
- Paid invoices reconciled one by one across a closed month.
- Rechecked 30 days later and after any change to the portal or Engage routing.
FieldPulse · free audit
What we check in the free audit
- Submit a test booking from an ad-tagged URL
- Check the Automatically Schedule setting
- Trace the Engage numbers on your site and ads
- Count Operator AI and Chat AI jobs
- Find marketplace and repeat-customer leakage
Checked against
FieldPulse invoices marked Paid, with invoice total, customer lead source and the job created from the original request
Free30 minutesNo obligation
FieldPulse · when not to buy
When you don't need this on FieldPulse
Plenty of FieldPulse shops are better off spending this money on trucks.
- If you don't run Google or Meta ads and your work comes from referrals, Angi and Thumbtack, FieldPulse's lead source field already tells you where jobs come from.
- If you run one small campaign and a dedicated Engage line per channel tells you enough, keep it simple.
- If most of your schedule is maintenance-agreement visits for existing customers, ad attribution won't change many decisions.
- If the only problem is a portal missing from your landing page, you can paste the iframe yourself, and we'll say so.
FieldPulse · what we deliver
The event map on FieldPulse
Ad lead captured
gclid, gbraid, fbclid and UTMs saved on your site and written to a custom field on the FieldPulse customer through the API.
Booking request submitted
Portal, Chat AI or Operator AI, labeled by path. Tracked as a lead, never as revenue.
Job scheduled
From FieldPulse's Job Created webhook, so only requests your office accepts count as booked.
Estimate approved
From the Estimate Custom Status Update webhook, mapped to the status your office uses for approved, for replacement and install work. We confirm the payload carries the estimate total before using it as value.
Invoice paid
The primary conversion, valued from the invoice total and sent server-side to Google Ads and Meta.
Excluded
Angi and Thumbtack leads, existing customers FieldPulse matched by email, reschedules that fire Job Start Time Update again, and declined out-of-area requests.
Written guarantee
95%+ tracking accuracy
Measured against FieldPulse invoices marked Paid, with invoice total, customer lead source and the job created from the original request. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
FieldPulse questions, answered
Not that its help center documents. There is no Google Ads, GA4, Tag Manager or Pixel setting, so tracking comes from your website, the FieldPulse API and webhooks that FieldPulse Support turns on.
No. The portal is embedded as an iframe, so the steps happen on FieldPulse's page and your site's tags only see the page that holds it. Bookings have to be confirmed from FieldPulse's own records instead.
They show which channel a call came from. They carry no click ID, so Google Ads can't tie the call, or the job it became, to a campaign or keyword.
Both tag their customer and job records as AI generated. We pick those jobs up from FieldPulse and, when the customer came from an ad, send the paid invoice back with the original click.
As a secondary signal, yes. The primary conversion should be a scheduled job or, better, a paid invoice, because a request can still be declined or never answered.
They can if every new FieldPulse customer fires a conversion. FieldPulse sets their lead source automatically, which makes them easy to exclude.
More on FieldPulse
- 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 FieldPulse, and what their bookings feed
- BuildOpsYour BuildOps pipeline knows which ads won contracts. Google and Meta don't.
- SuccesswareSuccessware says your jobs came from "Google." Google Ads never learns which ones paid.
- AspireAspire conversion tracking: your ads never hear which contracts you won
- OnfleetOnfleet conversion tracking: your ads take credit for deliveries that never arrived
- LMNLMN conversion tracking: stop guessing which ads turn into Won estimates
- MarkateMarkate is full of booked jobs. Your ads can't see which clicks booked them.
- KickservKickserv conversion tracking for ads that fill the inbox but not the schedule
- FieldRoutesYour FieldRoutes widget sells pest plans online. Google Ads can't tell which ads sold them.
Free · 30 min
Find out what your ads really booked in FieldPulse
WhatsAppFree30 minutesNo obligation
