Domains
By default, whether used to load a consent notice, a preference center, or a privacy request widget, the Didomi Web SDK, including its assets (JavaScript files, images, etc.) and API requests, relies on the privacy-center.org domain.
You can use one of your own domains for:
Serving the Web SDK and API requests from your own domain by redirecting all requests to your domain instead of the domain used by Didomi (
privacy-center.org
). This ensures that Didomi does not appear as a third-party on your websites.Sharing consents across domains.
Reducing reliance on browsers. This ensure visitor's consent is captured and ads served comply with user choices.
Once configured, a custom domain can be used for some or all those purposes listed above.
We offer two solutions for setting up your domain:
Setup options available
Resilience
Robust against Adblockers until subdomain is blocked
Robust against Adblocker and Safari ITP until subdomain is blocked
Robust against Adblocker and Safari ITP.
Increase Adblocker resilience
✅
✅
✅
Safari ITP
❌
✅
✅
Implementation complexity
🟢 Low – NS record only
🔴 High – Requires reverse-proxy setup
🔴 High – Requires reverse-proxy setup + Path transformation
Recommendation
Best for low-budget, non-technical clients, or non-critical setups
Best for technical teams with strong infra and ITP concerns, and allows subdomain branding
Best for technical teams with strong infra and ITP concerns
Last updated