NexaGuard CMP SDK - Android Setup

Last updated: February 21, 2026


Artifact	`implementation("com.nexaguard:nxg-sdk:1.0.29")`
Minimum	API 24 · Kotlin 1.9 · AGP 8
Footprint	approx. 200 kB AAR

1 Add Maven Central

settings.gradle (top-level):

2 Add the Dependency

app/build.gradle.kts:

Pin exact versions in production for reproducible builds.

Snapshot builds:
Use <nextVersion>-SNAPSHOT and add:

3 Initialize and Display the Banner

Initialization should occur once during application startup.
Android API expects an Activity for initialization and banner methods.

Jetpack Compose Example

Classic View-Based (Activity)

4 Public API Summary

Method	Description
`initialize(activity, settingsId, onComplete?)`	Loads configuration, vendor list (GVL), and initializes consent state.
`forceShowBanner(activity)`	Reopens consent UI/preferences for review/update.

Consent actions and TC-string writing are handled internally by SDK UI flows.

NexaGuard CMP fully supports Google Consent Mode.

Basic Mode (Default)

Google SDKs remain blocked until user consent.

No advertising or analytics signals are transmitted prior to user interaction.

Recommended for strict regulatory environments.

Advanced Mode

Google SDKs initialize immediately.

Limited, cookieless signals may be transmitted until user choice.

Consent updates automatically adjust SDK behavior.

Important: Consent Mode is a technical framework.
Customers remain responsible for regulatory configuration decisions.

6 IAB TCF v2.3 Support

NexaGuard CMP Android implementation supports IAB TCF v2.3, including:

TC string generation and lifecycle management

Purpose and vendor consent tracking

Multi-segment TC string output:

core segment

VendorsDisclosed segment (type 1)

VendorsAllowed segment (type 2)

Compatibility with downstream SDK consent routing

If TCF is enabled, the TC string is stored and accessible via SDK methods.

7 Quickstart Verification Checklist

Before production release:

Initialize once during application startup.

Confirm banner displays on first launch.

Confirm reopen action works from privacy/settings screen.

Confirm consent changes propagate to analytics or attribution SDKs.

Validate TC string behavior (if TCF enabled).

Capture QA evidence for accept, reject, and granular flows.

8 Performance Considerations

Initialization is lightweight and asynchronous.

SDK footprint is minimal (~200 kB).

Consent updates are non-blocking.

Avoid repeated initialization in multiple activities.

9 Rollback Procedure

If rollback is required:

Disable CMP feature flag or revert to prior build.

Remove com.nexaguard:nxg-sdk dependency.

Rebuild and confirm no CMP initialization calls remain.

Validate analytics SDK behavior post-removal.

10 Support

For integration assistance:

[email protected]

Full documentation: https://developer.nexaguard.com

NexaGuard CMP SDK - Android Setup

1 Add Maven Central#

2 Add the Dependency#

3 Initialize and Display the Banner#

Jetpack Compose Example#

Classic View-Based (Activity)#

4 Public API Summary#

5 Consent Mode: Basic vs. Advanced#

Basic Mode (Default)#

Advanced Mode#

6 IAB TCF v2.3 Support#

7 Quickstart Verification Checklist#

8 Performance Considerations#

9 Rollback Procedure#

10 Support#