Subdomain consent sharing lets a visitor choose once for every subdomain of your website, for example example.com, shop.example.com and blog.example.com. Each subdomain is a site of its own in Kukie.io, and the sites read one shared consent cookie. Organisation owners and admins can change this setting.
How it works
The banner runs only on the hostname its site was added with. A www. prefix is ignored, so example.com and www.example.com are one site. Any other subdomain, such as shop.example.com, needs a site of its own with its own embed code. The banner of example.com does not appear there.
When subdomain sharing is on, the banner writes its consent cookie (_cc_consent) for your whole domain, for example .example.com, instead of only for the hostname that set it. Every site under that domain reads the same cookie, so a choice made on one subdomain applies on the others.
When subdomain sharing is off (the default), the cookie belongs to the exact hostname that set it, and each subdomain asks visitors on its own.
Set up subdomain sharing
- Add each subdomain as a site in Kukie.io and install that site's embed code on the subdomain.
- For each of these sites, go to Site Settings > Consent and turn on Subdomain consent sharing.
- Leave Cookie domain empty. Kukie.io then uses your main domain, for example
.example.com, or.example.co.ukfor a site underco.uk. If you enter a domain instead, enter the same one on every site that shares consent. - Select Save Settings.
Settings that must match
A site uses a shared choice only when the choice was made under the same settings. Otherwise the banner asks the visitor again. Keep these the same on every site that shares consent:
- Cookie categories: the same categories in Banner Editor > Categories. When Re-consent on config change is on in Banner Editor > Regions (the default), a site with a different list of categories asks again.
- Consent version: Renew user consents in Site Settings > Consent raises the version on that site only, so renew consents on every site that shares consent at the same time. While one site has a newer version, a visitor who moves between the sites is asked on each of them, because each site stores its own version in the shared cookie.
What to know
- A choice is recorded in the Consent Log of the site where the visitor made it. The other sites use it without a record of their own.
- Sharing works only under one domain. A choice made on
example.comcannot reachexample.netor another brand's domain, because browsers keep each domain's cookies apart. - If your subdomains use different cookies or serve different audiences, keep sharing off so each site asks on its own.
- Tell visitors which websites their choice covers, for example in your cookie policy.
Check it worked
Make a choice on one subdomain, then open another. The banner does not appear there. In your browser's developer tools, the _cc_consent cookie shows your main domain with a leading dot, for example .example.com.
If the banner does not appear on a subdomain at all, even before a choice, add ?kukie_debug=1 to the page address. A domain mismatch in the console means that subdomain needs a site of its own.
