Support

Omea Consent · Troubleshooting

Tracking scripts not running after consent: how to fix it

Analytics or a pixel not firing after visitors accept cookies? Check the script's category, location, Enabled switch and snippet in Omea Consent.

Updated · Omea Consent 1.0.2

On this page
  1. 1. The visitor hasn’t accepted that category
  2. 2. The script is switched off
  3. 3. It’s in the Body location and your theme lacks wp_body_open
  4. 4. The snippet is incomplete
  5. 5. Auto-blocking is holding something it depends on
  6. 6. You’re on an old version
  7. How to see what’s happening

Scripts in Omea Consent › Scripts are printed inert and switched on in the browser when the visitor accepts their category. If a script never runs, one of these is usually why.

1. The visitor hasn’t accepted that category

A script in Marketing only runs after Marketing is accepted. Test in a private window and click Accept all. Then check the category under Omea Consent › Scripts – the Category column shows it.

2. The script is switched off

Check the Enabled switch in the Scripts table. A disabled script is kept but never printed.

3. It’s in the Body location and your theme lacks wp_body_open

Body scripts are printed through WordPress’s wp_body_open hook. Most current themes call it; some older ones don’t. If a Body script never appears in the page source, switch it to Head or Footer.

4. The snippet is incomplete

Paste the vendor’s whole snippet as Inline code, including the <script> tags. For an external file, choose External URL and paste only the address. Check the browser Console for errors from the snippet itself – a typo there stops it after consent too.

5. Auto-blocking is holding something it depends on

If the script loads but its tracking calls fail, auto-blocking may be holding a request or a cookie it needs. A library that your script loads from another address can be held even when the script itself runs. Turn on Log blocked writes for debugging under Settings › Advanced, reproduce the problem, and look at Settings › Maintenance › Debug events. See auto-blocking rules.

6. You’re on an old version

Older versions had bugs here – for example, before 1.0.0 an inline snippet that was HTML without a <script> tag (like a GTM <noscript> iframe) caused a JavaScript error after consent. Update under Plugins.

How to see what’s happening

View the page source and search for your script’s name or URL:

  • Before consent, a managed script has type="text/plain" and a data-cmp-category attribute – that’s the inert, waiting state.
  • After you accept, the browser’s Elements panel shows a live copy of the script. If it doesn’t, the category hasn’t been granted.

For Google tags, also read How to check Google Consent Mode v2 is working – they can be loaded but sending cookieless pings, which is correct before consent.