Your ProSites site sends appointment requests. Which ads actually put patients in the chair?
ProSites builds and maintains your dental website, its online booking tools, digital patient forms and, on full-feature plans, AI Chat. Its own blog describes tracking appointment requests as GA4 events and a Google Ads tag on the thank-you page, which counts a request, not a scheduled new patient. We tie each request, call and chat to the ad click and send scheduled new patients from your schedule to Google Ads and Meta, with no ad tags on patient forms.
Free30 minutesNo obligation
ProSites · what breaks
What goes wrong on a ProSites website
- 01
Google Ads shows more new patients than the front desk saw
A thank-you-page tag fires on every appointment request, including existing patients moving a cleaning and requests your team never confirms. Smart bidding then buys more of those clicks.
- 02
An implant consult counts the same as a cleaning request
An implant center or cosmetic practice sending one flat lead to Google Ads makes a whitening question look as good as a request that became a full-arch case, so bids never climb on the searches that pay.
- 03
After-hours chats and missed calls vanish from ad reports
ProSites AI Chat captures contact details and AI Receptionist covers after-hours and overflow calls, sending callers a booking link. A chat that ends without a form submit, or a call the receptionist handles, never loads the thank-you page, so the 9 p.m. patient from your emergency-dentist ad is credited to nothing.
- 04
A Pixel loading next to medical history fields
Your ProSites patient forms are where new patients type in medical history and insurance. A site-wide Meta Pixel fires there too, which is a privacy exposure for a dental practice, and ripping it out blind leaves Meta's bidding with no signal at all.
ProSites · the fix
What changes — ProSites
Bidding learns from scheduled new patients
Google Ads and Meta get a conversion when your team books a new patient, not when someone taps submit.
Procedure value on every conversion
Implant, ortho and emergency visits each carry their own value, so budget drifts toward the searches that bring cases.
Ad tags kept away from patient forms
Browser tags run only on marketing pages; money events go server-side from your schedule through a container on your subdomain.
ProSites · architecture
What ProSites actually lets you hook into
Built from ProSites' own published material. Anything it doesn't document is listed as a check, not assumed.
- 1
ProSites-built website
ProSites designs and maintains the site. Confirm whether you can add a Google Tag Manager container yourself or request it through their team.
- 2
Online booking tools
ProSites says booking integrates with your scheduling system. Check whether booking runs on your domain or in a frame, which decides whether your tags see it.
- 3
Digital patient forms
Part of the core platform. These pages get no ad tags.
- 4
AI Chat and AI Receptionist
Chat captures contact information; the receptionist gathers caller details and sends booking links. Confirm what you can export and whether it keeps the traffic source.
- 5
Thank-you-page conversion tag
ProSites' PPC guide describes a Google Ads tag firing on the page after a form. That's the browser half, and it only counts requests.
- 6
No documented server-side path
We found nothing from ProSites on Meta's Conversions API, offline conversion imports or webhooks, so that leg is built from your schedule.
ProSites · diagnose
Where ProSites tracking breaks, in the order we check
We start with what Google Ads counts today, because if that's a request rather than a patient, every later fix rests on bad data.
- 01
Which actions Google Ads treats as primary
Thank-you-page loads, call clicks and chat starts can all be marked primary at once, so one patient gets counted two or three times.
- 02
Whether the click ID survives the booking step
Book once from a gclid-tagged link and open the request.
- 03
Tags firing on patient-form pages
Load each form with Tag Assistant and Meta Pixel Helper open.
- 04
Chat and receptionist leads with no source
Compare a week of AI Chat and receptionist records with ad-attributed leads.
- 05
Requests against scheduled new patients
Week by week, so the over-count becomes a number instead of a hunch.
ProSites · prove
The QA evidence — ProSites
Run on your live ProSites site from real ad-tagged links, on a phone and a desktop.
Source of truth
Your practice management schedule: new-patient appointments by date and procedure, matched to the appointment requests and online bookings your ProSites site sent
- A test appointment request from a gclid-tagged link, with the ID confirmed on the record.
- One online booking from an fbclid-tagged link, seen as a single Meta event with a shared event ID.
- Patient-form pages loaded with no Google Ads or Meta tags firing.
- Scheduled new patients for a closed month matched one by one against Google Ads and Meta.
- Rechecked after a month of live patients, and again whenever ProSites pushes a design or page change to your site.
ProSites · free audit
What we check in the free audit
- Which actions Google Ads treats as primary
- Whether the click ID survives the booking step
- Tags firing on patient-form pages
- Chat and receptionist leads with no source
- Requests against scheduled new patients
Checked against
Your practice management schedule: new-patient appointments by date and procedure, matched to the appointment requests and online bookings your ProSites site sent
Free30 minutesNo obligation
ProSites · when not to buy
When a ProSites practice doesn't need us
Some practices need a settings change, not a project.
- If you don't run paid ads and new patients come from referrals and the map pack, GA4 counts of calls and requests are enough.
- If your site gets only a few web requests a month, there isn't enough volume for value-based bidding; fix which action is primary and stop.
- If ProSites runs your Google Ads in an account you own and its conversions already match your new-patient list, leave it alone.
- If an old PPC vendor's leftover tag is the whole problem, that's a ticket for ProSites' support team, not a paid project, and we'll say so on the call.
ProSites · what we deliver
The event map on a ProSites site
Appointment request or online booking sent
The lead event, with the gclid or fbclid and the procedure page it came from written into the record.
Call from the site or AI Receptionist
Counted for new patients only, where call details can be exported; recall and billing calls stay out.
AI Chat contact captured
A secondary event for reporting, kept out of bidding until chats prove they book.
New patient scheduled
The primary conversion, sent from your practice management schedule once the front desk confirms.
First visit kept, with procedure value
Sent to Google Ads as an offline conversion and to Meta through the Conversions API.
Excluded on purpose
Patient-form completions, reschedule requests, review clicks and cancellations.
Written guarantee
95%+ tracking accuracy
Measured against Your practice management schedule: new-patient appointments by date and procedure, matched to the appointment requests and online bookings your ProSites site sent. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
ProSites questions, answered
ProSites' blog describes tracking appointment requests as GA4 events plus a Google Ads tag on the thank-you page, added by your webmaster. That measures requests, not patients, so what's actually firing is the first thing we check.
ProSites' own articles recommend Tag Manager for conversion tracking. Since their team maintains the site, we confirm whether you add the container or they do, and keep it off patient-form pages.
It can be on pages where patients enter health or insurance details. We keep pixels to marketing pages and decide with you and your compliance advisor what patient data, if any, leaves the practice.
Not on their own, from what ProSites documents. We log them as secondary events and only let bidding use them once they're shown to book patients.
You may not. But when one vendor builds the site, runs the ads and reports results, an outside check against your schedule tells you whether the reported new patients are real.
Conversion history stays in whichever Google Ads and Meta accounts hold it, so make sure they're in your practice's name. The server container we build sits on your subdomain and moves with you.
More on ProSites
- 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 ProSites, and what their bookings feed
- PerkvilleYour ads are taking credit for Perkville referrals
- ShowitYour Showit inbox is full of inquiries. Google Ads says you got none.
- Dealer SpikeDealer Spike sends the leads. Your ads can't tell which ones bought a unit.
- R.O. WriterAds ring your phone. R.O. Writer closes the RO. Google Ads never learns which calls paid.
- LawLyticsYour LawLytics site gets the inquiries. Google Ads can't tell which ones signed.
- Ours PrivacyOurs Privacy took the pixels off your site. Now your ads can't tell which clicks became patients.
- OfficiteYour Officite portal shows visitors. Which ads actually fill your schedule?
- AutoLeapAutoLeap conversion tracking: your calendar is full, but which ads filled it?
Free · 30 min
See which ads bring new patients to your ProSites site
WhatsAppFree30 minutesNo obligation
