Consent analytics that help teams make decisions

What should consent analytics tell you?

Consent analytics are worth your time when they answer questions you'd act on. Which categories do visitors reject, and how often? Did last month's copy change move anything? When the scanner found a new marketing cookie, did the consent picture change with it? Total banner views can't answer any of these.

A good test for any consent report, including ours, is whether a number leads to a decision, such as rewriting the copy, reviewing a vendor, rescanning the site, or checking whether a script is firing before it should.

Per-event records make the answers possible

Totals can't answer those questions on their own, so UserGuard records consent as individual events. Each one has the site, the banner version, the region, the language, any Global Privacy Control signal, the per-category choices, hashed visitor and IP identifiers, and a timestamp. The log is append-only, so nobody can tidy it up after the fact.

You get the useful breakdowns by slicing those fields, such as choices by region or behavior before and after a banner change. The Consent tab shows which categories visitors allow, and each record and the CSV keep the choice for each category, so you can also work out a rejection rate by category from the export. The same records also serve as evidence when someone asks what one visitor chose on one afternoon, which is the question enforcement asks.

Version stamps tie choices to a banner

When you publish a banner in UserGuard, that version is saved and can't be changed, and every consent event records the version that produced it. So you can answer before-and-after questions from the data. You can put a shift in choices next to the exact banner that caused it, and say which design a given visitor saw.

The enforcement record has one warning for you. When acceptance jumps after a redesign and nobody can explain why, it's usually because rejecting got harder to find. Equal-prominence expectations exist to catch that pattern, and you'd much rather find it in your own version comparison than have a regulator find it in theirs.

Export the numbers as CSV

If you can only view your records inside a tool, you don't fully control them. UserGuard exports the consent log as CSV, so a lawyer, an auditor, a client, or a spreadsheet can work with it directly. Retention defaults to 400 days, and you can adjust it up to three years to match your own policy.

If you report to clients, you can use the same export to work out how many visitors accepted optional categories, what was rejected where, and what changed after the work you billed for. A non-technical client will get more from numbers they can read than from a screenshot of a dashboard.

What should you check each month?

Once a month, export the log and ask three questions. Did rejection rates move, and does the banner version history explain it? Did the latest scan add anything the banner and policy now need to cover? Is anything in the numbers surprising enough that you can't explain it in a sentence?

If a number moved and you don't know why, find out before someone outside your company does. The whole check takes about fifteen minutes.

Go deeper: consent analytics in UserGuard