-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cross-domain Consent #79
Comments
Hi, The "Cookie domain" field in the GTM template is used for this. Consent will then be valid on all subdomains, for example |
Hi, but be careful when setting up those domains. I don't recommend testing it in production mode. The functionality around cookies itself is very outdated. If you set up two domains, for example We can mention it in the readme (@tg666). It might be useful to have it mentioned in the original plugin as well. orestbida/cookieconsent#683 To support cross-domain across different domains (example.com, myexampleapp.com, ...) you would need some backend solution to store the consents, e.g. 68publishers/consent-management-platform. For example, we currently use the bar from the web app in mobile apps, which allows us to sync across devices. |
Hi @BKKNomad, was it resolved? |
so finally we can do cross domain tracking or not? |
As mentioned earlier:
For supporting cross-domain you will need a back-end solution to store consents. |
Yes many thanks for your great support @jelen07, we were able to set up cross-subdomain cookie consent. |
Hello, many thanks for this great solution which works really well. However, it seems that it's not possible to set up cross-domain consent to avoid having the Cookie Consent banner showing again when we switch from a domain to another, or a subdomain to another one.
Do you have any solution to set up cross-domain Cookie Consent with this solution?
Many thanks in advance for your support.
The text was updated successfully, but these errors were encountered: