Skip to content

Your healthcare client can't send patient data to Meta. They still need to run ads.

Regulated clients need tracking that respects consent and keeps sensitive data away from ad platforms. We set up Consent Mode v2 and privacy-safe conversion tracking, and document exactly what is sent where so the client's compliance team can review it.

source

Consent banner

Consent Mode v2
Server-side filter
Ad platforms

Who it's for

  • Clients in healthcare, dental, finance, insurance and legal
  • Sites with EEA or UK traffic that need Consent Mode v2
  • Accounts where URLs, form fields or page titles could expose sensitive information

What usually breaks

If any of this sounds familiar, the numbers are off.

  • 01

    Tags fire before consent

    Ad tags load before the banner has an answer, or ignore the answer entirely.

  • 02

    Sensitive data in URLs

    Page paths, form fields or search terms that reveal health or financial details reach ad platforms.

  • 03

    Consent Mode half set up

    A banner exists, but the defaults and updates Google needs were never configured.

  • 04

    Nobody knows what's sent

    The client's compliance team asks what data leaves the site, and there's no answer.

What we do

What we do, step by step.

  1. 01Map what every tag sends today: URLs, parameters, form fields and identifiers
  2. 02Configure Consent Mode v2 defaults and updates with the client's consent banner
  3. 03Strip or replace sensitive data before it reaches Google or Meta, using server-side GTM where needed
  4. 04Use internal IDs instead of personal data for conversions where the client requires it
  5. 05Test consent states: accepted, rejected and no answer
  6. 06Write a tracking data spec the client's compliance or legal team can review

Platforms covered

Works with the client's existing stack.

  • Google Consent Mode v2
  • Cookiebot
  • OneTrust
  • CookieYes
  • Usercentrics
  • Server-side GTM
  • Google Ads
  • Meta
  • GA4

Something else? Tell us which tools the client uses and we'll confirm before you pay.

How we prove it

Nothing is “done” until a test lead says so.

  • Every consent state tested

  • Outgoing requests inspected for personal data

  • A written spec of what each platform receives

Privacy & consent: questions

4 questions

No setup can promise that, and we don't claim certifications. We build privacy-safe tracking that sends no personal data to ad platforms and document it, so the client's compliance or legal team can decide.

Some, yes. Consent Mode lets Google model part of what is lost, within its own thresholds. Correct consent is not optional, so the aim is accurate data within the rules.

No. We implement what the client's legal or compliance team approves, and we flag risks we see in the current setup.

Not always. Consent Mode on its own is a browser setup. Server-side GTM helps when data has to be filtered before it reaches ad platforms.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.