Cross Domain Support

  • Updated

As of Chrome v.115, Google Chrome no longer supports Cross Site Scripting. Cross domain support will not function on Google Chrome browsers operating on version 115 or newer. If cross domain support is enabled, users will be prompted to provide consent on all listed domains individually.

This is a Premier-only feature.


What is Cross Domain Support

Cross-domain support is enabled by flipping the cross-domain switch in your configuration "Settings."

When enabled, you have the option to add multiple domains into a single configuration's settings. This will allow initial consents to be shared across unrelated domains owned by the same entity. 

Cross-domain support is recommended when the goal is for the initial consent experience to be shared across root domains: (ex. and 

Osano naturally supports sub-domains, so cross-domain support is not necessary to share consent information across sub-domains: (ex. and 

Cross-domain support is not recommended if you have multiple properties with different brand identity or separate privacy and data storage/retention policies. 


Enabling Cross Domain Support

  • Log in as an Admin or a Consent Manager.
  • Navigate to Consent Management.
  • Create or Edit a Consent Manager configuration.
  • In "Settings," flip the switch labeled "Cross-Domain Support" to on (to the right).

Screenshot 2023-01-18 at 9.38.41 AM

  • Once Cross-Domain support is enabled, add your desired domain to the "Domains" field, "tab," and add all additional domains. 

    Screenshot 2023-01-18 at 9.39.07 AM
  • Save and Publish. 

You can now use the same osano.js across multiple root domains. The cookie and script information for all sites will be gathered under that configuration, and initial consents will be shared across each root domain.

Note: Cross-Domain consent is only copied for the user's initial consent. Further consent is isolated to the local domain. Initial consent is only saved on the browser for 30 days. After that, the initial consent will be considered void for future cross-domain sites visited. 

Due to the nature of cross-domain support, some browser restrictions may apply (Ex. Safari's Default Settings or Firefox Default Settings).