Domains

The Didomi Web SDK, including its assets (Javascript files, images, etc...) and API requests, rely on the privacy-center.org domain to load a consent notice, preferences widget and/or privacy request widget by default.

As an alternative to relying on the default Didomi domain to serve these assets your organization can configure a custom domain to load the SDK and its assets. Some benefits of configuring a custom domain to serve the Didomi SDK include:

• Share consent across domains

• Prevent adblockers from blocking the Didomi SDK

• Ensures Didomi does not appear as a third-party on your websites

Custom domain configurations

Didomi offers your organization two different solutions to configure your custom domains:

Delegated custom domain relying on Didomi infrastructure

Reverse proxy relying on your organization's infrastructure

Only delegated custom domain relying on Didomi infrastructure (NS delegation) is available from the Didomi console. The articles in this section cover how to create and manage custom domains from the Didomi console using the NS delegation method.

Refer to the table below for additional information for all domain options available to your organization:

	Default (privacy-center.org)	NS delegation (subdomain)	Reverse proxy (subdomain)	Reverse proxy (main domain)
Increased adblocker resilience	❌	✅	✅	✅
Safari ITP	❌	❌	✅	✅
Implementation complexity	Low	Low - NS record only	High - requires reverse proxy setup	High - requires reverse proxy setup and path transformation
Recommendation	Low budget, non-technical teams or non-critical setups	Low budget, non-technical teams or non-critical setups	Technical teams with strong infra and ITP concerns, and allows for subdomain branding	Technical teams with strong infra and ITP concerns