Templates and Geolocation Rules FAQ

You can retrieve the HTML or CSS code by executing Optanon.getHTML() or Optanon.getCSS(), respectively.

We use Cloudflare, which is leveraged to perform a reverse IP lookup that will return the general location of the user (approximately at the city level). The location is not stored and is only used to determine the applicable rule.

For more information, see Cloudflare Support.

Yes, we use the full IP address of the site visitor. Cloudflare is GDPR and CCPA compliant.

For more information, see Cloudflare GDPR and CCPA.

The consent cookie is stored with the location they are in when consent is given. Therefore, the consent model for the location they were in when they consented will be applied as long as the consent cookie is active. To trigger a re-prompt for consent, the user would have to clear their cookies or the consent cookie would have to expire.

Built-in/default categories cannot be disabled or removed from the Preference Center. However, if you do not require a category to display on the Preference Center, make sure there are no cookies in the Categorizations tab assigned to that category. Custom categories can be deleted after recategorizing any cookie mapped to a custom category to a different category.

You are required to enable the Enable persistent Cookie Settings hover button setting for the icon to show up after Banner interaction. For more information, see Customizing the Preference Center Template.

Yes, it is a Preference Center setting that is available for all the frameworks.

For more information, see Customizing the Preference Center Template.

Templates are not assigned to a domain. A template is assigned to a geolocation rule group, which in turn is assigned to a domain.

You can reassign a template to another organization if you have multiple organizations in your organizational hierarchy. Please note that users assigned to a particular organization will only be able to view items (including domain scans, templates, geolocation rules, etc.) assigned to that organization and any of its child organizations. For details on creating and managing organizations, please refer to Managing Organizations.

A default template means any time a new geolocation rule group is created, the default template will be assigned to this geolocation rule group.

A default geolocation rule group means anytime you add a domain for scanning and do not assign a geolocation rule group manually, the domain will automatically be assigned to the default geolocation rule group.

No, there is no limit on the number of templates you can create.

When you publish the production scripts for a domain, the geolocation rules and templates tied to it automatically change from Draft to Active status.

No, the language codes are not case sensitive.

In the Content section of your Banner template, select Button Set. For the item When using the button in a web page to access the Cookie’s Preference Center, you can select Show other text and enter your desired text. Please note that if you would like to apply this change for all geolocations, you will have to make this change to all the templates you have assigned in your geolocation rule group.

For more information, see Customizing the Banner Template.

You can view the version history of a template by clicking on the Context Menu icon in the header of the Template Details screen and selecting View Version History. For more information, see Customizing the Banner Template or Customizing the Preference Center Template .

For more information, see Configuring Geolocation Rules.

If you would like to modify any of these details, you can navigate to the Cookie Consent menu and select Purposes. Here, you can select the appropriate category and edit the details. These changes will display in your templates.

For more information, see Configuring Purposes.

Yes, you can assign multiple domains to the same geolocation rule by clicking the Assign to Domains button on the Assigned Domains tab of the Geolocation Rule Group Details screen. All assigned domains will appear in the Assigned Domains tab.

For more information, see Configuring Geolocation Rules.

The cookie list provides users with updated information on cookies, which is required by law for certain regulations.

Yes, it's common practice to display a cookie list to users. Please consult with your legal team for specific requirements.

Currently, OneTrust does not support the use of variables to dynamically modify cookie banner content based on the domain or location. Instead, OneTrust applies branding configurations (such as the cookie policy link, logo, and color scheme) at the domain level. These settings override the original template configurations according to the geolocation rule. To meet the need for domain-specific content, you can create separate templates for each domain or brand. Assign each template to its corresponding geolocation rule group. This approach allows each domain to display a uniquely customized cookie consent banner with brand-specific links and styling.

For more information, see Configuring Domain Branding.

The CMP suppresses the Require banner interaction overlay (grey background) when the current page URL matches a URL configured within the banner or preference center content.

The CMP evaluates URLs configured in the following locations:

• Cookie policy link template field

• Imprint link template field

• Custom anchor (<a>) tags added to the Title and description field

When a user navigates to a configured disclosure URL, the CMP suppresses the require banner interaction overlay to ensure the content remains accessible. URLs configured within banner or preference center content are typically intended to direct users to privacy-related disclosures and legal notices, such as Privacy Policies, Cookie Policies, Terms of Use, or similar notices. End users must be able to access and review this transparency and disclosure information before making a consent decision. Providing access to these resources prior to consent supports informed consent practices and improves transparency.