OneTrust Next Generation CMP SDKs
Overview
As of May 9, 2025 (202505.1.0 Spring Release), a new, rearchitected version of the CMP SDKs has been released. We have embedded our Server-Side CMP API to deliver a scalable solution that adapts to the latest privacy standards without requiring additional effort from your team.
For new, rearchitected CMP SDKs, see:
For previous versions, see:
Why this change?
Privacy regulations and consent signaling are evolving rapidly. As such, modern organizations need a future-proof, scalable, and regulation-ready solution that streamlines compliance without disrupting the user experience.
Why upgrading?
If you are already using our SDKs, it is a simple upgrade to take advantage of a more lightweight, scalable, and future-ready solution.
Key benefits of the new SDK
- Smaller SDK Footprint: The new architecture improves load times and system performance. The size of the SDK is also reduced.
- Server-Side Business Logic: We handle consent string generation and updates server-side, eliminating the need for SDK updates every time regulations change.
- Seamless Scalability: As consent evolves (e.g., Global Privacy Platform, TCF, and emerging frameworks), our API-driven approach ensures you stay compliant without disruption.
Frequently Asked Questions (FAQ)
1. Does SDK versioning still matter once the CMP API is implemented?
No. Moving forward, platform versioning is no longer a dependency for core consent logic.
2. How will OneTrust platform releases impact my SDK?
Instead of SDK frequent updates, we now bundle updates on a quarterly basis. See our OneTrust Seasonal Releases page and refer to the corresponding SDK Reference documentation to see the latest updates.
Have any methods changed?
Yes, some methods have changed. Review the corresponding SDK Reference documentation for the new updated methods.
3. Can I use the CMP API to build my own Mobile or CTV user interface?
Yes. In this case, we recommend using the Server-Side CMP API solution directly.
4. How can I build custom user interface components with the new CMP API?
Our CMP Simulator provides clear guidance to build UIs seamlessly.
5. Will new CMP features require an SDK upgrade in the future?
No, new features will not require an SDK upgrade as they will be implemented via API headers, ensuring almost instant availability without breaking existing implementations.
6. When I migrate from the legacy SDK (pre 202504.1.0) to the new SDK (202504.1.0+), will end users need to give consent again?
No, our API automatically migrates previously given consent from the legacy SDK. However, SDKs predating January 2024 may not support this migration which emphasizes the importance of keeping SDKs up to date.
7. Are there rate limits for the CMP APIs?
No, there are no rate limits for our CMP APIs.
8. Where can I find updates for the CMP APIs?
For more information, see our Changelog page.
9. How is the API performance monitored?
We provide real-time monitoring dashboards and reports on API health via the OneTrust system status page.
10. How do I migrate to the next generation CMP SDKs?
Please review the corresponding SDK Reference documentation for more information and contact your OneTrust Customer Success Manager (CSM) or representative if you need additional assistance.
Updated about 8 hours ago