What do you mean by “request” or "hit"?

Cost Optimization and Server-Side Hit Management

Adopting Server-Side tracking transforms your data collection architecture. Unlike classic client-side tracking, Server-Side acts as a proxy infrastructure that secures your data and scripts.

This infrastructure generates server requests (or "Hits") that go beyond simple Analytics "page views." This document details the cost structure and the new optimization levers available to balance maximum robustness and budget control.

---

1. Understanding the Structure of a Server-Side "Hit"

A common misconception is thinking that 1 Page View = 1 Hit. In a robust Server-Side configuration (with Adblocker bypassing and script security), this ratio is actually closer to 1 Page View = 10 to 15 Hits if all options are active.

Why? The server doesn't just receive data (collection); it also delivers resources (scripts) to guarantee their loading.

Cost Table by Feature

Feature	Description	Cost Impact
Loader Loading	Initializes the secure environment on your subdomain.	1 Hit / page
CMP Proxy	Downloads the Consent script (e.g., Sirdata) via the server to avoid blocking.	1 Hit / page
GTM / GA4 Proxy	Downloads Google libraries (gtm.js, gtag.js) via the server.	1 Hit / script
Service Workers	Optional. Google technical calls to improve network reliability.	Variable (Medium)
Set Cookies	Optional. Technical route to set/extend cookies.	Variable (High)
Collection (Pings)	Sending the actual data (Page View, Add to Cart...).	1 Hit / event

Note: Loading scripts (CMP, GTM) via the server is essential for Unblocking (bypassing ad blockers). This is a necessary infrastructure cost to recover 10% to 20% additional data.

---

2. Google Script Optimization Options

To give you more control over your billing, we have introduced options to disable certain autonomous technical calls made by Google. These options are found in the Script Optimization section.

A. Allow Google Service Workers

Google uses background "Service Workers" to improve measurement reliability (notably for GA4 and Google Ads) and handle unstable network scenarios.

• ✅ Enabled (Recommended default): Tracking is more robust. In return, this generates additional technical requests to the container.

• ❌ Disabled: Service Workers are blocked. Tracking is standard, but you save hits.

B. Allow Delayed Cookie Setting

When standard HTTP headers aren't enough, Google may use a specific route (/set_cookie) to set or extend cookies after the initial response.

• ✅ Enabled (Recommended default): Improves cookie persistence and cross-session tracking (especially on Safari/ITP). Generates additional hits.

• ❌ Disabled: This mechanism is blocked. The container is "lighter" in hits, with a potential risk of reduced cookie lifespan.

---

3. Which Strategy to Adopt?

Use this guide to position your cursor between Cost and Performance.

Strategy Profile	Configuration	Pros & Performance	Cons & Cost
E-Commerce / Performance	✅ Workers ✅ Delayed Cookies	• Ultra-robust tracking. • Max cookie persistence. • Optimal attribution (Ads/Meta).	• High hit consumption. • Higher bill.
Media / High Traffic	❌ Workers ❌ Delayed Cookies	• Drastic cost reduction (-30%). • Maintains unblocking & collection.	• Cookie persistence is less effective in the long term (Safari).
Low Cost	⚠️ No sGTM Loader	• Floor cost (1 hit = 1 event).	• No unblocking. • Scripts blocked by Adblockers. • Cookies limited to 7 days.

Our Advice: Start with options enabled. If you need to optimize your budget, disable Service Workers first, then Delayed Cookie Setting.