Activity & Insights
Monitor consent rates, review audit-ready consent logs, and manage detected third-party scripts.
ConsentStack gives you three tools to understand and prove your compliance: an analytics dashboard for trends, consent logs for audit-ready records, and tracker detection for managing third-party scripts.
Consent Analytics
The analytics dashboard shows you how visitors are responding to your consent banner at a glance.
KPI Cards
Four key metrics sit at the top of the page:
- Total Events -- the number of consent interactions during the selected period.
- Consent Rate -- the percentage of visitors who opted in (accepted all categories).
- Time to Action -- the average time between seeing the banner and making a decision.
- Bounce Rate -- the percentage of visitors who left without interacting with the banner at all.
Each card shows a delta indicator when comparison mode is on, so you can see whether a metric is trending up or down versus the prior period.
Trend Chart
Below the KPIs, a trend chart plots your selected metric over time. Use the time range selector to view the last 24 hours, 7 days, 30 days, or 90 days.
Turn on comparison mode to overlay the current period against the previous one -- helpful for spotting the impact of banner changes or seasonal shifts.
Breakdown Charts
Two breakdown panels round out the dashboard:
- Devices -- consent events split by desktop, mobile, and tablet.
- Top Countries -- consent events by visitor country, with the applicable regulation and per-country consent rate shown inline.
Export
Click Export CSV to download the current dataset. Useful for sharing with legal or plugging into your own reporting tools.
Analytics is available on Pro plans and above.
Consent Logs
Every consent decision a visitor makes is recorded as an individual log entry. Logs are your proof of consent -- the record you hand to an auditor or regulator when they ask, "Can you prove this visitor consented?"
What Gets Logged
Each entry captures:
| Field | Description |
|---|---|
| Timestamp | Exact date and time of the decision |
| Visitor ID | A cryptographically hashed identifier -- no personal data is stored |
| Action | Opt In, Opt Out, Partial Consent, or Acknowledged |
| Categories | Which consent categories the visitor accepted or rejected |
| Device | Device type, browser, and operating system |
| Country & Region | Where the visitor was located, plus the regulation that applied |
| Page URL | The page the visitor was on when they interacted with the banner |
Browsing and Inspecting Logs
Logs appear in a paginated table sorted by most recent. Click any row to open the inspector panel on the right, which shows the full detail of that consent event -- including the interaction timeline (banner shown, preferences opened, decision made) and metadata like SDK version and banner position.
Privacy by Design
Visitor IDs are cryptographically hashed before they are stored. No names, emails, IP addresses, or other personally identifiable information ever touches your logs. This means your consent records are audit-ready without creating a privacy liability.
Data retention varies by plan. Check your plan details for how long logs are kept.
Tracker Detection
ConsentStack automatically detects third-party scripts running on your site and reports them back to the dashboard. This gives you a clear picture of what is loading on your pages -- and whether those scripts are properly gated behind consent.
How It Works
The SDK monitors your site for third-party scripts and reports their domains to the dashboard. Those domains are matched against a database of 5,800+ known tracker domains and auto-categorized (e.g., Analytics, Advertising, Social Media). Recognized scripts show the vendor name, logo, and a link to the vendor's site.
Scripts that don't match a known domain are flagged as uncategorized and surfaced at the top of the page for your review. You can assign a consent category to any script with a single click.
Triggering a Scan
Trackers appear automatically as visitors browse your site. If you want results immediately -- for example, after launching or connecting a new domain -- click the Sync button to trigger a fresh scan on demand.
Custom Rules
For scripts that aren't auto-detected, you can add custom domain pattern rules to manually assign a consent category. This is useful for internal tools or niche vendors that aren't in the known tracker database yet.
What's Next
- Categories & Regions -- learn how consent categories and regional rules connect to tracker blocking.
- Script Blocking -- understand how ConsentStack prevents scripts from running before consent is given.