Summary
- Advertising tags send information about each visit to the ad platform, usually including the address of the page being viewed.
- On a clinic website, a page address such as
/conditions/endometriosiscan reveal why someone is visiting. The Privacy Commissioner has found that this kind of browsing data can be health information. - Meta now restricts page addresses for many health advertisers, but Google Ads, Microsoft, Pinterest, LinkedIn, Snap and Reddit tags often still receive them.
- You can check your own site in about fifteen minutes using the developer tools already in your browser.
Most clinic owners did not choose to share patient information with Facebook or Google. A developer added a tag to measure a campaign, or a website template came with one built in. This guide explains, without jargon, what those tags actually send and how to tell whether yours are sending something they shouldn’t.
What a pixel is and what it sends
A tracking pixel is a small image or piece of JavaScript code on a web page. When the page loads, the visitor’s browser contacts the pixel provider’s server and sends information about the visit1. In its basic form that includes the page address, the time, language settings, the IP address, and device and browser details. More advanced setups can also send form entries, search terms and button clicks1.
The OAIC’s guidance notes that information can make a person reasonably identifiable even without a name, for example an IP address, a page address, or a hashed email address that the platform can match to an account2. When the OAIC looked closely at 12 health websites, it found full page addresses, searches and button clicks being sent, and hashed form fields shared with platforms3.
Why the page address is the problem
Clinic websites are usually organised by service. That is good for patients and for search engines, but it means the page address often describes a health need: /ivf-costs, /mental-health/anxiety, /book/skin-check. When an advertising tag sends that address, it sends the reason for the visit.
In the Medmate determination, the structure of the site’s page addresses could reveal conditions or prescriptions4. The Commissioner found that visiting pages about topics such as egg freezing or fertility checks was enough to reveal health information1. In our pilot Clinic Pixel Index, 18% of the 94 clinic sites we scanned sent a page address naming a condition or treatment to an advertising platform5.
The Meta pixel in 2026
Meta assigns advertisers’ data sources to categories, including a Health and wellness category6. Data sources in some categories carry restrictions. The most common, Core Setup, “restricts the sharing of custom parameters and parts of URLs following the domain”. Meta also restricts certain standard events, and blocks custom events until they are reviewed7.
So is a Meta pixel on a clinic site now safe? Not automatically. Meta itself says its systems “are not a substitute for your own compliance mechanisms” and that the advertiser remains responsible7. The pixel still loads, still identifies the browser, and still tells Meta that the person visited your clinic’s site. In our scan, Meta received only the domain on 38 of the 40 sites where its pixel fired on an inner page, but it still fired, and because our scanner never touched a banner, every one of those requests happened before any consent choice5.
The Google Ads tag, and the others
Google Ads conversion and remarketing tags work in a similar way. Google’s advertising policies treat health as a sensitive interest category, covering things like health conditions, mental health counselling, pregnancy and infertility, and cosmetic procedures. In those categories, advertisers cannot use their own audiences, such as remarketing lists, Customer Match or lookalike segments8. That policy limits how you can target ads, but it does not stop a tag on your website from sending page addresses in the first place.
Google’s Consent Mode lets tags adjust their behaviour based on the visitor’s choice. In its “advanced” setup, Google tags load before consent and send cookieless pings when consent is denied, and the page address can still be included9. In “basic” mode, tags are blocked until the visitor interacts with the banner9. We explain this further in our guide to cookie banners.
In our pilot, the condition and treatment page addresses we saw were sent to Google Ads, Microsoft Bing, Pinterest, Snap, LinkedIn and Reddit tags rather than to Meta5. If your agency checked “the Facebook pixel” and stopped there, they may have missed the larger exposure.
Check your own site in fifteen minutes
You don’t need special software. Use Chrome, Edge or Firefox on a desktop computer.
- Open a private or incognito window so you start without existing cookies.
- Open the developer tools (press F12, or right-click the page and choose Inspect) and select the Network tab.
- Visit one of your most sensitive service pages directly, for example a condition or treatment page, or your booking page. Do not click the cookie banner if there is one.
- In the Network filter box, type each of these in turn:
facebook.com/tr,googleadservices,doubleclick,bat.bing,ct.pinterest,px.ads.linkedin,analytics.tiktok,tr.snapchat,reddit. - Click any request that appears and look at its address or Payload. If you can see your page’s path, such as
/conditions/…, that platform received it. - Repeat on your booking confirmation page, if you can reach it with a test booking your reception team will cancel.
If requests appear before you have touched the banner, those tags are firing before consent. If the payload includes your page path, the tag is receiving the reason for the visit. Our free scan does the homepage part of this automatically.
What to do if you find a leak
- Ask whether you still need the tag. Remove old campaign pixels and duplicates first. The OAIC has described a provider that found 50 pixels added over time by a vendor3.
- Stop advertising tags from loading on condition, treatment and booking pages, or until the visitor has given specific consent. The OAIC suggests considering whether pixels are needed on particular pages at all2.
- Replace descriptive page addresses in tag data with generic values, using a privacy-safe dataLayer.
- Turn off features that send form contents or contact details to ad platforms, such as Meta’s Advanced Matching, which was enabled at points in both OAIC investigations4.
- Make sure Google Analytics receives no personal information. Google requires that page addresses and titles be free of it10.
- Write down what you changed and when, and re-check after every website update.
See what your own website shares
The free Akesis scan checks your homepage for advertising and analytics tags, whether they fire before consent, and what they receive. It takes about a minute and needs no install.
Run a free scanSources
- Mallesons, Privacy Commissioner zooms in on tracking pixels, 3 July 2026. www.mallesons.com/au/en/insights/latest-thinking/privacy-commissioner-zooms-in-on-tracking-pixels.html
- OAIC, Tracking pixels and privacy obligations, 4 November 2024. www.oaic.gov.au/privacy/privacy-guidance-for-organisations-and-government-agencies/organisations/tracking-pixels-and-privacy-obligations
- OAIC, Your life, pixelated: how tracking pixels watch your every click, 24 June 2026. www.oaic.gov.au/news/blog/your-life,-pixelated-how-tracking-pixels-watch-your-every-click
- Clayton Utz, OAIC determines the use of tracking pixels “did not track”, 8 July 2026. www.claytonutz.com/insights/2026/july/oaic-determines-the-use-of-tracking-pixels-did-not-track
- Akesis, The Australian Clinic Pixel Index 2026 (pilot, n=94), 27 October 2026.
- Meta Business Help Centre, Help article: data source categories (including Health and wellness). www.facebook.com/business/help/1402913027039332
- Meta Business Help Centre, Help article: restrictions on data sources (including Core Setup). www.facebook.com/business/help/511197658391698
- Google Ads Help, Health in personalized advertising. support.google.com/adspolicy/answer/16701855
- Google for Developers, Consent mode overview. developers.google.com/tag-platform/security/concepts/consent-mode
- Google Analytics Help, Best practices to avoid sending Personally Identifiable Information (PII). support.google.com/analytics/answer/6366371
Sources were checked on 27 October 2026. Links to third-party sites are provided for reference; Akesis is not affiliated with the organisations listed.