This checklist works with any tag manager, consent platform, analytics product or advertising platform. It gathers the steps from our remediation guides into one list that a business owner, web agency or in-house team can work through in an afternoon, with a link to the full guide behind each item. It costs nothing to use and needs only a desktop browser and access to the site's tag manager.
What does the checklist cover, and who can use it?
It covers what tags run on the site, whether they wait for consent, whether a refusal stops them, and what sensitive pages, search boxes, forms, replay tools and servers send.
Anyone with a desktop browser and access to the site's tag manager can run it. Work through the sections in order, write down what you find with the date, and fix the earliest failure first: a tag that runs before consent matters more than a privacy policy that lists it in the wrong place. For a shorter first pass that needs only a browser, start with the Website Tracking Compliance Self-Check. If you received a letter about your site, keep the records described in the last section before changing anything.
What tags are on the site, and where do they load from?
Every tag that sends data to another company belongs on one written list, whether it loads from the tag manager, the site's own code, a plugin, a widget or a server.
- [ ] Export the live tag manager container and list each tag, its destination and its trigger. Checking a Case File Against Your Tag Manager shows how.
- [ ] Search the site's theme, header and plugins for tags pasted in directly. Remove Unauthorized Website Trackers covers where they hide.
- [ ] List chat, scheduling, video, form and review widgets that load their own code.
- [ ] Note any server container or first-party collection address that receives events from the browser.
- [ ] For each vendor, record what it receives, from the vendor's own documentation. Tracking Pixels: What They Capture explains the common categories.
- [ ] Remove any tag with no current business owner or purpose.
Do the tags wait for the visitor's choice?
They should: no advertising, analytics or replay request should leave the browser before the visitor chooses, and checking takes five minutes in a private window.
- [ ] Load the home page in a private window, touch nothing, and filter the Network panel for each vendor on your list. Does Your Reject Button Actually Stop Tracking? walks through it.
- [ ] In the tag manager, check each tag's consent settings. A tag with no consent settings and no built-in consent checks runs whenever its trigger fires.
- [ ] Know which consent setup your analytics tags use. In Google's advanced setup, for example, tags send measurements without cookies while consent is denied. Google Consent Mode: Basic Versus Advanced explains the difference.
Does a refusal stop every tag?
It should, and you confirm it by clicking the banner's refusal, browsing three or four pages, and checking that nothing goes to any vendor afterward, including your own tracking subdomain.
- [ ] Click Reject or Necessary only, clear the Network list, browse, and filter again for every vendor.
- [ ] Check the cookies written after the refusal. An advertising cookie set after a refusal means a tag ran anyway.
- [ ] Repeat on a phone-sized window and in a second browser.
- [ ] Make the banner's words match what the site does. If a choice cannot stop a tag, remove the tag or change the banner.
Which pages should carry no advertising tags?
Pages that say something about a person's health, money or legal situation: condition and service pages, provider profiles, booking, intake, insurance, portal, thank-you and search results pages.
- [ ] Map those page addresses for your site.
- [ ] Fire advertising tags only on an allowlist of pages that say nothing sensitive. Removing the Meta Pixel from Patient Pages shows the method, and it works for any vendor.
- [ ] Keep analytics and advertising tags off pages behind a login.
- [ ] Health sites: read Google Analytics 4 on Health Websites and The Meta Pixel on Health Websites.
- [ ] Addiction treatment programs: read Website Tracking at Addiction Treatment Programs.
What do the search boxes and forms send?
Check that no search words or form details reach a vendor through page addresses, page titles, event parameters or contact-matching features.
- [ ] Search the site for a made-up word and look for it in every vendor request. Site Search and Form Events explains the routes.
- [ ] Turn off analytics search and form events you do not need.
- [ ] Turn off any feature that collects email addresses or phone numbers from forms for advertising matching.
- [ ] Keep advertising tags off pages reached only after a form is sent.
- [ ] Test with made-up entries. Never submit a real intake, appointment or contact request.
Is session replay masked, or off, where it should be?
Replay should be off on forms and sensitive pages, or set to mask or exclude every field and the sensitive text around it, and checked again after each layout change.
- [ ] Read the vendor's masking and exclusion settings. Session Replay on Healthcare Sites compares the documented controls.
- [ ] Confirm the settings cover text outside input boxes, such as appointment details shown on a page.
- [ ] Retest when forms, layouts or vendors change.
Does any server forward the same data?
If the browser sends events to your own domain, a server you run may forward them to the same vendors, so the server's tags need the same consent and page rules as the browser's.
- [ ] List every destination in the server container and every server-to-server connection to an advertising platform.
- [ ] Pass the visitor's consent choice to the server, and make every server tag check it.
- [ ] Apply the sensitive-page rules on the server too. Meta Conversions API and Server-Side Tagging explains why.
Does the privacy policy match what the tags do?
It should name each vendor, say what it receives, and describe what the banner's choices actually do, because a policy that promises more than the site delivers is a statement consumer-protection laws can reach.
- [ ] Name each vendor on your inventory and what it receives.
- [ ] Describe what each banner choice does, in words the tags actually honor.
- [ ] Remove promises the site cannot keep.
- [ ] Update the policy whenever the tag inventory changes.
What records should you keep?
Keep every tag manager version, consent platform setting, server log, test result and policy version with its date, and make changes as new versions rather than deleting old ones.
- [ ] A dated log of what changed, when, and who reviewed it. Remove Unauthorized Website Trackers has a template.
- [ ] Old tag manager versions, kept rather than deleted.
- [ ] Screenshots and notes from each test, with the date and time.
- [ ] If you have received a letter, the records described in What to Do After a Privacy Demand Letter, kept before anything changes.
Which laws does this checklist track?
It tracks the federal Wiretap Act's consent rule, HIPAA's limit on disclosing health information, and the federal and state bans on deceptive practices.
- Consent. The federal Wiretap Act's exception for a party's consent does not cover an interception made "for the purpose of committing any criminal or tortious act," 18 U.S.C. § 2511(2)(d). One-Party Consent and the Party Exception explains the rule.
- Health information. 42 U.S.C. § 1320d-6 makes it a crime to knowingly disclose individually identifiable health information in violation of HIPAA's rules.
- Deception. The FTC Act declares "unfair or deceptive acts or practices in or affecting commerce" unlawful, 15 U.S.C. § 45(a)(1), and state laws such as New York General Business Law § 349 reach deceptive practices too.
The checklist describes configurations, not legal conclusions. Your own attorney can tell you how these laws apply to your site.
What sources does this guide rely on?
This guide relies on the statute text listed here and on the linked guides, which cite the vendor documentation behind each item. Checked on November 10, 2026.
- 18 U.S.C. § 2511 (Legal Information Institute)
- 42 U.S.C. § 1320d-6 (Legal Information Institute)
- 15 U.S.C. § 45 (Legal Information Institute)
- Google: Consent mode overview