HTML5 SDK - Tizen and webOS
Overview
As of 202504.1.0, a new, rearchitected version of the HTML5 SDK has been released. We have embedded our Server-Side CMP API under the hood to deliver greater efficiency and scalability.
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 upgrade?
If you are already using our SDKs, it’s 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 dramatically 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.
Supported Platforms
The HTML5 SDK officially supports Chromium devices on Tizen and LG platforms.
| Manufacturer | Certified Versions | Supported Versions |
|---|---|---|
| Samsung | 2022 - Tizen 6.5 - Chromium 2021 - Tizen 6.0 - Chromium 2020 -Tizen 5.5 - Chromium 2019 - Tizen 5.0 - Chromium 2018 - Tizen 4.0 - Chromium | 2018+ |
| LG | 2022 - webOS TV 22 - Chromium 87 2021 - webOS TV 6.0 - Chromium 79 2020 - webOS TV 5.0 - Chromium 68 | 2020+ |
Prerequisites
- Tizen Studio
- WebOS TV CLI
- WebOS TV Emulator
- VirtualBox
Tech Stack Overview
| Specifications | Details |
|---|---|
| Language Version | Javascript (ES6) |
| Desktop OS | Windows, Mac |
| Build Dependencies | N/A |
| Compression Tools | Rollup |
| External Dependencies, 3rd Party Frameworks, and SDK Libraries/Components | N/A |
| Encryption | N/A |
SDK Size
| Files | Uncompressed File Size |
|---|---|
| onetrust.js | 140 KB |
Frequently Asked Questions (FAQ)
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.
Have any methods changed?
Yes, some methods have changed. Review the documentation for the new SDK for updated methods.
Will new CMP features require an SDK upgrade in the future?
Most new features will not require an SDK upgrade as they will be implemented via API headers, ensuring near-instant availability without breaking existing implementations.
Can I build my own UI?
Yes. In this case, we recommend using the Server-Side CMP API solution directly instead of the HTML5 SDK.
Are there rate limits for the CMP APIs?
No, there are no rate limits for our CMP APIs.
Where can I find updates for the CMP APIs?
For more information, see our Changelog page.
How is the API performance monitored?
We provide real-time monitoring dashboards and reports on API health via the OneTrust system status page.
Updated 3 days ago