Cookie Consent Hub Advanced FeaturesConsent Audit Log Guide

Consent Audit Log Guide

The Consent Logs page provides a detailed registry of consent events on your website. This is your primary tool for demonstrating compliance with regulations like GDPR and CCPA.

📑 Understanding the Audit Log

Every time a user interacts with your cookie banner, an entry is created in this table. Here is what each column represents:

  • User IP: The IP address of the visitor.
  • Event ID: A unique identifier for the specific consent action.
  • Action:
    • AcceptAll: The user accepted all cookie categories.
    • Reject: The user rejected all non-essential cookies.
    • Update/Custom: The user saved specific preferences.
  • Source: The exact URL where the consent was given.
  • Categories (Necessary, Analytics, etc.): A visual indicator (Check for accepted, X for rejected) of which categories the user consented to.
  • Timestamp: The exact date and time the action occurred.
  • Technical Details: Includes the Browser (User Agent), Platform, and Language to provide a full context for the event.

🔍 Managing Your Logs

1. Search & Filter

Use the search and filter controls to narrow results by event behavior and source context:

  • IP Address: Find all actions taken by a specific user.
  • Event ID: Locate a specific transaction if a user provides their ID for a support request.
  • Source URL: Filter events from a specific page URL.
  • Action type: Filter by Accept All, Reject, or Partial.
  • Analytics status: See only granted or denied analytics consent events.
  • Time window: Quickly focus on the last 7, 30, or 90 days.

2. Export CSV

Export the currently filtered site logs as a CSV file to share with legal or compliance teams.

3. Retention Policy

Consent logs are retained for 90 days. Older entries are automatically removed by background cleanup jobs to keep storage bounded.

4. Pagination

Use pagination to browse available logs within the retention window.

🛡 Why is this important?

Under GDPR, the "burden of proof" is on the website owner. If a regulatory body or a user requests proof that they gave consent, you can use this log to provide:

  • Who gave consent (IP/ID).
  • When they gave it (Timestamp).
  • What they consented to (Specific categories).
  • How they gave it (Action and Source).

TIP

Keep consent logging enabled and retain logs according to your policy so you have a reliable audit trail when needed.

Getting Started - PreviousScript Management Guide
Next - Getting StartedEnd of Getting Started