04 · Performance & loading

Tune loading and execution order for more reliable tracking.

Several options in this section add billable technical requests. Disabling them lowers costs, at the price of a less efficient container.

Load the CMP from the server-side host

Impacts billing

Loads your consent banner from the same subdomain as the container, within the same script as GTM. Better synchronisation and bypass of some blockers.

Technical detail

The CMP is served from the same host as the sGTM container, in the same script as GTM. Bypasses some adblockers and optimises CMP/GTM timing. Generates additional billable requests.

Reorder data layer events

Enabled by default

Moves Google consent events to first position so tags fire in the right order.

Technical detail

Google Consent Mode V2 events are repositioned first, with tag events placed immediately after, for better consistency.

Allow Google's Service Workers

Enabled by default Impacts billing

Lets Google install Service Workers to make GA4 / Google Ads tracking more reliable. Disabling them reduces costs but makes the container less efficient.

Technical detail

Allows Google to load Service Workers (routes /_/service_worker, sw_iframe.html, sw.js). Creates additional billable technical requests. When disabled, the container is less efficient but generates fewer hits.

Allow deferred cookies

Enabled by default Impacts billing

Lets Google write some cookies after the first response, which improves certain tracking flows. Disabling this can reduce costs.

Technical detail

Allows Google to use the /set_cookie route to write cookies after the initial response. Improves some flows but adds billable technical requests.

Going further

• Optimize GTM Web

• Optimization of CMP and GTM loading

• Script loading

• What do you mean by "request" or "hit"?