Troubleshoot late consent

Late consent means that the default consent command is set after Google tags have already fired.

This is usually a timing issue. It can happen in a standard setup, but it can also happen when Google Tag Gateway affects how tags are loaded or how easy script order is to control.

In some setups, this becomes a timing issue, sometimes described as a race condition, where Google tags start before CookieTractor has completed the default consent step.

Start by checking GTG

Before changing script order or moving code around, first verify whether the affected tag or GTM container is using Google Tag Gateway.

If GTG is enabled, the cause may be different from a standard load-order issue. Start with Verify Google Tag Gateway before making changes to your implementation.

Common causes

Late consent is usually caused by one of these situations:

• CookieTractor loads too late on the page
• Google tags load earlier than expected
• GTG changes how the tag or container is delivered
• a managed GTG setup gives you less control over script order
• the implementation mixes multiple loading paths or tag setups

What to check

When investigating late consent, review the following:

• whether the affected tag or GTM container is using GTG
• whether the Google tag or GTM container is loaded through your own domain
• whether CookieTractor loads early enough
• whether the default consent command is set before Google tags fire
• whether your current setup gives you enough control over script order

If you need to inspect how CookieTractor behaves on the page, add ?ct-debug=true to the URL to open CookieTractor Debug Mode.

Then reopen the banner, click Read more about our cookies, and review the Debug section at the bottom of the expanded panel. See CookieTractor Debug Mode for more details.

How to address it

If GTG is enabled, do not assume that the fix is simply to move CookieTractor earlier.

Start by reviewing whether your GTG setup limits control over script order. In that case, the better fix may be to adjust the implementation rather than only moving scripts around.

For GTG-enabled setups, advanced consent mode is usually the recommended approach.

Other common options are:

• use advanced consent mode
• move all Google tags into Google Tag Manager and deploy GTM through GTG
• set up GTG manually so that script order is easier to control

If GTG is not enabled, treat the issue as a standard load-order problem. In most cases, that means checking that CookieTractor is loaded early enough and that Google tags do not fire before the default consent command has been set.

Related information