Summary

  • Under the OAIC’s June 2026 determinations, the clinic that deploys a pixel is treated as collecting what it sends, even if an agency installed it. Responsibility can’t be outsourced.
  • Tracking problems often start with a well-meant change: a new campaign, a new tag, a new conversion. A short sign-off step before anything goes live catches many of them.
  • This checklist gives practice managers twelve questions to agree with their agency or developer, and gives agencies a clear standard to work to.
  • Print it, share it with your agency, and keep the answers on file.

Good marketing agencies want to measure results, and clinics want to know their spend is working. Nobody sets out to send patient information to an ad platform. But the OAIC has observed that many organisations were not aware of all the tracking pixels on their websites, often because marketing was separated from privacy or outsourced12. It also described one provider that found 50 tracking pixels added over time by a vendor1.

The Commissioner has found that an entity which commissions a pixel, controls its deployment and can customise it is the one collecting the information3. In other words, if a tag runs on your clinic’s website, your clinic is accountable for it. This checklist is a simple way to share that responsibility sensibly with the people who do the technical work.

How to use this checklist

Agree the checklist with your agency once, then ask them to answer it in writing whenever they propose a new tag, pixel, conversion, landing page or tracking integration. Keep the answers with your privacy records. If an answer is “we’re not sure”, the tag waits.

For agencies: treat this as your definition of done for any change to a health client’s website. It protects you as well as the clinic.

Before the tag: purpose and necessity

  • 1. What is it for? Name the campaign or report this tag supports, and the decision it will inform. If there is no clear purpose, don’t add it.
  • 2. Do we already measure this? Check for an existing tag that does the same job. Duplicate and forgotten tags are a common source of leaks.
  • 3. Could we do it without a third-party pixel? The OAIC suggests considering first-party channels such as email for some marketing1, and considering whether pixels are needed on particular pages at all4.

What the tag will receive

  • 4. Which pages will it run on? List them. Exclude condition, treatment and booking pages unless there is a specific, documented reason and consent. Where simply visiting a page reveals sensitive information, the OAIC suggests it may be preferable to avoid pixels4.
  • 5. What page address will it send? Confirm the tag receives a generic value, not the real path, wherever the path could describe a health need.
  • 6. Which events and parameters will it send? Event names must be generic (booking_complete, not book_ivf_consult). Parameters must not include condition, treatment, appointment type, practitioner specialty or dates.
  • 7. Will it send any contact details? Features that send form fields or hashed emails and phone numbers to ad platforms should be off. Meta’s Advanced Matching was enabled at points in both OAIC investigations3.
  • 8. Will it wait for consent? The tag must not fire before the visitor agrees, and must not fire if they decline. For Google tags, confirm the Consent Mode setup. For all other platforms, confirm the trigger is tied to the consent tool. Google states that the site owner must make sure both Google and third-party tags respect the visitor’s choice5.
  • 9. Do the banner and privacy policy cover it? If this is a new platform, update the banner wording and privacy policy before go-live. A privacy policy alone is not sufficient notice3.

Platform settings

  • 10. Is the ad account set up for a health advertiser? In Meta, check the data source’s category and any restrictions. Meta notes its systems are not a substitute for the advertiser’s own compliance6. In Google Ads, remember that health is a sensitive category for personalised advertising, and advertiser-curated audiences such as remarketing lists and Customer Match can’t be used for it7.
  • 11. Are audiences built from site visitors? Retargeting based on website behaviour was treated as direct marketing in the OAIC decisions, needing consent for sensitive information2. Don’t build audiences from visitors to health service pages.

After go-live

  • 12. How was it tested, and who checks it later? Ask for evidence: a screenshot of the browser Network tab, or a scan report, from the live site showing what the tag sends before and after consent. Agree who re-checks after each website change. The OAIC says pixels are not “set and forget”1.

A simple tag register

Ask your agency to keep a shared register with one row per tag. It becomes the evidence you need if a patient, insurer or regulator ever asks how your website handles data.

Suggested columns for a tag register
ColumnExample
Tag and platformGoogle Ads conversion tag
Purpose and ownerMeasure bookings from the winter campaign; agency account manager
Pages it runs onHome, about, contact. Not service or booking pages
Data sentbooking_complete event, generic page value, no parameters
ConsentFires only after advertising consent; blocked on decline
Added, last tested, review dateDates, with a link to the test evidence

When to remove a tag

Remove a tag when its campaign ends, when nobody can say what it is for, when a platform is no longer used, or when it cannot be configured to meet the checklist. The OAIC’s guidance recommends regular reviews of pixel use4. A quarterly clean-up is a sensible rhythm for most clinics, and a check after every website change.

Akesis Guard re-scans your key pages every week and flags new or changed trackers, so a tag added without sign-off doesn’t go unnoticed. See how it works.

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 scan

Sources

  1. 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
  2. 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
  3. 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
  4. 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
  5. Google for Developers, Consent mode overview. developers.google.com/tag-platform/security/concepts/consent-mode
  6. Meta Business Help Centre, Help article: restrictions on data sources (including Core Setup). www.facebook.com/business/help/511197658391698
  7. Google Ads Help, Health in personalized advertising. support.google.com/adspolicy/answer/16701855

Sources were checked on 27 October 2026. Links to third-party sites are provided for reference; Akesis is not affiliated with the organisations listed.