tab32 shows new patients on the dashboard. Google Ads and Meta can't say which ads sent them.
Your tab32 New Patients number climbs, but the ad accounts report a handful of form fills, so nobody can say whether the implant or emergency-dentist campaign pays. tab32 documents no Google tag, Meta Pixel or ad-platform connection, so the click and the appointment never meet. We link each new-patient appointment back to its ad click, keep AutoRemind recall out, and send kept first visits to Google and Meta as the conversion they bid on.
Free30 minutesNo obligation
tab32 · what breaks
What goes wrong with tab32 and your ads
- 01
"tab32 shows a busy month of new patients. Google Ads shows a handful."
tab32 documents no way to send an appointment to an ad platform, so bidding learns from Book-button clicks and short calls instead of patients who sat in the chair. The campaigns filling your schedule look no better than the ones wasting budget.
- 02
Recall and reactivation patients counted as ad wins
AutoRemind recall and reactivation campaigns put existing patients back on your tab32 schedule. Lumped in with paid bookings, they hand your Meta campaign credit for people you already had.
- 03
Online bookings you have to confirm the next morning
tab32 describes patients grabbing after-hours slots the team confirms the next day. An ad platform counting the request treats a never-confirmed booking like a kept consult, and you pay for both.
- 04
A DSO dashboard that can't split results by office
Summit puts every office on one patient record and one dashboard. Without the location on each conversion, you can't see that one practice books periodontal consults from search while another books denture patients from Meta.
tab32 · the fix
What changes — tab32
Each paid new patient reaches Google and Meta once
The click ID is saved before the patient leaves your site, matched to the new tab32 appointment, and sent server-side with one shared event ID.
Campaigns graded on kept first visits
A confirmed, completed first appointment in tab32 becomes the conversion bidding learns from; unconfirmed requests and no-shows stop counting.
Budget follows the offices and services that book
Location and a broad value band ride on every conversion, so an implant consult outweighs a cleaning, with no clinical detail sent.
tab32 · architecture
What tab32 actually lets you hook into
tab32 publishes no developer documentation for ad tracking, so this list comes from its own product and pricing pages. Anything not documented is a check, not a promise.
- 1
Online booking (HelloPatient)
tab32 describes native booking against live provider availability, while its pricing page lists online booking as a coming add-on. We confirm which you have and whose domain it runs on.
- 2
Patient portal
Patients book, reschedule and do paperwork without an app or account. Mostly existing patients, so separated from acquisition.
- 3
AutoRemind and DashCare
Partner tools for reminders, recall, texting and intake forms that sync into the tab32 record. Good for tagging returning patients, not a route to ad platforms.
- 4
Live reports and the New Patients count
tab32 runs operational reports straight off live practice data and tracks new-patient volume. On Alpine we confirm which appointment reports your team can export, since tab32 documents scheduled exports only for BI connections.
- 5
Open API, MCP server and BigQuery warehouse (Summit)
Listed as Summit options. The BigQuery warehouse refreshes nightly, with real-time streaming sold as a premium add-on, so a nightly pull of kept appointments is the realistic default.
- 6
No documented Google Ads, GA4, GTM or Meta connection
Nothing in tab32 sends conversions to ad platforms, so that part is ours to build.
tab32 · diagnose
Where tab32 tracking breaks, in diagnostic order
Start at the website hand-off, because that's where most practices lose the ad click before tab32 ever sees the patient.
- 01
Book a test appointment from an ad-tagged URL
Then open it in tab32 and look for any trace of the source.
- 02
Count what fires on the booking path
Does any tag run once the patient leaves your site?
- 03
Check how calls are tracked
tab32 documents no call tracking, so a phone booking only carries the ad click if a tracking number on your site does.
- 04
Separate new from returning patients
AutoRemind recall and portal rebookings flagged before anything is sent.
- 05
Compare kept first visits with reported conversions
Per location, over a closed month.
tab32 · prove
The QA evidence — tab32
Run on a live booking through your real website and booking page, then checked in tab32, not in a preview.
Source of truth
tab32 appointment records: new-patient appointments by creation date, confirmation status, location and whether the first visit was kept
- One booking from an ad-tagged URL, with the click ID tied to the new tab32 appointment.
- One call from an ad, matched to the appointment it produced.
- Exactly one conversion per kept first visit in Google Ads and Meta, with a shared event ID.
- Unconfirmed requests, cancellations and no-shows confirmed absent.
- AutoRemind recall and portal rebookings confirmed absent from acquisition conversions.
- Reconciled record by record over a closed window, then again 30 days later.
tab32 · free audit
What we check in the free audit
- Book a test appointment from an ad-tagged URL
- Count what fires on the booking path
- Check how calls are tracked
- Separate new from returning patients
- Compare kept first visits with reported conversions
Checked against
tab32 appointment records: new-patient appointments by creation date, confirmation status, location and whether the first visit was kept
Free30 minutesNo obligation
tab32 · when not to buy
When you don't need this on tab32
Some tab32 practices are better off with a quick settings check or nothing at all.
- If you don't run paid ads and new patients come from referrals and your Google Business Profile, tracking tab32 bookings back to ads has nothing to measure.
- If almost every appointment is recall from AutoRemind, retention reporting in tab32 tells you more than ad attribution would.
- If you spend a few hundred dollars a month on one campaign and the front desk asks every new tab32 patient how they found you, that may be enough for now.
- If your only problem is a broken call button or a missing tag on the link to your tab32 booking page, that's a small fix and we'll tell you how to do it yourself.
tab32 · what we deliver
The event map on tab32
Book Online or Call clicked
The hand-off from your website, with the Google and Meta click IDs stored in a first-party cookie. A signal, never the bidding goal.
Appointment requested
Captured where your booking page allows, or matched later from tab32 by contact details and request time.
Appointment confirmed in tab32
Counted only after the front desk confirms it, so every reported booking is a real slot on the schedule.
First visit kept
The primary conversion, sent to Google Ads and Meta from the appointment record and valued by broad visit type.
Cancelled, broken or no-show
Never sent, and kept out of any audience built to find new patients.
AutoRemind recall, reactivation and portal rebookings
Logged for retention reporting and excluded from every acquisition conversion.
Written guarantee
95%+ tracking accuracy
Measured against tab32 appointment records: new-patient appointments by creation date, confirmation status, location and whether the first visit was kept. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
tab32 questions, answered
Not that tab32 documents. Its product and pricing pages describe no Google tag, Meta Pixel or offline conversion connection, so appointments have to be matched to ad clicks outside tab32 and sent from a server container.
Yes, through offline conversion import or enhanced conversions for leads, which match the click ID or hashed contact details captured at booking to the kept appointment. Google is moving these uploads to its Data Manager API from June 15, 2026.
We send only what matching needs, hashed contact details and a broad value, never treatment, diagnosis or chart data. Clinical information stays in tab32.
Yes. Each conversion carries the office from the appointment, so you can see which locations book from search and which from Meta. Summit's optional open API or BigQuery warehouse can feed it.
Only if they're mixed in. We flag recall, reactivation and portal rebookings as returning patients and keep them out of every acquisition conversion.
More on tab32
- 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 tab32, and what their bookings feed
- WebPTYour ads stop at the Reach form. See which ones fill your WebPT schedule with evaluations.
- NextGen HealthcareGoogle Ads can't see the new patients booking through NextGen Self-Scheduling
- PhreesiaPhreesia books the new patient, and Google Ads never finds out
- NextechYour ads report leads. Nextech shows who actually booked a consult.
- AdvancedMDYour ads go blind at AdvancedMD's patient portal. See which ones book new patients.
- ClerriClerri conversion tracking: your plan is gaining members, so why do your ads show none?
- Blueprint OMSYour Blueprint OMS schedule fills with online bookings, and Google Ads can't see one
- Open DentalOpen Dental Web Sched books new patients your ads never see
Free · 30 min
Find out which ads are filling your tab32 schedule
Free30 minutesNo obligation
