---
title: 'Consent-aware measurement | Plainrouter'
description: 'Measurement that keeps declared consent evidence separate from event collection and delivery decisions.'
last_updated: 2026-09-10
---

# Consent-aware measurement

Consent-aware measurement preserves the declared consent basis and applies the relevant processing and delivery rules. Receiving customer data is not evidence of permission to use it.

## Does server-side collection remove consent requirements?

No. Moving an event through a server does not supply a missing consent basis. Plainrouter integrations must preserve the evidence required by the current API contract.

## Can an arrival stand in for consent to deliver a conversion?

No. Arrival counting and conversion delivery have separate rules. The presence of an arrival does not authorize advertising delivery.

## Where should an integration check the contract?

Use the current API schema and the server-side consent guide. Do not infer consent from a customer identifier, a successful request, or a change in transport.

## Related reading

- [How consent works for server-side tracking](/library/server-side-consent)
- [All definitions](/definitions)
- [Signals](/product/signals)
- [Actions](/product/actions)
- [Implementation guides](/library)
- [API documentation](https://plainrouter.com/docs/api/conversions)