NexaGuard
  1. Mobile-SDKs
NexaGuard
  • Getting-Started
    • NexaGuard Developer Documentation
    • Quickstart (5 to 10 Minutes)
    • Documentation Overview
    • Concepts and Glossary
  • Compliance-and-Standards
    • Compliance Overview
    • IAB TCF v2.3 Support
    • Google Consent Mode v2 Validation
    • TCF API Validation
    • Audit Checklist (Pre-Launch)
  • Web-and-CMS-Integrations
    • NexaGuard CMP SDK – Web & GTM Setup
    • Integrate NexaGuard CMP with Webflow and Wix
    • Integrate NexaGuard CMP with WordPress
    • Integrate NexaGuard CMP with Drupal
    • Integrate NexaGuard CMP with Shopify
  • Mobile-SDKs
    • NexaGuard CMP SDK - iOS Setup
    • iOS SDK API Reference
    • NexaGuard CMP SDK - Android Setup
    • Android SDK API Reference
    • App Attribution Partner (AAP) Integrations
  • Developer-Reference
    • Web JS API Reference
    • Consent Event Schema
    • Deployment and Environments
    • NexaGuard Debug Tool
    • Troubleshooting Playbook
    • Performance and Best Practices
    • Accessibility and UX Guidelines
    • Localization Workflow
    • Migration Guide
  • Security-and-Privacy
    • Security Overview
    • Privacy Architecture
    • Data and Logging Transparency
    • Subprocessors
    • CSP and Network Allowlist
  • Enterprise-and-Legal
    • DPA and Legal Pack
    • RFP Feature Matrix
    • Status and Reliability
    • Support and Escalation
    • NexaGuard CMP SDK – Commercial Licence
  • Operations
    • Changelog and Version Policy
  1. Mobile-SDKs

Android SDK API Reference

Last updated: February 21, 2026

1. Initialization#

NexaGuardCMP.initialize(activity, settingsId, onComplete?)
call once at app startup with an Activity
fetches remote config + GVL and prepares consent state
callback is invoked after load/routing path completes

2. Banner Controls#

NexaGuardCMP.forceShowBanner(activity)
always opens consent UI/preferences for review/update

3. Public Surface Policy#

consent action handlers are internal SDK flow controls
user decisions should be made through NexaGuard CMP UI only
expose a "Review Consent" entry and route it to forceShowBanner(activity)

4. TCF Output Notes#

For TCF v2.3 flows, Android generates a multi-segment TC string:
core segment
Vendors Disclosed segment (type 1)
Vendors Allowed segment (type 2)

5. Lifecycle Notes#

initialize once; do not repeatedly initialize per screen
expose a visible "Review Consent" entry in app settings/privacy
use forceShowBanner(activity) for QA re-entry tests

6. Logging#

SDK logs are controlled through NxgLog.enabled
keep disabled in production unless troubleshooting
Previous
NexaGuard CMP SDK - Android Setup
Next
App Attribution Partner (AAP) Integrations