← Back to the glossary
Measurement
Server-side
Server-side collection and forwarding
Server-side means sending events to your own server and letting that server, not the browser, distribute them to each destination. The browser stops talking to every tool and talks to one.
- When it applies
- It fits when many destinations receive the same thing, when the distribution logic is better out of the browser, or when a single point has to control what goes where.
- What it is confused with
- It is not a way around consent, nor a way to recover what browsers block. If the user says no, it is still no. What changes is where the decision is made, not whether it is made.
- Architecture consequence
- The server becomes your own infrastructure: it has to be sized, monitored, and understood when it fails. And consent has to travel with the event all the way to the final destination, or control is lost exactly where it matters.