Skip to main content
allGood never shows its own cookie banner. Whatever platform your site already uses, such as OneTrust, Cookiebot, Usercentrics, or one you built, stays the one place a visitor’s choice is recorded. This page tells allGood where to read that decision, and what to do with tracking while it waits for an answer.

Prerequisites

  • You can open the Consent Provider settings page.
  • Your site already has a consent banner or platform.
  • A developer or web team can add a short bridging snippet to your site. They write the visitor’s decision to the place allGood reads from.

What the settings control

Consent provider is a label: Not configured, OneTrust, Cookiebot, or Custom. It records which platform you run, for your team and for support. On its own, it does not change any tracking behavior. Signal source is what actually gates tracking. It is the JavaScript value that your website writes the visitor’s decision to. The default is window.__consent. allGood’s tracking tag checks it before sending anything. Your developer writes that value, using the bridging code for your platform in What consent gates. No tracking before opt-in decides what the tag does until a visitor answers.
  • On (the default), the tag holds page views and events. If the visitor says yes, it sends everything it held. If the visitor says no, it discards them. If no answer ever arrives, it gives up after about half a minute.
  • Off, allGood treats every visitor as already consented. Use this only where you have another lawful basis and your privacy counsel has said so.
The Consent Provider settings, with the signal source and the gating behavior

The Consent Provider settings, with the signal source and the gating behavior.

Set it up

2

Set the provider label

Choose the platform you run from the dropdown.
3

Check the signal source

Keep the default, or enter the path your developer writes to. A path such as window.myCmp.state.consent works. A path that contains a function call or an operator does not.
4

Keep No tracking before opt-in on

Leave it on unless your privacy counsel has told you otherwise.
5

Save

Select Save, then wait for the status chip to read Live at the edge.
Your settings are now saved. Tracking is held or sent according to what your developer’s snippet writes. To confirm it, ask your developer to follow Test your setup, which has buttons that grant and deny consent the way a real banner would.

What this does not cover

Two things surprise people, because they do not behave like the tracking above:
  • Form submissions are never held for consent. A submission is something the visitor explicitly did, and it rests on a separate basis from analytics tracking.
  • A tracked email link click still works and still records, the same way a submission does. The click has to go somewhere either way.

Keep evidence of what visitors agreed to

Each consent text version you add is a permanent record. It holds an ID, a label, and the exact wording a visitor saw. Bind a version to a form, and allGood stamps its ID onto every accepted submission. It does this from its own records, not from whatever the page sent. That makes it evidence you can point to later, not just a claim.
Adding a consent text version, with its id, label, version and the exact statement shown

Adding a consent text version, with its id, label, version and the exact statement shown.

The list only grows, and a new version saves immediately. To change your wording, add a new version instead of editing the old one. A submission from six months ago then still points at the exact text its visitor agreed to.
If tracking never seems to fire, a likely cause is that the bridging snippet is not writing the signal. See Web Edge FAQ and Troubleshooting.