Cookie Consent and Tracking — How UniPixel Keeps You Compliant

If you run ads on Meta, Google, TikTok or Microsoft, you need conversion tracking to work. But if your website has visitors in the EU, UK, or other regulated regions, you also need to respect their privacy choices. Get it wrong and you’re either losing conversion data or risking a compliance issue.

This is where cookie consent comes in — and where most tracking setups get complicated. UniPixel keeps it simple.

What is Cookie Consent

Privacy laws like the GDPR (Europe), the ePrivacy Directive, and similar regulations around the world require websites to ask visitors for permission before tracking their activity. That includes firing pixels, setting cookies, and sending conversion events to ad platforms.

When a visitor lands on your site, they see a consent banner — a popup asking whether they accept or decline different categories of tracking. These categories are typically:

  • Necessary — essential cookies the site needs to function (always allowed)
  • Functional — cookies that remember preferences like language or region
  • Performance / Analytics — cookies used to measure site usage and traffic
  • Marketing / Advertising — cookies used for ad targeting and conversion tracking

The visitor makes their choice, and the website is expected to honour it. If they decline Marketing cookies, no ad pixel should fire. If they decline Performance cookies, no analytics data should be sent.

What is a CMP?

A Consent Management Platform (CMP) is the tool that handles this process. It shows the consent banner, records the visitor’s choices, and stores those choices as cookies in their browser. Popular CMPs include OneTrust, Cookiebot, Complianz, CookieYes, and others.

The problem is that most tracking plugins ignore these choices entirely, or require complicated manual integration to connect your CMP to your pixel setup. That means either your consent banner is decorative and your site isn’t actually compliant, or your events stop firing altogether because nobody wired things up properly.

How UniPixel Handles Consent

UniPixel treats consent as a core part of the tracking pipeline, not an afterthought. Every event — whether it fires in the browser (client-side) or from your server (server-side) — passes through a consent gate before anything is sent.

Here’s what that means in practice:

  1. A visitor arrives on your site and makes their consent choices via the consent banner.
  2. Those choices are stored as cookies in their browser.
  3. Before UniPixel sends any event to Meta, Google, TikTok or Microsoft, it checks those cookies.
  4. If the visitor has granted consent for Marketing and Performance, the event fires normally — both the browser pixel and the server-side API call.
  5. If they haven’t, nothing is sent. No data leaves the browser, no data leaves your server.

This happens automatically. There is no manual wiring, no code to write, no tag rules to configure.

Two Options — Both Fully Handled

UniPixel gives you two paths depending on your setup, and both are fully supported out of the box.

Option 1: Use UniPixel’s Built-in Consent Banner

Don’t have a consent solution yet? UniPixel includes one. Enable it in your Consent Settings, and your visitors see a clean consent popup where they choose which cookie categories to accept. UniPixel stores their choices and respects them across every platform and every event — client-side and server-side.

No third-party consent plugin needed. No extra cost. One toggle and it’s live.

Option 2: Use Your Existing Consent Manager

Already running a CMP on your site? Keep it. UniPixel detects and reads consent choices from all of the most popular WordPress consent managers:

  • OneTrust
  • Cookiebot
  • Osano
  • Silktide
  • Orest Bida
  • Complianz
  • CookieYes
  • Moove GDPR

There is nothing to connect or configure. Each of these platforms stores consent choices in its own cookie format. UniPixel knows how to read every one of them. It parses the cookies your CMP has already set, builds a normalised consent summary, and uses that summary to decide whether each event is allowed to fire.

If your CMP is on this list, consent is handled. Select “Use my existing Consent Manager” in UniPixel’s settings and you’re done.

What Happens Under the Hood

For those who want to understand the mechanics:

UniPixel runs consent parsing on both sides of the tracking pipeline. In the browser, JavaScript reads the consent cookies and checks them before any pixel fires. On the server, PHP reads the same cookies from the incoming request and checks them before any API call is made to Meta, Google or TikTok.

Both checks require the same thing: Marketing and Performance consent must both be granted. If either is missing or has been declined, the event is blocked on both sides.

This dual-layer approach means there’s no gap. Even if a browser extension interferes with client-side consent checking, the server-side gate still holds. And because UniPixel generates a single normalised consent summary regardless of which CMP set the original cookies, the logic is consistent across all supported platforms.

One Toggle, Full Control

In your UniPixel Consent Settings, the “Honour User Consent” toggle controls the entire system:

  • On — every event is gated by consent. If a visitor hasn’t given explicit permission, nothing is sent. If no consent choices are found at all (for example, if your CMP hasn’t loaded yet or the visitor hasn’t interacted with the banner), events are blocked by default.
  • Off — all events fire without consent checks. This is useful during testing, or for sites operating in regions where cookie consent isn’t a legal requirement.

Why This Matters for Your Ad Performance

Consent isn’t just about compliance — it directly affects your ad data quality. If your consent setup is broken and events fire regardless, you risk legal exposure. If it’s overly aggressive and blocks events unnecessarily, your ad platforms lose conversion data and your campaigns can’t optimise properly.

UniPixel strikes the right balance: events fire when they should, and don’t when they shouldn’t. Your ad platforms get the maximum amount of legitimate conversion data, and your visitors’ privacy choices are genuinely respected.

No extra plugins. No manual integration. No gaps between what the banner says and what actually happens.