Excluded Routes
Understand what path exclusions suppress—and what they do not.
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.
Configure path exclusions deliberately
Use the excluded-path controls in Banner Design. Match actual site routes using the formats accepted by the editor. Test both initial requests and client-side navigation.
Suppressed behaviour
Excluded routes suppress automatic banner UI, the floating revisit control and banner analytics. They are not a universal firewall for other scripts, nor a statement that a page is exempt from privacy requirements.
Explicit preferences action
A visitor's tested data-consentease-preferences control or showPreferences() call can still open preferences on an excluded route once the runtime is loaded. It does not automatically accept or reset anything.
Check coverage
Verify language-prefix routes, query strings, nested paths and important checkout/account pages against the current path matching. Do not copy arbitrary wildcard syntax from another tool. Ensure withdrawal is reachable wherever required.
An intentional exclusion can explain missing analytics. Document it before diagnosing missing events as an installation failure.