Sample only — fictional BrightPath Academy. Not a live customer site. Back to ConsentSignals

What other sites actually ship

Two artefacts, two jobs. The cookie banner gets a small evidence chip (independent check, not a CMP). The DPO / board gets the HMAC-signed PDF. ConsentSignals does not install or replace the banner.

1. On the website — cookie banner

BrightPath Academy Courses · About · Contact

Welcome back, learners

A normal marketing homepage. The CMP still owns Accept / Reject. ConsentSignals only adds the dark chip so anyone can open the public evidence page.

2. The signed PDF — DPO / board pack

17 Jun 2026, 14:32 UTC · 8 isolated sessions · HMAC-SHA-256

Consent verification report

https://www.brightpath-academy.demo

6Domains still fire under Reject
FailConsent Mode v2 observed
P1Gate ads tags behind CMP
PDFTamper-evident, public /verify
doubleclick.net googlesyndication.com facebook.net

This is what you email counsel or attach to a ticket. It is not placed inside the cookie banner. Anyone can check the file was not edited at /verify.

Open sample PDF On-screen report sample

3. How a site like dryspell.ie implements this

  1. Keep your CMP. Cookiebot / OneTrust / custom banner still collects the choice. ConsentSignals does not show Accept/Reject for you.
  2. Scan the live URL on ConsentSignals (e.g. https://dryspell.ie). Download the signed PDF for your records.
  3. Verify DNS for that domain in the Dashboard so the public chip is allowed.
  4. Paste one script in the CMP “additional HTML” field, or just above the banner markup. Until consentsignals.com is in production, the live chip will not load — use the PDF in the meantime.
<!-- Independent evidence chip — does not replace your CMP -->
<script
  src="https://consentsignals.com/trust/consentsignals-trust.js"
  data-domain="dryspell.ie"
  data-api="https://api.consentsignals.com"
  data-app="https://consentsignals.com"
  data-target="#cookie-banner"
  defer
></script>

data-target should match an element on your banner (here #cookie-banner). If omitted, the script tries to attach to a Cookiebot-style dialog, then any element whose id/class contains “cookie”. The chip links to the public verify page — not to a “compliant” claim.