Support

Omea Consent · Guides

Own consent mode for Meta Pixel, TikTok and Microsoft UET

Load Meta Pixel, TikTok Pixel and Microsoft UET after Marketing consent, or right away with the platform's own consent mode – what changes and when.

Updated · Omea Consent 1.0.2

On this page
  1. The two options
  2. How each platform holds back
  3. Change the setting
  4. When own consent mode makes sense

Meta Pixel, TikTok Pixel and Microsoft Advertising (UET) each have their own way of holding back cookies until consent. In Omea Consent Pro you choose, per platform, whether to use it.

The two options

After Marketing consent (recommended, default) Own consent mode
Script loads Only after the visitor accepts Marketing Straight away
Before consent Nothing is sent to the platform The platform receives the request – the visitor’s IP address and browser details – but holds cookies and events
On consent The script loads and starts tracking The platform is told consent was granted and releases what it held
Platforms Meta, TikTok, UET, LinkedIn, Snap Meta, TikTok, UET

How each platform holds back

When you choose own consent mode, Omea uses the platform’s official consent API:

  • Meta Pixel – fbq('consent', 'revoke') until the visitor agrees, then grant.
  • TikTok Pixel – cookies disabled and consent held until the visitor agrees.
  • Microsoft UET – ad_storage denied by default and the page-load event held until the grant. If Microsoft consent signals are on under Settings › Advanced, the updates come from those; the card tells you which.

When the visitor chooses, Omea grants or revokes consent on the platform.

Change the setting

  1. Go to Omea Consent › Integrations and open the platform’s card.
  2. Choose After Marketing consent (recommended) or Own consent mode – script loads now, cookies and events wait for consent.
  3. Click Save changes.

When you pick own consent mode, the card warns: “The platform receives the visitor’s IP address and browser details before they choose. Check that this matches your privacy policy.”

Use it only if you and your privacy adviser are comfortable with the platform receiving a request before consent – for example where the platform’s consent mode is part of your agreed setup. For most sites, waiting for Marketing consent is simpler to explain and to defend.

Either way, the Conversions APIs send server-side events only with Marketing consent.

Frequently asked questions

Which option should I choose?

After Marketing consent (recommended) unless you have a reason to change it. It sends nothing to the platform before the visitor agrees.

Do LinkedIn and Snap have an own consent mode?

No. Their tags have no consent API, so they always wait for Marketing consent.

What happens for a visitor who already agreed?

Returning visitors who granted Marketing consent load the tag normally, with either option.