Targeting is what defines on what websites or mobile apps a consent notice is embedded.
We support two types of targeting:
- Domain/Mobile app ID targeting: Define a list of domains or mobile app IDs where a consent notice will be embedded and should be displayed.
- Manual targeting (Websites only): A consent notice will be displayed on any website or mobile app ID it is embedded on.
Both types of targeting support pushing updates of your notice configurations to your websites and mobile apps without re-deploying the embed code.
1- Domain/Mobile app ID targeting
This targeting mode allows you to deploy the Didomi embed code once and define what notice is displayed on a website or mobile app dynamically.
When creating a notice, you can configure domain/mobile app ID targeting in two ways:
- Use on all domains/mobile apps: 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.
- Custom domains/mobile app IDs: Create a consent notice that applies 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 domains and IDs defined.
For instance, if you create a notice that targets all your websites and, later on, need to create a separate notice for a specific website, you will be able to do so without re-deploying the Didomi embed code.
2- Manual targeting (Websites & App)
This targeting mode provides an Embed code that will display the consent notice wherever it gets embedded, irrespective of the configured domains or mobile app IDs. Domains or mobile app IDs defined in the Environment tab do not apply when using manual targeting.
This mode is useful if you want to use different consent notices on a single domain.
To use Manual targeting, pick the Manual targeting code in the Embed code section:
📰 Please consult the technical documentation: