Skip to main content

Verify installation

This is the manual checklist for confirming OptSens works on your site. For the one-click version, run the implementation check first, either as the onboarding Verify step or from the dashboard Integration page. This page covers what to check by hand and what each result should look like.

1. The banner shows on first visit​

  1. Open your site in a private or incognito window, where no consent from a previous visit is stored.
  2. The consent banner should appear on the first page load.

If it does not appear, work through Install troubleshooting.

2. The snippet loads first-party in the head​

  1. Open developer tools and view the page source or the Network tab.
  2. Confirm the OptSens script is in <head> and loads before Google Tag Manager, Google Analytics, the Meta Pixel and other tags.
  3. Confirm there is only one copy of the snippet on the page.

The script must load first-party, not only through Google Tag Manager. Safari Private Browsing blocks googletagmanager.com, and a GTM-only banner never shows there.

3. The global object is available​

In the browser console, type OptSens.version. It returns the script version. OptSens.debug() prints the current consent state and configuration.

  1. In developer tools, open the Application tab and view cookies and storage.
  2. Before you make a choice, only necessary cookies should be present. Analytics and advertising cookies should not be set yet.
  3. Click Accept all in the banner. The previously blocked scripts and cookies should now load.
  1. Reload the page and run OptSens.debug() in the console to confirm the script is ready. Then accept or reject in the banner.
  2. The choice is stored, and the banner does not reappear on later visits until the consent lifetime expires or the visitor withdraws consent.
  3. If you build on top of OptSens, the consent_update event fires with the new state.

If Google Consent Mode v2 is enabled in Frameworks, OptSens sets consent defaults before any Google tag runs and sends an update when the visitor chooses.

  1. In the console, inspect window.dataLayer and confirm a consent default entry from the page load.
  2. Accept cookies and confirm a consent update entry follows.
  3. Run the implementation check from the Integration page. With Consent Mode enabled and the snippet check passing, it reports whether Consent Mode v2 is compliant, partial or missing.

See Consent Mode v2 for the signal mapping.

Verification summary​

CheckExpected result
Private windowBanner shows on first visit
Page sourceSnippet first in <head>, only one copy
ConsoleOptSens.version returns a version
Before consentOnly necessary cookies set
After Accept allBlocked scripts and cookies load
Consent storedBanner does not reappear on later visits
Consent Mode v2Check reports compliant

If any check fails, see Install troubleshooting.