Purposes

In the Didomi Console, a purpose is the specific reason or objective for processing end-user data, such as advertising personalization, analytics, sharing with third parties, or targeted advertising. Purposes are presented in the Preferences layer of the consent banner.

The default list of purposes in Didomi is based on the following:

IAB Purposes

IAB TCF purposes are automatically assigned to IAB vendors and are added to your notices when you select a vendor in the notice. This mapping in the Didomi Console relies on the IAB Vendor List, where vendors declare the purposes for which they require consent.

  • The IAB TCF framework includes 11 purposes, and their content cannot be edited.
  • By default, IAB TCF purposes apply to European countries under GDPR, but you can modify their applicable regulations.

If you used IAB purposes in notices configured for U.S. regulations before December 13th 2024, the purposes are scoped to all regulations, and your notices remain unchanged.

List purpose

For IAB TCF, 11 purposes are available for use.

ID

Description
cookies 1. Store and/or access information on a device
select_basic_ads 2. Use limited data to select advertising
create_ads_profile 3. Create profiles for personalised advertising
select_personalized_ads 4. Use profiles to select personalised advertising
create_content_profileq 5. Create profiles to personalise content
create_content_profile 6. Use profiles to select personalised content
measure_ad_performance 7. Measure advertising performance
measure_content_performance 8. Measure content performance
market_research 9. Understand audiences through statistics or combinations of data from different sources
improve_products 10. Develop and improve services
use_limited_data_to_select_content 11. Use limited data to select content

US Purposes

  • The GPP framework includes 20 purposes (5 main purposes and 15 SPI), and their content cannot be edited.
  • By default, US purposes apply to the relevant regulations, as specified in the GPP Guidelines.
  • US purposes are automatically assigned to the default first-party vendor created for your organization.

For GPP framework, 20 purposes are available to use:

id description
sell-info Sell my personal information
share-info Share my personal information
target-ads Use my personal information for targeted advertising
use-info Use my personal information
addl-data Use additional personal information for further purposes
racial-ethnic Use information that reveal my racial or ethnic origin
id-numbers Use information that reveal my data for social security, driver's license, state identification card, or passport number
religion Use information that reveal religious beliefs
account-creds Use information that reveal account log-in, financial account, debit card, or credit card number in combination with any required security or access code, password, or credentials allowing access to an account
health-diagnosis Use information that reveal mental or physical health condition or diagnosis
geo-location Use information that reveal precise geolocation

sexual-orientation Use information that reveal sex life or sexual orientation

racial-religion-union Use information that reveal racial or ethnic origin, religious or philosophical beliefs, or union membership

citizenship-status Use information that reveal citizenship or immigration status

trans-nonbinary Use information that reveal my status as transgender or nonbinary

communication-data Use information that reveal mail, email, and text messages unless I am the intended recipient of the communication

national-origin Use information that reveal national origin

genetic-data Use information that reveal my genetic data

biometric-data Use information that reveal my biometric data for the purpose of uniquely identifying an individual

crime-victim-status Use information that reveal my status as a victim of a crime


If you do not want to display the IAB or US purposes in your notice, you can:

Custom purposes

Custom purposes are designed to offer flexibility to address your specific privacy requirements and needs.

When configuring a custom purpose, you can set:

  • A name and description for up to 54 languages.
  • The type of purpose: Standard or SPI.
  • Applicable regulations: All or specific regulations - By default, applicable to all regulations.
  • An SDK ID.

Custom purposes are not mapped to IAB purposes and are not shared with vendors on your website if you use the IAB TCF framework. For ad-related purposes, we strongly recommend using IAB standard purposes to simplify compliance.

Add purpose

Refer to our detailed documentation on creating custom purposes.