Cookie Options

How it works

Cookie Options hosts the banner JavaScript and CSS on cookieoptions.com. Your website loads one script. Visitors choose necessary, analytics and marketing cookies. Those choices stay on their browser and can be written to the hashed consent log.

1. Add the website

Create an account, then add the hostname you will embed on, such as example.com. Staff can also add and edit domains.

2. Paste the loader

The public loader URL is always https://cookieoptions.com/assets/loader.js. Add ?v= when hosted assets change. The exact snippet is:

<script src="https://cookieoptions.com/assets/loader.js?v=1.0.1" data-site="example.com" async></script>

Replace example.com with the site you registered, or omit data-site and the loader will use the current hostname. See the embed page for the same tag and the footer link.

3. Open preferences from a footer link

<a href="#" onclick="window.ogConsentManager.openPreferences(); return false;">Cookie settings</a>

window.ogConsentManager and window.coConsentManager are the same object. cookieoptions.com uses that call on this site’s footer.

What the loader requests

  • Banner CSS: /assets/og-consent-manager.css
  • Banner JS: /assets/og-consent-manager.js
  • Site settings: /backend/site-config.php?site=
  • Consent log: POST /backend/log-consent.php

Those paths are resolved from the loader script origin. Do not hardcode a second hostname unless you set data-base on the script tag.

Hashed consent log

Each accept, reject or preference save can be stored against a daily session hash. IP addresses and user agents are hashed. The banner reason is not stored. See Privacy.

Quick Scan

From a site page, staff or the site owner can run Quick Scan. It fetches the HTTPS homepage HTML and looks for known tracker strings. It does not execute JavaScript. Deep Scan (Node and Chrome) is not part of this product on this host.

Not included

There is no regional or country rule. Page tags are not blocked before the banner. Payment is not included.