Targeting defines the websites or mobile apps where a consent notice is embedded.
Notice targeting is based on a Domain/Mobile app ID, so you need to define a list of domains or mobile app IDs where a consent notice will be embedded and should be displayed.
This allows you to deploy the Didomi embed code only once, and define which notice is dynamically displayed on a website or mobile app.
There are two options for configuring domain/mobile app ID targeting:
Option 1: List all domains / app IDs
Use this option if you want your consent notice to apply to a specific list of domains or mobile app IDs. When this option is selected, your consent notice will only show on websites or mobile apps that match the defined domains and IDs.
To activate this option:
- Go to the last step of the notice configuration flow (3. Publish).
- Add your target domains (or app ID for mobile) in the dedicated field.
- Don't forget to click the plus sign (+) to add the domain!
- Click on Publish.

Even if you add or remove domains, your Didomi embed code will remain the same.
Option 2: Declare the notice as the default notice
Use this option if you want to create a consent notice that applies to all domains or mobile app IDs. When this option is selected, your consent notice will show on any website or mobile app that you embed it on.
To activate this option:
- Go to the last step of notice configuration flow (3. Publish).
- Enable the option to Declare the notice as the default notice.
- Click on Publish.
You do not need to redeploy the embed code when pushing updates of your notice configurations to your websites and mobile apps.
The former version of the Didomi console offered Manual targeting (websites & app), i.e., displaying a consent notice on any website or mobile app ID it was embedded on. This option is:
- No longer supported for notices created with the new console flow.
- Still operational for notices created with the old console flow. However, if custom domains are added, then manual targeting will no longer be available.