> For the complete documentation index, see [llms.txt](https://server-side.docs.sirdata.net/sirdata-server-side/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://server-side.docs.sirdata.net/sirdata-server-side/english-1/f.a.q-server-side/pricing/hit-volume.md).

# Hit Volume

## 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 your scripts.

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

***

### 1. Understanding the structure of a Server-Side "Hit"

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

#### Why?

The server does not just receive the data (collection), it also **delivers** the resources (scripts) to guarantee their loading.

#### Cost table by feature

| Request Type           | Role                                                                              | Billing Impact        |
| ---------------------- | --------------------------------------------------------------------------------- | --------------------- |
| **Loader Loading**     | Initializes the secure environment on your subdomain.                             | **1 Hit / page**      |
| **CMP Proxy**          | Downloads the Consent script (e.g. Sirdata) through the server to avoid blocking. | **1 Hit / page**      |
| **GTM / GA4 Proxy**    | Downloads the Google libraries (`gtm.js`, `gtag.js`) through the server.          | **1 Hit / script**    |
| **Service Workers**    | *Optional.* Technical Google calls to make the network more reliable.             | **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**     |

{% hint style="info" %}
**Note:** Loading the scripts (CMP, GTM) through the server is essential for **adblocker bypassing**. It is a necessary infrastructure cost to recover 10 to 20% of additional data.
{% endhint %}

***

### 2. Google Script Optimization Options

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

#### A. Service Workers (Connection reliability)

This is a backup system that helps Google avoid losing data if the user's internet connection drops or is unstable.

* ✅ Enabled: This is the "Safety" option. If the network fails, you do not lose data. (Better for the quality of your stats.)
* ❌ Disabled: This is the "Savings" option. If the network fails, too bad, the data is lost. (Better for reducing your server bill.)

#### B. Deferred cookie setting (Long-term memory)

This is a method to force the browser (especially Safari on iPhone/Mac) to remember your visitors longer, even if it tries to delete your cookies.

* ✅ Enabled: This is the "Persistence" option. You will better recognize a visitor coming back in 10 days. (Essential if you run Google/Facebook ads.)
* ❌ Disabled: This is the "Lightweight" option. Your cookies may be deleted sooner by the browser. (You save server resources.)

<figure><img src="/files/O26b6w9sDmC1sN0FsPBZ" alt=""><figcaption></figcaption></figure>

### 3. Which strategy should you adopt?

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

| Profile                      | Recommended Configuration                                                     | Benefits                                                                           | Drawbacks                                                                                                  |
| ---------------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **E-Commerce / Performance** | <p><strong>Everything Enabled</strong><br>✅ Workers<br>✅ Deferred Cookies</p> | Ultra-robust tracking. Maximum cookie persistence. Optimal attribution (Ads/Meta). | High hit consumption. Higher bill.                                                                         |
| **Media / High Traffic**     | <p><strong>Optimized</strong><br>❌ Workers<br>❌ Deferred Cookies</p>          | Drastic cost reduction (-30%). Adblocker bypassing and collection maintained.      | Less effective cookie persistence over the very long term (Safari).                                        |
| **Low Cost**                 | <p><strong>Minimal</strong><br>No sGTM Loader</p>                             | Floor cost (1 hit = 1 event).                                                      | ⚠️ No adblocker bypassing. Scripts blocked by adblockers. Cookies limited to 7 days. (Enrichment possible) |

{% hint style="success" %}
**Our advice:** Start with the options enabled. If you need to optimize your budget, disable the **Service Workers** first, then the **Deferred cookie setting**.
{% endhint %}