Consent not recorded
If a visitor accepted or rejected on your banner but the action isn't showing up in the Consent Audit, check the following.
1. Wait a moment
Consent events are recorded almost in real time, but it can take a few seconds for a record to appear in the dashboard. Refresh the audit page and look again.
2. Confirm the banner is the live version
Make sure the website you tested on uses the Production snippet, not the Test snippet. Records from Test events do not appear in the Live audit.
If you tested on a staging site with the Test snippet, those records appear in the Test audit (not the production one).
See Getting your script.
3. Look up the right user ID
Audit search is keyed by User ID. The visitor's User ID is set in their cookie. To find it on your own browser:
Open Developer Tools (F12), then Application → Cookies → your domain.
Look for onePrivacyConsent. The cookie value contains the User ID and the chosen categories.
Use that User ID in the Consent Audit search box.
If you searched a different User ID, no records will show up even though the consent was recorded correctly.
4. Check cookies are not blocked
One Privacy stores the User ID in a cookie. If your visitor's browser blocks cookies (strict privacy mode, ad blocker, third-party cookie restriction), the consent can't be tied to a stable User ID and may not appear under a single ID across visits.
Test in a normal browser session first.
5. Confirm the banner script loaded
Open your website with Developer Tools open. In the Network tab, search for oneprivacy. You should see at least one request to One Privacy's servers.
If there's no network request to One Privacy when consent is given, the recording call isn't reaching us. Make sure the snippet is in the page (see Banner not appearing) and that an ad blocker isn't blocking it.
6. The visitor is offline or behind a firewall
If your visitor was on a corporate network or VPN that blocks third-party requests, the consent record may not have reached One Privacy. There's nothing you can do for past visits, but you can check whether your environment has restrictions.
7. Wide date range search
If you've narrowed your search by date, widen it. Records may be slightly outside the range you expected (timezone differences, server timestamps).