If your site sends page-level activity to an advertising platform, a recent federal appellate ruling should change how you audit it. On October 23, 2026, the Fifth Circuit decided Rand v. Eyemart Express, L.L.C., No. 25-10784, reversing the dismissal of a proposed class action. The plaintiffs allege an optical retailer disclosed consumers' health-related information to Meta Platforms, Inc. through the Meta Pixel.
Two findings matter for your program. The court held the plaintiffs sufficiently alleged an injury to establish Article III standing. It also held they plausibly alleged that their website interactions amounted to individually identifiable health information (IIHI) sent to Meta without their knowledge or consent. The case was not dismissed at the threshold, and that is the point of this playbook.
1. The Problem
Ordinary browsing events can become sensitive data when they reveal a health context. A page view, a form interaction, or a button click on a health-adjacent service can carry meaning. Paired with an identifier, that event may be characterized as IIHI once it reaches a third party.
Many teams treat pixels as marketing infrastructure. Litigants treat them as disclosure mechanisms. Your job is to make sure nothing fires before valid consent exists, and that you can prove it.
2. What You Need Before Starting
Gather these before you touch a configuration:
- Tag inventory access. Admin rights on your Tag Manager and any hard-coded scripts in your templates.
- A Consent Management Platform with prior consent blocking, granularity by purpose, and exportable consent logs.
- Browser developer tools and a network capture tool such as a proxy or HAR export.
- A data-flow map of which pages and forms touch health-related services, products, or appointments.
- Legal input on which of your page categories could be characterized as health-related.
- A named owner for each third-party vendor tag.
3. Step-by-Step Implementation
Step 1: Inventory every tracker. Crawl your site and list every script, pixel, and third-party cookie. Include tags added directly to templates, which Tag Manager audits miss. Record the vendor, purpose, data fields, and the pages where each fires.
Step 2: Classify page sensitivity. Tag URLs and form flows into tiers. Treat anything tied to health services, appointments, prescriptions, or eligibility as high sensitivity. Decide per tier whether non-essential cookies and advertising pixels may ever load.
Step 3: Gate advertising tags behind prior consent. Configure your CMP so Meta Pixel and similar tags do not load until a clear affirmative action grants the relevant purpose. In your Tag Manager, set consent-based trigger conditions rather than relying on a page-load trigger. Block by default, then release on consent. This is data protection by default in practice.
Step 4: Suppress advertising tags on high-sensitivity pages entirely. Consent alone may not be enough where the page content itself implies a health condition. Exclude those URL patterns from pixel firing, and remove advertising tags from authenticated or appointment flows. Consider server-side controls that strip URL parameters, form field values, and event metadata before any vendor call.
Step 5: Reduce what events carry. Audit event payloads. Remove query strings, search terms, product names, and free-text fields that describe a condition. Avoid sending hashed email identifiers or other universal identifiers alongside sensitive events.
Step 6: Write specific purpose disclosure. Your consent notice should name the advertising purpose, identify that data goes to third parties, and offer symmetry of choice with equal prominence for accept and reject. Vague language undermines unambiguous consent.
Step 7: Configure withdrawal. Provide a persistent control for withdrawal of consent, and confirm that withdrawal stops tag firing on the next page load and clears related identifiers.
Step 8: Log consent evidence. Store timestamp, notice version, choices by purpose, and a pseudonymous user reference. Retain the logs so you can show what a given user saw and chose.
Step 9: Update contracts and policies. Confirm vendor agreements reflect the restrictions you've configured, and align your privacy notice with what actually loads.
4. Validation: Verify It Works
Don't trust the dashboard. Test the browser.
- Open a clean browser profile with no stored consent.
- Open developer tools, go to the Network tab, and enable "Preserve log."
- Load your homepage and a high-sensitivity page without interacting with the consent notice.
- Filter requests for known advertising domains, including Meta's pixel endpoint (search for
facebook.com/trandconnect.facebook.net). - Confirm zero requests before consent. Any hit is a failure.
- Reject all, reload, and repeat. Confirm still zero.
- Accept advertising, then visit a high-sensitivity page. Confirm the pixel stays suppressed there if you applied Step 4.
- Withdraw consent and confirm requests stop on the next navigation.
- Inspect cookies, local storage, session storage, and IndexedDB for advertising identifiers set before consent.
- Export a HAR file for each test as dated evidence.
Run the same sequence on mobile browsers and in-app web views, where behavior often differs.
5. Maintenance
Tracking drift is the real risk. Build recurring controls:
- Scheduled scans. Re-crawl on a fixed cadence and after every release. Flag new domains automatically.
- Change control for tags. Require privacy review before any marketing tag is added or edited in your Tag Manager.
- Vendor monitoring. Watch for vendors changing data collection behavior or adding sub-processors.
- Consent renewal. Re-prompt when purposes, vendors, or notice text change materially, and refresh stale records on a defined schedule.
- Log integrity checks. Periodically sample consent records against observed network behavior.
- Legal watch. Track how courts apply the IIHI reasoning in Rand and update your page-sensitivity tiers accordingly.
A court allowing this case to proceed doesn't decide the merits. It does tell you that "it's just analytics" won't end a dispute early. Evidence that nothing fired without valid consent will.




