You can setup domain delegation to ensure that the Web SDK is served from your own domains. When configured, all HTTP requests used by the Didomi SDK are routed through your own domain to ensure that Didomi does not appear as a third-party on your websites.
Pick a sub-domain that will be used for serving the Didomi Web SDK and API requests. We recommend picking a sub-domain of your biggest website.
Create a DNS record with your DNS provider or registrar that manages your domain, and use the following configuration parameters:
Your custom domain (
You will be creating a DNS record for a specific sub-domain of your domain name (like
NS (Name server)
The type NS allows us to generate SSL certificates for the sub-domain and serve your privacy center with SSL/HTTPS.
ns1.privacy-center.org ns2.privacy-center.org ns3.privacy-center.org ns4.privacy-center.org
Didomi's name servers that will host the DNS records for your custom domain
Before you can start using your custom domain, we need to setup our DNS servers to recognize it. Send an email to [email protected] to let us know what custom domain you will be using and that the setup is done on your side.
Do not configure the Didomi SDK to use your custom domain until we have confirmed that the setup is done on our side.
Once your sub-domain and proxy are setup, the SDK needs to be configured to use your domain for three types of requests:
loader.js request that is sent directly from the Embed code obtained from the Didomi Console.
The chunks loaded by the SDK itself.
Requests sent to the API by the SDK.
The following steps explain how to configure the SDK.
Update the Embed code from the Didomi Console to replace
https://privacy.company.com/. This ensures that the first request to load the Didomi SDK (the
loader.js file) uses your sub-domain.
apiPath properties in the
sdkPath property must start with
//. It must also end with a final
apiPath property must start with