Reopen Cookie Preferences

Keep withdrawal accessible

The floating privacy button and your own controls are independent. Keep the floating button enabled until your alternative is placed and tested on the real site across relevant pages, mobile and keyboard navigation. ConsentEase does not edit your footer/theme/menu.

Footer link with navigation fallback

<a href="/cookie-policy" data-consentease-preferences>
  Cookie preferences
</a>

Replace /cookie-policy with an existing cookie/privacy page. The URL is only a fallback when JavaScript is unavailable, not a guarantee visitors can change choices there.

Native button

<button type="button" data-consentease-preferences>Cookie settings</button>

Native buttons provide keyboard activation. Multiple controls and controls inserted after client-side navigation are supported. DOM presence does not prove visibility or accessibility.

JavaScript API

window.ConsentEase.showPreferences();

Call showPreferences() only after the embed has loaded. There is no pre-load command queue: a button cannot open the panel before initialization; a link can navigate to its fallback.

Do not use showBanner() or reset stored consent. Opening preferences does not change consent. Repeated calls focus the existing panel. Escape closes it and returns focus. If category metadata cannot load, Retry leaves consent unchanged.

This works with manual embedding and the official GTM template. An explicit visitor action can open preferences on an excluded route; automatic UI, floating controls and analytics remain suppressed there.