/ Docs
Consent Management

Consent Logs and Reporting

Last updated August 27, 2026 · View as Markdown

Audience: admins, compliance teams, auditors.

What gets captured

When consent logging is enabled for a domain (see the Admin Configuration Guide), every consent decision a visitor makes is recorded as a structured event:

Field Description
Record ID Unique identifier for the consent record
Device ID Randomly generated device identifier
Device Name e.g., "Mac," "Android"
User ID Populated for authenticated visitors (see the Technical Implementation Guide); blank for anonymous ones
GPC Status Whether a Global Privacy Control signal was detected
Timestamp Time of the consent event, down to the millisecond in the detail view
Agent Version Version of the Consent Agent script that recorded the event
Domain The domain/property the event occurred on
Region The resolved jurisdiction/Region Group that applied
Source IP Visitor's IP address (subject to the anonymization setting below)
Purposes Per-purpose accept/reject breakdown, e.g. {"Strictly Necessary": "Accepted", "Analytics": "Accepted", "Marketing": "Declined"}
Accepted All / Rejected All Boolean shortcuts for bulk actions
User Agent Full browser user-agent string (subject to the minimization setting below)

This level of detail - a per-purpose breakdown rather than just an "accepted" flag - is what makes the log usable as compliance evidence: it shows exactly what a visitor was asked, and exactly what they chose, at a specific point in time.

Enabling logging

Toggle Store records of consent (a.k.a. Enable Consent Logging) on the domain's Behaviors tab, per Region Group. Two optional data-minimization settings are available under Advanced Storage Settings:

  • Anonymize IP addresses - removes the last octet before storage.
  • Store browser type only - stores a normalized browser identifier instead of the full user-agent string.

We recommend enabling both unless you have a specific reason to retain full precision - see the Legal and Compliance Guide for the compliance rationale.

Viewing logs

Grid view (Manage → Consent Logs, also labeled Records of Consent in some platform views): Device ID, Domain, Region Group, Purposes, and Timestamp columns, filterable and searchable.

Detail view (click any row): the full field set above, plus - for authenticated consent records - a Consent History tab showing every prior consent decision tied to that user across all their devices (or, for anonymous records, history scoped to that device).

Exporting logs

Open the Consent Logs page → click Export → in the dialog, choose:

  1. Domain - single-select; one domain or app per export.
  2. Date range - preset options (Last week, Last 15 days, Last 30 days) or a custom start/end date.
  3. Format - CSV or XLSX.

Click Export. The job runs in the background with a progress indicator and continues even if you navigate away; a Download link appears when it's ready.

Limits to plan around:

  • Maximum date range per export: 32 days (covers any single calendar month).
  • Download links expire 30 days after the export completes.
  • Exports are single-domain - you can't batch multiple domains into one export.
  • For a full year of data, run up to 12 separate monthly exports.

Choosing a format: CSV is generally best for scripted ingestion into a GRC tool or BI pipeline; XLSX is more convenient for sharing directly with auditors or non-technical stakeholders.

Exported columns: Record ID, Device ID, Device Name, User ID, GPC Status, Timestamp, Agent Version, Region, Source IP, Domain, Purposes (pipe-joined), Accepted All, Rejected All, User Agent.

Access requirements

Viewing Consent Logs and using Export requires the Consent Settings viewing permission on your Relyance role. If the Export button or Consent Logs page isn't visible, that's the first thing to check with your Relyance admin.

Using logs for compliance

Consent logs are the primary evidence base for:

  • Regulator inquiries - demonstrating that a specific visitor (or class of visitors) was shown the correct notice and that their choice was honored.
  • Audits - exporting a defined period for internal or external audit review.
  • DSARs - locating an individual's consent history (especially straightforward for authenticated visitors via the Consent History view).
  • GRC/BI reporting - CSV exports feeding into broader compliance dashboards or reporting pipelines.
← Previous
Admin Configuration Guide