Consent Records
Hosted mode stores consent activity in the backend so teams can inspect what happened after a visitor interacts with a banner or dialog.
What a record shows
Consent records can include:
- subject ID
- external ID when supplied by the app
- policy
- captured purposes or categories
- user action
- capture time
- country and region
- language
Use records to debug integration issues, confirm that policies are being resolved as expected, and inspect the consent state associated with a subject.
Search and filter
Use search and pagination when reviewing large sets of records. Start with the subject or external ID when you are investigating one user. Filter by policy or date range when you are validating a rollout.
Overview analytics
The consent overview helps you understand aggregate behavior:
- total consent volume
- accept, customize, and reject split
- consent rates by policy
- changes over a selected date range
Analytics are operational signals, not legal conclusions. Use them to spot implementation issues, policy changes, or unexpected changes in consent behavior.
Common checks
After shipping a new consent integration:
- Save each banner action in a test browser.
- Confirm the expected consent records appear.
- Check that the resolved policy matches the test region.
- Verify category values line up with script behavior.
- Reopen privacy settings, change preferences, and confirm the new record state.