What is server-side measurement?
Server-side measurement routes events through a server the business controls. That server can validate an event, remove fields, check consent, and send the permitted data to selected analytics or advertising destinations.
For a website interaction, a browser script may still detect the action and send it to a first-party collection endpoint. For a backend outcome, such as an order being paid, the order service can send the event directly. The server then handles each event according to its source and purpose.
Why use it?
- Control: Validate names, values, and identifiers before data leaves the pipeline.
- Routing: Send one permitted event to the destinations that need it.
- Consistency: Use shared rules for web, app, and backend events.
- Maintenance: Change some destination mappings without editing every website or app client.
This setup does not recover a browser action that was never captured. It also does not remove consent duties or make identifiers anonymous. Test the full path, from collection through destination receipt, and use a shared event ID when both browser and server report the same action.
For architecture and implementation choices, read the server-side tracking guide. For direct backend exchange, see server-to-server.
How Hardal handles it
Hardal runs the server layer for you on your own first-party subdomain, hosted in the US, UK, EU, EMEA or Asia, and delivers events to GA4, Meta, TikTok and other destinations.
Related terms: Server-to-server, Event deduplication, First-party data, Data discrepancy