GTG, consent, and late default
If you are investigating a "Default consent not sent on time" alert, this guide explains:
- How Google Tag Gateway (GTG) may relate to the issue.
- Why a late default may occur.
- Which solutions to apply based on your setup.
When a late default occurs, one or more Google tags check the consent state before default consent has been set correctly.
This can affect:
- Google Consent Mode compliance.
- Conversion and event measurement.
- Audiences, remarketing, and other Google Ads features.
- The quality of the data reported in Google Analytics.
Check whether your site uses Google Tag Gateway (GTG), as the recommendations may vary depending on how Google tags are loaded.
Google Tag Gateway, consent, and late default
Google Tag Gateway does not modify users' consent choices or change how Google Consent Mode works. However, it can make an existing load-order issue more visible.
When GTG is enabled through certain CDN integrations or automatic setups, Google tags may load before Lawwwing has set the default consent values. If this happens, Google may detect that the consent state was not available when the tag first ran, creating a late default situation.
Google Tag Gateway is not usually the direct cause of the problem. Most often, it reveals or amplifies a pre-existing issue related to script load order.
For this reason, if you notice consent issues after enabling GTG, it is worth checking whether Google tags are running before Lawwwing.
How to identify a possible late default issue
Lawwwing automatically detects this issue and alerts you when it happens. Detection is performed through the diagnostic tool and dashboard alerts, allowing you to quickly identify issues related to load order and consent.
If Lawwwing detects this situation, it will display an alert similar to the following:
🔴 Default consent not sent on time
The presence of this alert indicates that one or more Google tags ran before default consent was properly established.
You can review the incident details, its impact, and the recommended solutions in:
If the alert appears after enabling Google Tag Gateway, it is also recommended to verify whether GTG has changed the tag load order and review the steps described in this guide.
What to do when a late default is detected
The solution mainly depends on whether you are using Google Tag Gateway (GTG) or not.
Case 1: There is a late default and Google Tag Gateway is active
If GTG is active, the load order of tags may be influenced by how GTG has been deployed on your site.
Before making changes, verify that GTG is actually active by following the guide.
Once confirmed, you can choose one of the following solutions.
Option A: Manage all tags in a Google Tag Manager container
If you currently use Google tags inserted directly on the page, consider migrating them to a Google Tag Manager container.
Move all Google tags into a GTM container and configure consent through Consent Initialization. This allows Lawwwing to set default consent before Google tags run.
In this scenario:
- Lawwwing must be configured according to the GTM installation guide.
- Lawwwing's trigger must be Consent Initialization - All pages.
- GTG must be applied to the GTM container, not to individual tags.
You can follow Google's guide to configure GTG correctly with a GTM container.
Option B: Use Advanced Google Consent Mode
This is usually the simplest and most compatible alternative in environments where it is not possible to guarantee that consent is set before tags load.
With Advanced Consent Mode, Google tags can initially load in cookieless mode and update their behavior when the user makes a consent choice.
It is also recommended to review:
- Data Transmission Controls
- Global Consent Defaults, managed by Lawwwing.
- Your general Google Consent Mode configuration
Option C: Configure GTG manually
If you need more precise control over load order, you can implement GTG manually and explicitly define when scripts load.
Manually configure GTG's "origin" and "path" instead of using one-click injection, so that Google tags are served from your own domain and load after Lawwwing has set default consent.
This option usually requires advanced technical knowledge and full deployment validation.
Case 2: There is a late default and Google Tag Gateway is not active
If GTG is not active, the problem is usually caused by Google tags running before default consent is set.
Option A: Fix the load order
Verify that Lawwwing initializes before any Google tag.
The recommended order is:
- Lawwwing script, which sets the default consent
- Google Tag Manager, Google Analytics, Google Ads, and so on
Option B: Use wait_for_update
If you cannot guarantee the correct load order, Google allows you to temporarily delay tag execution using wait_for_update.
gtag('consent', 'default', {
wait_for_update: 500,
...
});
You can adjust the waiting time based on your needs, but keep in mind that a value that is too high can affect the user experience.
Follow the Google Consent Mode implementation guide for more details.
Verify that the problem has been resolved
After applying any changes:
- Run the Lawwwing diagnostic tool again.
- Confirm that the "Default consent not sent on time" alert no longer appears.
- Validate in Google Tag Assistant that consent states are set before Google tags run.
Quick decision table
| Google Tag Gateway | Situation | Recommendation |
|---|---|---|
| Active | You manage tags with GTM | Configure Consent Initialization correctly |
| Active | You cannot easily control load order | Use Advanced Consent Mode |
| Active | You need full control | Implement GTG manually |
| Not active | - | Fix the script load order |
| Not active | You cannot easily fix the order | Evaluate using wait_for_update |
If you need help validating your setup, feel free to contact us through any of our support channels.