GDPR and HIPAA compliance
One setting decides how visitors are tracked. GDPR and HIPAA ask for different things, so each has its own mode.
Set this up with AI
Copy this prompt into ChatGPT, Claude or whichever AI you use. It carries this whole guide, the pages it depends on, and a link to every video, so it can walk you through it one step at a time.
These controls live under your site's Settings, in the Privacy & Security section. If you use WordPress, the Privacy card in the TrueMetriks plugin settings is the same setting: change it in either place and both change.
Privacy & Security
Control how visitors are identified and protected.
Privacy mode
Full tracking
Cookies, IP address and cross-session attribution. Use this if your visitors are outside the EU or you collect consent another way.
Consent banner (GDPR)
Visitors choose. Accept gives full tracking; Reject or no answer keeps them cookieless. If you already use a consent tool, we follow its choice instead of showing our banner.
I already use a consent tool (Cookiebot, CookieYes, Complianz, OneTrust, Shopify's banner or similar)
HIPAA (cookieless)
For healthcare sites. No cookies, no IP address or other identifier in your reports, and nothing sent to any ad platform. Meta, Google and TikTok receive nothing from this site, because every parameter they need is forbidden by HIPAA, so your ads will not optimize on these conversions. Your dashboard still counts every visit and sale.
Block bot traffic
Blocks bots that announce themselves, such as crawlers and scripts. Bots that pretend to be real browsers can't be blocked safely. We mark them as Likely bots in your reports instead.
Choose a privacy mode
Privacy mode has three options. Each one decides what is stored on the visitor's device and what reaches your ad platforms.
| What changes | Full tracking | Consent banner (GDPR) | HIPAA (cookieless) |
|---|---|---|---|
| Who it is for | Visitors outside the EU, or consent collected another way | Sites with visitors in the EU | Healthcare sites |
| Cookies TrueMetriks sets on the visitor's device | Yes | Only after the visitor clicks Accept, plus one cookie that stores their answer | None |
| IP address in your reports | Yes | No | No |
| Conversions sent to ad platforms | All of them | Only from visitors who clicked Accept | None |
| Ads optimize on your conversions | Yes | On the visitors who clicked Accept | No |
| Banner shown to visitors | No | Yes, unless you already use a consent tool | No |
Cookies left on a device from days when the site ran Full tracking are ignored while a visitor is cookieless, not removed. Only a Reject on the consent banner deletes them (see Accept, Reject or no answer).
Full tracking is the default. It gives the most complete attribution.
Consent banner (GDPR) lets each visitor decide. It is the GDPR mode.
HIPAA (cookieless) keeps identifiers from the browser away from your visitors' devices, your reports and your ad platforms. It is off unless you turn it on.
Why GDPR and HIPAA need different modes
GDPR asks for consent. Sending a visitor's data to an ad platform needs their consent, whether it travels through a browser pixel or server to server. Once a visitor clicks Accept, sending is allowed.
HIPAA forbids the sending itself. On a healthcare site, an IP address, cookie, click ID, email or phone number sent to an ad platform together with a visit can disclose protected health information. Ad platforms do not sign the agreement HIPAA requires, and a click on a cookie banner is not a valid HIPAA authorization.
So a banner solves GDPR but cannot solve HIPAA. That is why the two are separate modes.
HIPAA mode (cookieless)
Use this mode on healthcare sites. TrueMetriks still counts every page view, lead and sale in your own dashboard. From the browser, it never collects anything that identifies the person, and it sends nothing to any ad platform. No banner is needed, because nothing is stored on the visitor's device.
What it does
No cookies. Nothing is written to the visitor's browser that could recognize them later.
No identity capture. The tracker does not read email addresses, names or phone numbers out of your forms or page links, and keeps none of them on the device.
No IP address or other identifier in your reports. The IP address is used to place the visit on the map (country, region and city) and to keep one day's visit together. The address itself does not appear in your reports and is never sent to an ad platform.
No identifiers in page links. Email addresses, phone numbers, names and ad click IDs that appear in your page links under the usual parameter names are blanked before the visit reaches your reports, so your reports show only that a click ID was there, not its value.
Nothing sent to ad platforms. Meta, Google Ads, GA4 and TikTok receive no events from this site: no IP address, no browser details, no click IDs, no email, no visitor ID.
No third-party scripts. Microsoft Clarity session recordings and the TikTok pixel are not loaded.
A visitor ID that resets every day. To keep one visit's pages together, the same device on the same network is counted as one visitor until midnight UTC. After that it is a new visitor, so no one can be followed from one day to the next.
Why nothing reaches your ad platforms
An ad platform can only use a conversion when it can match it to a person. To match, it needs at least one of these: an IP address, its own cookies, the click ID from the ad, an email address or a phone number.
On a healthcare site, HIPAA forbids sending every one of those to an ad platform.
A conversion with none of them cannot be matched, and Meta rejects such events outright. So in this mode TrueMetriks sends nothing at all, rather than sending events that cannot work.
What you give up
Ad optimization. Meta, Google and TikTok see no conversions from this site, so their algorithms cannot optimize your campaigns toward your leads and sales. Expect your ad platforms to report fewer conversions than your dashboard.
Returning visitors. Someone who comes back tomorrow is counted as a new visitor, so multi-day journeys and cross-session attribution are not available.
Data you send us yourself
Server-side sources you connect on purpose keep working: WooCommerce orders from the WordPress plugin, and webhooks from Stripe, Whop, PayPal, GoHighLevel, ClickFunnels and the like. They appear in your own dashboard with the details you send.
In this mode they are never passed on to an ad platform.
If you are covered by HIPAA, only connect sources that send TrueMetriks patient details once the agreements HIPAA requires are in place.
Turn it on
- Open the site's Settings and go to Privacy & Security.
- Set Privacy mode to HIPAA (cookieless).
- Leave Block bot traffic on.
- Click Save changes.
The tracker picks up the change within about a minute. On Shopify, copy the pixel code again and replace it in Shopify (see Platform notes).
Consent banner mode (GDPR)
Use this mode when your visitors are in the EU. Your visitors see a small banner and choose for themselves.
What visitors see
The banner says in a short note that the site uses cookies to measure its ads and improve the site, or shows your own text instead (see Position, link and text). It has an optional link to your privacy policy and two buttons, Reject and Accept. Both buttons are the same size, weight and color, so neither choice is pushed.
The banner does not block the page. Visitors can keep reading and scrolling while it is open.
Its text follows the language of your page, or the visitor's browser, in English, German, French, Spanish, Italian, Portuguese, Polish, Czech, Ukrainian, Chinese, Japanese and Korean. Any other language shows English.
Accept, Reject or no answer
Accept switches that visitor to full tracking from that moment. Cookies are set, and their conversions are sent to your ad platforms, so your ads optimize on them.
Reject keeps the visitor cookieless, with nothing sent to ad platforms, exactly as in HIPAA mode. TrueMetriks also deletes its own cookies they had. Meta's _fbp browser ID is left in place, because the site's own Meta pixel may share it.
No answer is treated like Reject. Until the visitor clicks Accept, they are cookieless.
Pages viewed before the visitor clicked Accept stay anonymous. If they accept on the page they landed on, the ad that brought them is still captured.
Position, link and text
Banner position places it at the bottom left (the default), bottom center or bottom right of the screen. Pick the corner your chat widget does not use.
On phones the banner always spans the bottom of the screen, whatever you choose.
Privacy policy link (optional) adds a "Privacy policy" link to the banner. It must start with https://. Leave it empty to show no link.
Banner text (optional) replaces the banner's sentence with your own words, up to 500 characters. It is plain text, shown exactly as you write it in every language, while the buttons and the "Privacy policy" link stay in the visitor's language. Leave it empty to use our sentence, which is shown in the visitor's language.
Asking again
The visitor's answer is remembered for 180 days in one small cookie, _tmc, which stores only the answer itself. After that the banner asks again. Some browsers, such as Safari, delete cookies set by a page's scripts after 7 days, so their visitors may be asked again sooner.
A site on several domains asks once per domain. A visitor who accepts on yourshop.com is asked again on yourfunnel.com.
Add a cookie settings link
Visitors must be able to change their mind as easily as they decided. Add a link such as "Cookie settings" to your site's footer that opens the banner again.
Any element with the data-tm-consent attribute opens the banner when clicked:
<a href="#" data-tm-consent>Cookie settings</a>
You can also open it from your own code with tm.consent().
If you ticked I already use a consent tool, neither of these opens anything: use your own tool's settings link instead.
When a visitor who accepted clicks Reject later, TrueMetriks deletes its own cookies on that browser (except Meta's _fbp, as above), forgets the Accept it recorded for that browser on its servers, and stops: later sales linked to that browser, including ones that arrive by webhook, are no longer passed to your ad platforms. Cookies that Microsoft Clarity or TikTok set while they had accepted belong to those services and are not removed.
Turn it on
- Open the site's Settings and go to Privacy & Security.
- Set Privacy mode to Consent banner (GDPR).
- If your site already has a consent tool, tick I already use a consent tool and skip to the last step.
- Pick a Banner position, add your Privacy policy link (optional) and, if you like, your own Banner text (optional).
- Click Save changes.
Already using a consent tool
If your site already runs a consent tool such as Cookiebot, CookieYes, Complianz or OneTrust, choose Consent banner (GDPR) and tick I already use a consent tool. On Shopify, follow the Shopify note instead.
With the box ticked, TrueMetriks never shows its own banner, so the banner position, privacy policy link and banner text fields are hidden. Each visitor stays cookieless until your tool gives an answer. One exception: if your tool sets a Google Consent Mode default of granted, with no region, that page runs with full tracking until the visitor answers.
Google Consent Mode is read automatically. Most consent tools publish the visitor's answer this way. A visitor counts as accepted only when your tool grants both analytics and advertising storage (analytics_storage and ad_storage). Anything less keeps them cookieless.
If your tool does not publish Google Consent Mode, tell TrueMetriks the answer yourself from your tool's accept and reject callbacks:
// When the visitor accepts in your consent tool
window.tm && window.tm.consent(true);
// When the visitor rejects, or withdraws consent
window.tm && window.tm.consent(false);
With the box ticked, tm.consent() with no argument does nothing, because your own tool owns the banner.
If you forget to tick the box, TrueMetriks still looks for Google Consent Mode on the page and hides its banner when it finds it. Ticking the box is the reliable way: a tool that loads late, or that does not publish Google Consent Mode, would otherwise show a second banner.
Platform notes
Shopify. TrueMetriks' banner does not appear on Shopify, because the pixel runs inside Shopify's sandbox. Turn on Shopify's own cookie banner in Shopify Admin under Settings, Customer privacy, Cookie banner. The pixel follows it: a visitor who allows both analytics and marketing gets full tracking, anyone else stays cookieless. Wherever Shopify's cookie banner is not turned on for a visitor's region, Shopify reports that visitor as allowing analytics and marketing and the pixel tracks them fully, so turning on Shopify's banner is what makes this mode ask your visitors.
The Shopify pixel code is generated for your privacy mode. After you change the mode, copy the code again from Settings, Tracking, Shopify and replace it in Shopify. Until you do, the old code keeps the old behavior, with two exceptions: on a Consent banner (GDPR) site an old pixel is always treated as not accepted, and on a HIPAA (cookieless) site every event is handled as cookieless whatever the old pixel sends.
WordPress. Use the Privacy card in the TrueMetriks plugin settings, or the dashboard. In Consent banner (GDPR) mode, a WooCommerce order is passed on to your ad platforms only when the buyer clicked Accept.
ClickFunnels, GoHighLevel and custom sites. Set the mode in the dashboard. There is nothing to re-paste: your tracking snippet picks up the change on its own.
Webhooks. In Consent banner (GDPR) mode, a sale from a webhook (Stripe, GoHighLevel, ClickFunnels and others) is passed on to your ad platforms only when the buyer clicked Accept on your site, with the same email address, in the last 180 days, on a browser where they have not clicked Reject since. Visits from before you switched to Consent banner mode do not count as an Accept. In HIPAA mode it is never passed on.
Block bot traffic
Blocks bots that announce themselves, such as crawlers and scripts. Bots that pretend to be real browsers can't be blocked safely. We mark them as Likely bots in your reports instead: see Likely bots.
ON (default, recommended): Traffic from known bots and crawlers is filtered out and never counted, so your numbers reflect real people.
OFF: Bot and crawler traffic is counted alongside real visitors.
This setting is purely about data quality. It has no effect on privacy or compliance, so you can leave it on at all times.
What this does not cover
These modes control what TrueMetriks puts in your reports and sends to ad platforms. They are not legal advice.
Your overall GDPR and HIPAA compliance also depends on the other tools on your site, the data you choose to send us through webhooks and integrations, and any agreements your providers require. TrueMetriks does not hold a HIPAA certification.
Frequently asked questions
How do I make TrueMetriks GDPR compliant?
Open the site's Settings, go to Privacy & Security, set Privacy mode to Consent banner (GDPR) and save. Visitors who click Accept get full tracking and reach your ad platforms. Visitors who click Reject, or do not answer, stay cookieless and are never sent to an ad platform.
How do I make TrueMetriks HIPAA compliant?
Set Privacy mode to HIPAA (cookieless). No cookies are stored, no IP address or other identifier appears in your reports, and nothing is sent to Meta, Google, TikTok or any other ad platform. Your own dashboard still counts every visit and sale.
Why does HIPAA mode send nothing to Meta, Google or TikTok?
Ad platforms can only use a conversion when it comes with an IP address, cookies, click IDs, an email or a phone number. On a healthcare site HIPAA forbids sending any of those to an ad platform, and none of them sign the agreement HIPAA would require. With nothing left to match on, TrueMetriks sends nothing, so your ads will not optimize on these conversions.
Can I use the consent banner on a healthcare site instead?
No. Under HIPAA, clicking Accept on a cookie banner is not a valid authorization to share a patient's details with an ad platform. Healthcare sites should use HIPAA (cookieless).
What happens when a visitor ignores the consent banner?
They are tracked cookieless until they click Accept. Ignoring the banner never counts as consent.
I already use Cookiebot, CookieYes, Complianz or OneTrust. Will visitors see two banners?
No. Tick I already use a consent tool and TrueMetriks never shows its own banner. It follows your tool's answer through Google Consent Mode, or through tm.consent() if your tool calls it.
How does the consent banner work on Shopify?
TrueMetriks' banner does not appear on Shopify. Turn on Shopify's own cookie banner and the pixel follows it. After any change to your privacy mode, copy the pixel code again from the dashboard and replace it in Shopify.
Does Block bot traffic affect privacy?
No. Block bot traffic is purely about data quality, keeping known bots and crawlers out of your reports. It has no effect on privacy or compliance, so you can leave it on at all times.