How will Cookiebot handle a scenario where a website is hosted under a third-party domain shared by many other websites?
How will Cookiebot handle a scenario where a website is hosted under a third-party domain shared by many other websites?
Example:
I'm a Cookiebot subscriber using a third-party booking engine and my pages are hosted under service.third-party-provider.com/my-pages/.
User X is also a Cookiebot subscriber using the same third-party booking engine at service.third-party-provider.com/user-x-pages/.
User Y's booking pages are hosted under service.third-party-provider.com/user-y-pages/, but User Y is not (yet) a Cookiebot subscriber.
Questions:
1.
I assume that my unique "Domain Group ID" or "cbid" will ensure there will be no conflicts in handling cookie consents in case the same unique browser visits both my booking pages and user X's booking pages.
Can someone please confirm this?
2.
What about scanning the domain/sub-domain for cookies?
Is the cookie scanning process based on my unique "Domain Group ID" or will Cookiebot just scan the entire service.third-party-provider.com sub-domain thus finding cookies that don't belong to my pages?
3.
Similar to question no.2 - will Cookiebot determine the number of subpages based on the Cookiebot-script including my "Domain Group ID" or by scanning the the entire service.third-party-provider.com sub-domain?
-
Hey Dan,
Can you clarify do you run your website with your own domain and you link to external service or your website is a sub-folder to someone else's domain ?
There should not be any conflicts if it's the first case. The third party service must be responsible for handling the consent on their cookies.
If it is the second options then you need to open a ticket to the support with your sub-domain and information and they will limit the scan to crawl only your sub-domain.
Regards,
Martin0 -
Hi Martin,
Thanks for getting back to me.
It's your second option, I'll guess.To clarify:
I have a main website at www.mywebsite.com + some additional checkout pages provided by a third-party service at service.third-party-provider.com/my-pages/.
Although the checkout pages are hosted by a third-party provider, the pages are owned by me and I'm responsible for the content. So I'm responsible for handling the consent of cookies on service.third-party-provider.com/my-pages/.However I'm not responsible for, nor having any connection what so ever to, other pages hosted under the service.third-party-provider.com sub-domain like, for example, User X's pages at service.third-party-provider.com/user-x-pages/.
I just want to make sure I can use Cookiebot on www.mywebsite.com + service.third-party-provider.com/my-pages/ without running into any issues regarding cookie consents and/or cookie scanning with other pages hosted under service.third-party-provider.com.
I also don't want to pay a license fee based on scanning the entire service.third-party-provider.com sub-domain.
Best regards
Dan0 -
Hey Dan,
Please setup 2 domains in your account: one is the main domain and the other the third party domain. Afterwards open a support ticket with this information and they will setup a scan to only scan the sub-folder of the third party domain.
This won't conflict with other cookies, cookie banners or users on the third party service site.
Regards,
Martin0 -
Hi Martin,
Great!
Thanks for your support.
A final question.Is the cookie scanning process limited to pages containing the Cookiebot script, or is the list of cookies generated based on scanning the entire domain or sub-domain?
Best regards
Dan
0 -
Hey Dan,
The cookiebot script is required in order to show the Cookie banner so users can accept and decline cookies and if you don't have it user won't be able to perform this action.
The cookie generated list is based on the domain or sub-domain, yes. You can see some more information here: https://support.cookiebot.com/hc/en-us/articles/360004051134-Do-subdomains-require-a-separate-subscription-
Regards,
Martin0
Please sign in to leave a comment.
Comments
5 comments