Core concepts

Proof chain

The proof chain links placement requests, decisions, render events, and visibility/click beacons into an auditable record.

Inputs

Placements establish the request context. Decisions identify selected assets. Beacons record what was rendered and observed.

Idempotency

Beacon IDs should be stable per event. Re-sending the same beacon must not double-count settlement events.

Check the evidence

After integration changes, check that each rendered placement has the expected observation events and that retries do not duplicate them.

Beacon fields and diagnostics →Proof integrity →

Need help with your integration?

Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.

Contact the team