Trackers · advertising or behavioural
Meta Pixel on a practice website
The Meta Pixel is an advertising script. It tells Meta which pages a visitor opened so that Meta can measure ads, build audiences of people who visited the site, and show them ads on Facebook and Instagram.
It is one of the six scripts our scanner finds most often on small practice sites. Of 362 dental and physical therapy sites scanned as of 2026-10-08, 66 (18%) load it, and 23 load it on a page where a visitor books an appointment, gets in touch or fills in a form. Those 23 are the ones worth looking at first.
What it reports, and to whom
- A PageView event with the full page address on every page it is installed on, including booking, contact and new-patient pages.
- A browser identifier (the _fbp cookie), and, when the visitor is logged in to Facebook or Instagram in the same browser, the link to that account is made on Meta's side.
- Whatever extra events the setup adds: a Lead, Schedule or Contact event on a form, and with Advanced Matching switched on, hashed values of fields such as email and phone number.
A third-party tracker is a script another company puts on a page, which reports back to that company. The page address is the part that matters on a practice site: an address like /book-an-appointment/ or/new-patient-forms/ says what the visit was about before anyone types a word.
How it usually gets there
- The PixelYourSite plugin on WordPress, or Meta's own 'Meta pixel for WordPress' plugin.
- A Google Tag Manager container, placed there by an agency that ran Facebook ads.
- Wix and Squarespace both have a settings field that asks for a pixel ID.
- Pasted into the theme header from Meta's Events Manager setup page.
In our scans the script is rarely something the practice chose. It came with a plugin, an agency or a template, and nobody has looked at it since.
How to check your own site in a minute
Open the booking or contact page, press Ctrl+U(Cmd+Option+U on a Mac) to view the page source, then search the page for any of these:
connect.facebook.netfbevents.jsfbq(facebook.com/tr?
A match means the script is on that page. No match on the page source is not the end of it: a tag inside a Google Tag Manager container does not appear in the source at all. The free scan reads the container as well and lists every page the script loads on.
How to remove it
- WordPress
- Deactivate PixelYourSite or Meta's plugin, or delete the snippet from the theme header or snippet plugin. Clear the page cache afterwards.
- Google Tag Manager
- Pause the Meta Pixel tag and any Custom HTML tag that contains fbevents.js, then publish.
- Wix, Squarespace
- Clear the pixel ID from the marketing integrations settings.
- Afterwards
- Check Events Manager in the Meta account: a pixel that still shows recent activity is still loading from somewhere, usually a second copy.
After any change, open the booking page again in a private window and repeat the search above, then do the same on the home page. Caching plugins and content delivery networks keep serving the old page for a while; clear them if the script is still there.
What we are not saying
This page says what the script does and how to take it off. It does not say what having it means for a particular practice's obligations. TagQuiet performs technical assessments and is not a law firm; that question is for your counsel, and counsel usually starts from an inventory of what actually loads.
If you would rather not do this yourself
The free scan gives you every third-party script on your site, page by page, written so you can forward it to whoever looks after the site. If you want it done for you, we remove the scripts, re-scan and send a log of what changed; what that costs is on the pricing page. Nothing on your site changes without your approval in writing.
The other five
- Google Analytics · on 68% of sites scanned
- Google Tag Manager · on 44% of sites scanned
- Google Ads conversion tag · on 21% of sites scanned
- Microsoft Clarity · on 7% of sites scanned
- CallRail call tracking · on 6% of sites scanned
Counts are the latest scan per practice as of 2026-10-08, from the same computation as the benchmark. No practice is named on this page.