React & Vite
Install once in the document shell rather than on each route.
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.
Use the application document shell
For a typical Vite application, put the complete dashboard snippet in index.html, before GTM/Google tags. Do not repeatedly append/remove the loader from route components or effects; development Strict Mode and navigation can expose duplicate initialization.
Client-side routes
Test initial navigation, direct deep links, back/forward and routes added after loading. Verify that preferences controls inserted by later components still work. Excluded-path settings suppress automatic UI/events, not all application scripts.
Preferences in React
<button type="button" data-consentease-preferences>Cookie settings</button>
Leave the floating button enabled until the replacement is visible and tested. The attribute does not prove the script has already loaded or that the button is unobstructed.
Environment and privacy
The banner public ID is not a secret. Keep Connect API keys on your backend, not in VITE_ variables or browser bundles. Configure Content Security Policy without broad bypasses.
Other React frameworks can have different document/SSR hooks; use their supported initialization surface.
Verify the published site
Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.