In-App Implementation
Clickio CMP SDK provides a comprehensive solution for managing user consent in mobile applications, ensuring compliance with various privacy regulations and frameworks. Our SDK is available for multiple platforms and supports the latest privacy standards.
Supported Platforms
-
Android: |
-
Native implementation in Kotlin
-
Published on Maven Central Repository
-
-
iOS: |
-
Native implementation in Swift
-
Available as XCFramework, SPM package, and CocoaPods package
-
-
Flutter:
-
Wrapper around native SDKs
-
Published on pub.dev
-
-
React Native: SDK Repository | Demo App
-
Wrapper around native SDKs
-
Published on npm
-
Key Features
TCF v2.2 Compliance
Our SDK fully supports the IAB Europe's Transparency & Consent Framework v2.2, ensuring compliance with GDPR requirements. It properly stores and manages TC Strings and related consent data.
Official Resources:
GPP Compliance
We support the Global Privacy Platform (GPP) standard, which helps standardize privacy compliance across US jurisdictions. The SDK handles GPP data storage and management according to technical specifications.
Official Resources:
Google Consent Mode v2
The SDK integrates with Google Consent Mode v2, allowing seamless communication of consent states to Google services and third-party measurement partners. This includes:
-
Firebase Analytics SDK integration with automatic consent state updates
-
Integration with App Attribution Partners (AAPs) SDKs
-
The CMP SDK detects the presence of the integrated Firebase or AAP SDK and automatically sends consent signals as appropriate.
Supported Google’s certified App Attribution Partners (AAPs) SDKs:
Official Resources:
Apple App Tracking Transparency (ATT)
Our SDK provides flexible integration options with Apple's App Tracking Transparency framework and supports different ATT implementation flows.
Official Resources:
Additional Consent Support
The SDK supports Google's Additional Consent specification, allowing communication with vendors not registered on the IAB Europe Global Vendor List.
Official Resources:
Getting Started
To begin integrating Clickio CMP into your mobile application:
-
Choose the appropriate SDK for your platform from the repositories above
-
Follow the platform-specific installation instructions
-
Configure the SDK with your publisher ID and other required settings
-
Implement the desired consent flow based on your requirements
For detailed implementation guides and technical specifications, please refer to the documentation in each repository.
Passing Consent Rejection from App to WebView via URL
Many iOS apps are just WebView wrappers. Since all WebView content is treated as part of the app, the ATT prompt must be shown. If the user declines ATT, showing a CMP dialog inside the WebView is redundant.
SDK integration and custom WebView handling are too complex for this scenario.
Consent rejection from ATT can be passed directly via the WebView page URL:
-
GET parameter
https://example.com/?clickio_consent=denyAll
-
Hash parameter (alternative way)
https://example.com/#clickio_consent=denyAll
When CMP detects these parameters, it:
-
Records rejection immediately
-
Suppresses the dialog
-
Works with both TCF and non-TCF
-
Registers opt-out for US users
Benefits
-
No SDK integration
-
No WebView modifications beyond adding a URL parameter
-
Minimal effort for wrapper apps
Support
For technical support and questions about implementation, please contact our