FAQ: Domain Settings and Consent Behavior in Osano Cookie Consent Manager
Q: What does the domain declaration in the settings page of Osano's Cookie Consent Manager control?
A: The domain declared in the settings page determines where user consent is saved, not where the Osano JavaScript runs. The domain you specify will be the location where the user's consent is recorded and saved, allowing it to be recalled later. You can declare ROOT domains or SUB domains in this setting section.
Note: This declaration does not stop the cookie consent banner from appearing on non-declared domains. If the osano.js exists on a page, it will appear on that page though consent will not be saved.
Q: Can I declare subdirectories in the domain section?
A: No, subdirectories (ex. website.com/subdirectory) cannot be used as domain declarations. Osano can support root domains and subdomains only for consent recording.
Q: How does specifying a root domain affect consent saving and recall?
A: If you specify a root domain (e.g., website.com), consent will be saved to that root domain. This setup naturally supports all subdomains, meaning the saved consent will apply across all subdomains and subpages under that root domain, as long as the Osano JavaScript is present on all pages and subdomains.
Ex. If a user goes to website.com and opts OUT of all categories of tracking and then goes to pages.website.com, their consent choices will automatically apply to that subdomain and all subsequent pages.
Q: What happens if I declare a subdomain instead of a root domain?
A: When you declare a subdomain (e.g., page.website.com), consent is saved specifically to that subdomain. This consent will not be recalled on the root domain (e.g., website.com), even if the Osano JavaScript is present on both the subdomain and the root domain. From the end user's perspective, they would see the consent banner again on the root domain, and any consent given on the subdomain would not be applicable to the root domain.
Q: What if I want to share consent across multiple subdomains?
A: This is the default behavior of root domain declaration.
To share consent across multiple subdomains, declare the root domain and apply the same cookie consent configuration and JavaScript across all subdomains. This ensures that consent saved on the root domain will be recalled on all subdomains.
Q: Can I have separate consent experiences on different subdomains?
A: Yes, you can have separate consent experiences on different subdomains. To achieve this, you need to create unique configurations and JavaScript for each subdomain. Additionally, both subdomains must be declared in their respective configuration settings (e.g., www.website.com and page.website.com).
Q: Is it possible to have most of my websites and subdomains operate under one configuration, while one specific subdomain has a separate consent experience?
A: Yes, this is possible, but it requires careful configuration.
Since Osano saves consent to the most specific domain declared, you would need to declare each individual subdomain under the configuration you want to share the consent experience across utilizing the cross-domain support setting.
The subdomain with a separate experience should be left on a different configuration. However, this approach can be complex to manage and is not generally recommended due to the maintenance required.
Related to