Skip to main content
Use Plainrouter’s consent management platform (CMP) to give visitors a choice, apply their decisions to supported browser tags, and inspect the choices your banner records. Bring together banner controls, saved preferences, consent receipts and cookie declarations in one workspace. You can use the included Plainrouter banner or connect a supported external CMP. Setup uses the workspace’s generated browser snippet; the banner controls are currently under Signals → Install → Consent banner. A Meta ad account connection is needed only for workflows that use Meta, such as advertising delivery.

Set up the banner

Enable the included consent card, configure reopening and choose coverage.

Read choices and receipts

Inspect recorded decisions by location, language and policy, or export receipts.

Scan cookies and publish a declaration

Review observed cookie and storage metadata, freshness and consent-phase coverage.

Connect an existing CMP

Pass supported consent signals and verify changes, rejection and withdrawal.

​
What does the CMP include?

The included banner’s Marketing choice maps to ad_storage, ad_user_data and ad_personalization; Analytics maps to analytics_storage. On the consent-based advertising path, all three advertising permissions must be granted. Missing or unknown choices stay unknown. Follow the consent-state reference when connecting your own interface.

​
How do I get started?

  1. Create the intended workspace and complete the shared browser installation. Use its generated key, collection domain and complete snippet once.
  2. Open Signals → Install → Consent banner to enable the included card and choose whether to show the floating reopen control. The workspace owner manages banner coverage separately.
  3. Copy the complete current installation and consent instructions. Follow the supplied Google and UET tag controls; the banner cannot configure unrelated CMS plugins or tag-manager triggers for you.
  4. Test acceptance, rejection, partial choices, returning saved choices and withdrawal with the browser verification guide.
  5. Read the recorded consent choices, then scan the website and publish its declaration.
For a same-origin installation, the enabled banner appears for all visitors because that serving path cannot pass visitor location. Off still disables the Plainrouter surface. Verify the installed page after changing coverage; saving a workspace setting cannot rewrite an older pasted snippet.

​
Can I keep my existing CMP?

Yes, when you connect its decisions through a supported signal or explicit adapter. The snippet checks explicit consent, TCF and Consent Mode inputs before using its fallback card. A detected supported CMP without a usable decision suppresses that fallback and leaves advertising consent unresolved. A later valid external decision dismisses the Plainrouter card. Use the external-CMP integration guide. If you turn the included banner off, follow the Off migration steps so your CMP owns defaults, saved choices, updates and withdrawal. External CMP records remain separate from receipts generated by the Plainrouter card.

​
How do I check the result?

Verify the visitor interface and the resulting requests separately. A visible card establishes that the interface loaded; inspect the recorded choice and subsequent browser behavior to check that the decision reached the integration. Withdrawal stops consent-dependent work, while requests already received by a destination cannot be recalled. Use Consent choices for recorded decisions and exportable receipt metadata. Use Cookie scan and declaration for observations about the pages the scanner visited. Read each host’s freshness and phase coverage; incomplete or unknown scans keep their limits visible.