Observary launches soon. Want to try it first? Email hello@observary.app to join the beta.

Observary

A consent banner set up from what your website really loads

The banner asks only about what the scan found, holds known trackers back until visitors agree, and keeps a record of every choice. It’s included on every plan.

  • Banner and preferences
  • Blocking until consent
  • Consent log
  • Cookie declaration

Blocking until consent

Scripts and iframes from known trackers are held back until the visitor agrees to their category, then released. Your tags keep working for everyone who says yes.

  • Custom rules for hosts the catalog doesn’t know, with one-click rules suggested from your scan.
  • Google Consent Mode v2: defaults are set before any Google tag and updated on every choice.
  • Manual markup for anything else. It also avoids the one gap automatic blocking has: a tracker written straight into your HTML can be requested by the browser, though never run, before the banner loads.

Manual markup

<script
  type="text/plain"
  data-observary-category="marketing"
  src="https://connect.facebook.net/…">
</script>

The script waits until the visitor accepts marketing, then runs.

Install and verify

One line, first in your <head>. The address never changes once it’s installed, so you never have to touch it again.

  • Step-by-step guides for HTML, WordPress, Shopify, Google Tag Manager, Webflow, Wix, Squarespace and Next.js.
  • “Email to my developer” writes a ready draft with the snippet and the steps.
  • Verify is free and doesn’t use a scan credit. Every failed check comes with its fix.
  • After every scan the install is checked again, and you get an alert if the banner stops working.

What Verify checks

It loads your start page as a new EU visitor and as one who accepts, and confirms that:

  • The snippet is there and belongs to this domain
  • It loads first and isn’t delayed by an optimiser plugin
  • The banner shows
  • Nothing sets cookies before consent
  • Accepting releases trackers
  • Consent Mode comes before Google’s tags
  • No second consent tool is running

For developers

A small API for your own “Cookie settings” links and for code that should wait for consent.

ObservaryConsent.open()Opens the preferences
ObservaryConsent.granted()Checks what the visitor has agreed to
ObservaryConsent.consentId()Returns the visitor’s consent ID
data-observary-openTurns any link or button into a “Cookie settings” link

Events tell your code when a choice is made.

The consent log

Every decision, with the categories, how the visitor chose, the banner and cookie declaration versions they saw, their language, the page and their country. No IP address and no user agent.

  • A visitor’s consent ID, shown in their preferences, finds their records.
  • Kept 12 months on Starter or 36 months on Pro and up, then deleted automatically. Export it as CSV.
What the consent log stores, in detail

A cookie declaration that keeps itself up to date

The cookie table for your privacy page is built from what scans actually saw, not from a list someone typed in. It updates as your site changes.

  • Grouped per category, with a “Your current choice” block and a one-click way to change it.
  • Embed it in your privacy page, or link to the hosted version.
  • Every version is kept with a diff, and each consent record points at the version that visitor could see. Download any version as PDF or CSV.
  • It lists cookies. Cookie purposes are in English.

Start with a scan, end with a banner

The consent banner, blocking and consent log come with every plan. Your first scan sets the banner up.

Get started See pricing