Consent management (CMP)

Choose the consent method

Configure the site in your CMP account using the domain visitors will open, including an active custom domain. In OrbitPage, open Privacy → Consent banner, enable consent management and select the external provider option. Choose the provider and enter the field described below, then Save.

Use Privacy → Documents for the privacy and cookie policies. A policy link or policy embed is separate from the consent banner installation. CMP plans, languages and regional rules are configured with the provider; OrbitPage does not create the provider account.

iubenda

In iubenda, open Manage and Embed for your site and copy the complete Privacy Controls and Cookie Solution installation snippet. Select iubenda in OrbitPage and paste it into the installation snippet field. Keep the complete configuration and loader together; a privacy-policy link alone does not install the banner.

Save and test the public page. OrbitPage maps iubenda purposes 2 or 3 to Preferences, 4 to Analytics and 5 to Marketing.

CookieYes

Open the website's installation code in CookieYes. Find the identifier between /client_data/ and /script.js in the script URL. Select CookieYes in OrbitPage and paste only that identifier into CookieYes script ID, then Save.

OrbitPage loads the CookieYes script and maps functional to Preferences, analytics to Analytics and advertisement to Marketing.

Cookiebot

Copy the data-cbid value from the Cookiebot installation code for your domain group. Select Cookiebot in OrbitPage and paste that value into Cookiebot CBID, then Save. This is the public installation identifier, not a Cookiebot API key.

OrbitPage loads Cookiebot with automatic blocking enabled. It maps preferences to Preferences, statistics to Analytics and marketing to Marketing.

OneTrust

Publish the banner configuration in OneTrust and copy the data-domain-script value from its installation code. Select OneTrust in OrbitPage and paste it into OneTrust domain script ID. Use the production identifier for a public production page.

The preset loads the standard cdn.cookielaw.org SDK and maps C0003 to Preferences, C0002 to Analytics and C0004 to Marketing. If your installation uses different category IDs or a different SDK host, use a custom integration with an explicit consent bridge instead.

Custom installation

Choose Custom only when you have a trusted installation snippet and a developer can connect its consent changes to OrbitPage. Paste the snippet into CMP script. The banner appearing is not enough: its accepted and withdrawn categories must also reach OrbitPage's consent bridge.

Custom integrations can dispatch the orbitpage-consent-update event with preferences, analytics and marketing booleans after each choice. Use Reopen selector when the provider needs a specific control to open preferences again. Test rejection, acceptance and withdrawal before using the page.

Check the public page

Open the saved public page in a private window, with no earlier consent. Repeat the check on the OrbitPage address and custom domain if both are used.

1. Check that one banner appears and both policy links work.
2. Reject optional categories and confirm that the corresponding embeds remain blocked.
3. Accept only Preferences, then Analytics or Marketing separately; check the matching blocks and tags.
4. Reopen preferences, withdraw consent and reload to check that the choice persists.

• If the banner is missing, check the installed identifier or snippet, published provider configuration, domain and regional display rules.
• If there are two banners, remove the duplicate installation from custom scripts or a tag manager.
• If choices do not affect embeds, check the category mapping and each block's Consent category. Avoid installing GA4 both in OrbitPage and through another script.