OrbisX conversion tracking for shops that can't tell which ads fill the bays
You turned on OrbisX's Meta Conversions API, Ads Manager filled up with Schedule and Purchase events, and you still can't say which ceramic coating or tint campaign paid for itself. OrbisX fires a Meta Lead event whether the lead came from your booking form, a phone-in your staff typed up, Zapier or the API, and it lists no Google Ads connection at all. We separate ad-driven bookings and send paid OrbisX invoices back to Google and Meta with the click attached.
Free30 minutesNo obligation
OrbisX · what breaks
What goes wrong with OrbisX and your ads
- 01
"Meta says it booked jobs my ads never touched"
OrbisX documents that its Lead event fires for leads from your booking form, manual staff entry, Zapier and the API. Dealer cars, fleet work and phone-ins your team keys in can land in Meta as conversions, so your campaigns take credit for jobs you'd have booked anyway and Meta bids up the wrong audience.
- 02
"Google Ads shows clicks but no booked tints"
OrbisX lists no Google Ads connection, and the booking form runs in a frame served from orbisx.ca. The Google tag on your page never sees the appointment, so Smart Bidding has no paid tint or coating jobs to learn from and keeps buying clicks that don't book.
- 03
"The Pixel and OrbisX both report the same booking"
A Pixel in your site header and the OrbisX CAPI connection can each send the same booking. OrbisX doesn't describe a shared event ID, so Meta may count it twice and flatter your cost per booking.
- 04
"A quick wash and a full-front PPF job count the same"
If you optimize on Schedule instead of the paid invoice, a maintenance wash teaches Meta as much as a full-front PPF install. Your budget drifts toward cheap, easy bookings.
OrbisX · the fix
What changes after we fix it — OrbisX
Only ad-driven OrbisX jobs reach the ad platforms
Bookings from Reserve with Google, staff entry and fleet accounts are kept out of acquisition conversions, so bidding learns from the customers your ads actually bought.
Google Ads finally sees paid work
Paid OrbisX invoices go back as offline conversions matched to the original click, with the real invoice value on each one.
One Meta conversion per job
The browser Pixel and OrbisX's server events are reconciled so each booking and each payment counts once in Events Manager.
OrbisX · architecture
What OrbisX actually lets you hook into
Everything below comes from OrbisX's own pages and its Zapier listing. Where a detail isn't documented, it's written as something we confirm on your account.
- 1
Embedded booking form (iframe)
OrbisX's own demo embeds the form as an iframe loaded from orbisx.ca/app/booknow. Your site's tags can't see inside it without help.
- 2
Google Analytics integration on the booking form
Listed as a booking form feature. Which events it sends, and whether it works alongside your GA4 property, is something we test on a live booking.
- 3
Meta Conversions API (native)
Pixel ID and Access Token under Admin Settings, Integrations. Sends Lead, a client event when a lead converts, InitiateCheckout (estimate), Schedule (appointment), Purchase (paid invoice, with value and currency) and CompleteRegistration, with hashed email, phone and name. OrbisX doesn't mention an event ID or click ID.
- 4
Zapier triggers
New Leads Hook, New Booking Request Received, New Events Hook, Completed Event Hook, New Invoice Hook, New Payment Hook and tag changes, among others. Our route to Google Ads and filtered Meta events.
- 5
Reserve with Google
Lets people book from Google Search and Maps, and OrbisX syncs those bookings to your calendar. They're real customers, but they aren't ad clicks.
- 6
No Google Ads connection
OrbisX doesn't list Google Ads or offline conversion import. Paid jobs have to be sent from the hooks above.
OrbisX · diagnose
Where OrbisX tracking breaks, in the order we check
On OrbisX the usual fault is too many Meta conversions, not too few, so we start with what CAPI is sending.
- 01
Count Meta events for one test booking
Pixel on the page plus OrbisX CAPI. Two Schedule events for one booking means no shared event ID.
- 02
Check which OrbisX leads become Meta Leads
Add a lead by hand in OrbisX and see whether it appears in Events Manager.
- 03
Book from an ad-tagged URL and open the OrbisX record
Look for the GCLID or fbclid anywhere on the lead, client or appointment.
- 04
Compare paid invoices with Purchase events
Per job, including deposits, split payments and gift cards.
- 05
Separate Reserve with Google bookings
Confirm they can be told apart from website bookings before anything reports them as ad results.
OrbisX · prove
The QA evidence you get — OrbisX
Tested on a real booking through the OrbisX form embedded on your live website, then reconciled against your invoices.
Source of truth
OrbisX invoices and payments: paid jobs by date, with service, amount and client, plus the OrbisX Meta CAPI delivery log
- A booking from an ad-tagged URL with the click ID confirmed on the OrbisX lead or appointment.
- Exactly one Meta Schedule and one Purchase per job in Events Manager.
- A staff-entered lead confirmed absent from Meta and Google Ads.
- A paid OrbisX invoice showing in Google Ads as an offline conversion with the right value.
- A deposit and final balance reported as one job, not two sales.
- Paid invoices matched to conversions job by job across a closed month.
- The same check repeated 30 days later and after any change to the booking form or CAPI settings.
OrbisX · free audit
What we check in the free audit
- Count Meta events for one test booking
- Check which OrbisX leads become Meta Leads
- Book from an ad-tagged URL and open the OrbisX record
- Compare paid invoices with Purchase events
- Separate Reserve with Google bookings
Checked against
OrbisX invoices and payments: paid jobs by date, with service, amount and client, plus the OrbisX Meta CAPI delivery log
Free30 minutesNo obligation
OrbisX · when not to buy
When you don't need us for OrbisX
Some shops are better off with a short settings review than a rebuild.
- If you only run Meta, nearly every OrbisX lead comes from your website, and the CAPI delivery log already matches your invoices, leave it alone.
- If most of your work is dealer, fleet or insurance windshield jobs, ad attribution won't tell you much. Your account relationships matter more.
- If you're not running paid ads yet and rely on Reserve with Google and referrals, OrbisX's own reports are enough for now.
- If the only problem is a duplicate Pixel on your site, removing it is a quick job and we'll tell you how to do it yourself.
OrbisX · what we deliver
The event map on OrbisX
Booking form loaded
Fired on your own page when the OrbisX iframe appears, showing which ads send people who start a booking.
Lead or booking request
A new OrbisX lead or a request awaiting your approval, carrying the click ID and source. Staff-entered and Zapier-imported leads are excluded.
Estimate sent
The quote stage for coating, PPF and wrap jobs, with the estimate amount. A secondary signal, not a bidding target.
Appointment confirmed
Counted once the booking is on the calendar. Repeat clients and fleet accounts are tagged so they don't inflate new-customer numbers.
Deposit or invoice paid
The primary conversion, valued from the OrbisX invoice. A booking deposit and the final balance are linked so one job isn't counted as two sales.
Gift card sale
Tracked as its own purchase and kept apart from service revenue, so a holiday gift card rush doesn't look like a great tint campaign.
Written guarantee
95%+ tracking accuracy
Measured against OrbisX invoices and payments: paid jobs by date, with service, amount and client, plus the OrbisX Meta CAPI delivery log. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
OrbisX questions, answered
It gets OrbisX data into Meta, which beats a Pixel alone. But it sends events for leads from every source, so Meta can't tell an ad customer from a walk-in or fleet job until that's filtered and tied to the click.
Not natively. OrbisX doesn't list a Google Ads integration, so paid invoices have to be sent through its Zapier hooks or a server container as offline conversions.
The booking form loads in an iframe from orbisx.ca, so the Google tag on your site never sees the appointment being made. The click ID has to be carried into OrbisX and the booking sent back afterward.
Purchase, once enough paid invoices are flowing, because it carries the real job value. Schedule is fine as an early signal for a new account, but it treats a quick wash and a full ceramic coating the same.
Usually not. Someone booking through Reserve with Google on Search or Maps came in through your listing, not an ad click, so we keep those out of Google Ads and Meta conversions and report them separately.
Edits to questions or services can change what gets stored on the lead, so we recheck after any form change. The server-side half reads your invoices, not the form layout.
More on OrbisX
- 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 OrbisX, and what their bookings feed
- BonzoBonzo is full of mortgage leads. Which ads actually funded loans?
- BuildiumGoogle Ads keeps counting leads. Buildium shows almost no applications.
- LineLeaderLineLeader shows who enrolled, but not which ad sent them
- Little Green LightLittle Green Light shows the gifts. Your ads can't see which campaign raised them.
- PlaygroundPlayground conversion tracking that credits ads with enrollments
- Deltek VantagepointVantagepoint shows which inquiries became awarded projects. Google Ads still bids on form fills.
- IgnitionIgnition shows who signed, but not which ad brought them in
- Builder PrimeYour rep marks the job Sold in Builder Prime. Google Ads never finds out.
Free · 30 min
Find out which ads are really filling your OrbisX calendar
Free30 minutesNo obligation
