What is Didomi?

Didomi is a Consent Management Platform (CMP). It gives app users control over whether their data can be used by analytics, advertising, attribution, personalisation and other third-party services.

Pugpig Bolt supports the Didomi mobile SDK on iOS and Android. Didomi provides the consent notice and preference centre, while the customer controls the consent rules, vendors, purposes, wording and visual styling in the Didomi Console.

Didomi supports the IAB Transparency and Consent Framework (TCF) and the IAB Global Privacy Platform (GPP). These frameworks allow consent and privacy choices to be represented in standard formats that supported vendors can read.

How the integration works

When Didomi is configured for a Bolt app:

1. Bolt initialises the Didomi SDK using the customer’s Didomi configuration.
2. Didomi determines whether consent needs to be collected for the user and region.
3. If required, Didomi displays its native consent notice and preference centre.
4. The user’s choices are stored by the Didomi SDK and made available to supported vendors and integrations.
5. When a user changes their choices, the consent state can be used by connected SDKs and services to update their behaviour.

IAB-compliant vendors can read the relevant consent signals themselves. Non-IAB vendors need either their own consent API or an explicit integration so that they are not initialised, or do not process data, until the required consent is available.

For Pugpig HTML content and supported webviews, Pugpig can expose the app’s consent state through its CMP bridge. This allows content and services that follow the relevant CMP API standard to use the app’s consent state rather than presenting a second consent experience. Custom webviews may require the Pugpig CMP scripts to be added to the page.

The legal basis, wording and policy choices remain the customer’s responsibility. Pugpig provides the integration and technical plumbing, but does not decide what consent the customer should request.

What the customer needs to configure

The customer must complete the following in the Didomi Console before setup and testing can begin.

1. Create and publish the Didomi notice

Create the mobile app notice that should be used by the Bolt app. Configure the notice with the customer’s required:

• Purposes and legal bases
• Vendors and partner SDKs
• Regional or geolocation rules
• Consent notice and preference centre wording
• Branding, colours and styling
• Supported languages
• Privacy policy and other legal links

The notice should be published in the Didomi environment that matches the app build being tested.

2. Provide Pugpig with the Didomi identifiers

For each environment, provide:

• API key
• Notice ID

Use the staging or sandbox values for pre-release testing and the production values for the live app. These values should be shared securely and should not be posted in a public ticket or documentation page.

3. Confirm the privacy frameworks and regions

Confirm which frameworks and jurisdictions are required, for example:

• IAB TCF for EEA, UK or other applicable traffic
• GPP sections for US or other applicable jurisdictions
• Whether different notice behaviour is required by region
• Whether consent should be collected before the user can access app content

Didomi supports TCF and GPP, but the customer must configure the applicable sections, vendors and purposes in the Didomi Console. The exact signals consumed by each downstream service should be confirmed during implementation and testing.

4. Confirm any iOS App Tracking Transparency requirements

Didomi does not replace Apple’s App Tracking Transparency permission. If the app uses ATT, confirm:

• Whether the ATT prompt is required
• The desired order of the Didomi notice and the ATT prompt
• Which app behaviour or SDKs depend on ATT permission

The customer should obtain legal and platform-policy advice for the final consent and ATT experience.

5. Provide access for setup and testing

If required, provide Pugpig with access to the relevant Didomi production and staging or sandbox environments. Access should be sufficient to verify the notice, configuration, vendors, regional rules and test behaviour.

What Pugpig configures

Pugpig configures the Bolt-side integration, including:

• Initialising the Didomi SDK on iOS and Android
• Supplying the API key and Notice ID for the selected environment
• Connecting the consent experience to the Bolt app lifecycle
• Exposing consent to supported Pugpig content and webviews
• Connecting consent changes to supported third-party integrations included in the project

The exact app behaviour depends on the Bolt version and the third-party SDKs included in the customer’s app. Any custom or non-IAB integration should be agreed separately.

Environment and publishing rules

Use matching environments throughout the setup:

• Staging or sandbox: Didomi staging credentials, notice and configuration, used with a pre-release Bolt build.
• Production: Didomi production credentials, notice and configuration, used with the live Bolt app.

Official documentation

• Didomi Mobile SDK overview
• Didomi iOS setup
• Didomi Android setup
• Didomi third-party SDKs, TCF and GPP
• Didomi Google Consent Mode
• Pugpig guidance on CMPs in Bolt