NexaGuard CMP SDK - iOS Setup

Last updated: February 21, 2026


Package	`pod 'NexaGuardSDK', '~> 1.0'`
Minimum	iOS 14 · Swift 5.10 · Xcode 16
Footprint	approx. 200 kB zipped xcframework

1 Install via CocoaPods

Add the dependency in Podfile.
Do not run pod 'NexaGuardSDK', 'x.y.z' directly in terminal.

If a just-published version is not yet visible via CocoaPods CDN, use temporary git tag pinning:

Xcode 15/16 note: SDK 1.0.1 may trigger sandbox-copy build errors.
Resolved in 1.0.2+.
If required, temporarily set:
Build Settings -> ENABLE_USER_SCRIPT_SANDBOXING = NO

2 Initialize and Display the Banner (SwiftUI)

3 Public API Summary

Method	Description
`initialize(settingsId:completion:)`	Loads configuration, vendor list (GVL), and initializes consent state.
`showBanner(force: Bool = false)`	Displays banner; `force: true` reopens even if consent exists.

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

NexaGuard CMP fully supports Google Consent Mode.

Basic Mode (Default)

Google analytics/ads SDKs remain blocked until user consent.

No advertising or analytics signals are transmitted before user action.

Recommended for strict regulatory environments.

Advanced Mode

Google SDKs initialize immediately.

Limited, cookieless signals may be transmitted until user decision.

Consent state automatically updates SDK behavior post-selection.

Important: Consent Mode is a technical mechanism.
Regulatory compliance remains the responsibility of the customer's implementation and configuration decisions.

5 IAB TCF v2.3 Support

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

TC string generation and storage

Purpose and vendor consent tracking

Disclosed Vendors segment (VendorsDisclosed)

Allowed Vendors segment (VendorsAllowed)

Compatibility with downstream SDK consent routing

If TCF is enabled in your configuration, an active TC string is generated and stored.
The SDK mirrors this value to standard IAB storage for ecosystem compatibility.

6 Quickstart Verification Checklist

Before production release:

Initialize SDK once with production Settings ID.

Confirm banner renders on first app open.

Confirm reopen action (showBanner(force: true)) works.

Confirm consent updates propagate to integrated analytics or attribution SDKs.

Capture QA screenshots or screen recordings for audit records.

7 Performance Considerations

Initialization should occur once per app lifecycle.

SDK footprint is minimal and does not significantly impact cold start.

Consent updates are asynchronous and non-blocking.

8 Rollback Procedure

If rollback is required:

Disable feature flag or revert app version.

Remove NexaGuardSDK pod dependency.

Rebuild and validate no CMP initialization calls remain.

Confirm analytics SDK behavior is restored to pre-CMP configuration.

9 Logging Behavior

NxgLog.enabled controls NexaGuard SDK logs only.

Third-party/system logs (for example Firebase/WebKit/network stack) are outside NexaGuard log control.

10 Support

For integration assistance:

[email protected]

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

NexaGuard CMP SDK - iOS Setup

1 Install via CocoaPods#

2 Initialize and Display the Banner (SwiftUI)#

3 Public API Summary#

4 Consent Mode: Basic vs. Advanced#

Basic Mode (Default)#

Advanced Mode#

5 IAB TCF v2.3 Support#

6 Quickstart Verification Checklist#

7 Performance Considerations#

8 Rollback Procedure#

9 Logging Behavior#

10 Support#