Integrations are used for getting user choices from the Didomi Platform to your internal services or to third-party vendors that you use internally for emailing, user management, analytics, etc. They allow you to leverage consent data collected by Didomi in all your existing tools.
The Didomi Platform exports all user consent data collected at a fixed interval (usually daily). The data is exported to cloud object stores like AWS S3 or GCP Storage.
The Didomi Platform notifies an HTTP endpoint every time a new user choice is collected. The data is streamed in real-time to your services.
The Didomi Platform exposes all user choices via an API that you can leverage to build your own custom consent solutions.
We often get the question of what integration method should be used for a specific use case.
Choosing the right integration for your problems should be driven by 4 criteria:
- Push/pull model: Does the Didomi platform push user choices to your services (push) or do your services pull data from the platform (pull)?
- Delivery lag: How fast are the user choices data made available for consumption by your services?
- Scalability: How many user choices can be read and at what speed?
- Risk of loss: Can user choices be lost during transfer if your services are unavailable at any point?
Based on the 4 criteria defined above, you can use the following matrix to decide what integration best fits your use case:
The most common use cases that we see for our integrations are: