Public Banner JavaScript Contract
Use the supported preferences entrypoint, not internal runtime functions.
Content and code last checked 2026-10-06 by ConsentEase product documentation. This is a review of the written content and code, not a test on a live third-party platform.
Supported public surface
The browser embed uses a public website ID, not a Connect API key. Add native links/buttons with data-consentease-preferences or call window.ConsentEase.showPreferences() after the runtime is available.
Loading boundary
There is no pre-load command queue. Guard JavaScript availability or use a native fallback link. Repeated calls focus the existing preferences panel; opening it alone does not alter consent.
Do not rely on internals
Internal variables, DOM classes, storage keys and helper functions are not a stable public customisation API. Do not use showBanner(), reset consent, scrape visitor IDs or invoke internal proof writers as a shortcut.
Integration constraints
Configure tag consent through supported Google/platform APIs and verify their actual state. Missing inventory presents Retry without guessing categories or changing choices. Preview mode is for design and must not be treated as a real visitor decision.
Server integrations
Use REST with server-held keys for authorised record/report integrations. Keep API-key and visitor-consent boundaries intact; MCP deliberately cannot write visitor consent.
See the preferences guide for complete HTML and JavaScript examples, accessibility and excluded-route behaviour.