Mobile Integration

Introduction

ADA rCDP Mobile SDKs integration with your mobile apps enables you to capture customer behavior and clickstream data from native and cross-platform mobile applications in rCDP. It allows you to track user interactions such as app launches, screen views, in-app actions, and transactions directly from your mobile applications.

ADA rCDP provides SDK-based integration for the following mobile platforms:

iOS SDK – For native iOS applications
Android SDK – For native Android applications
React Native SDK – For cross-platform mobile applications

Note: All SDKs (iOS, Android and React Native) use a common event model and API, ensuring consistent data collection across mobile platforms.

Choose the Right Approach

Use the following guidance to select the appropriate mobile integration method:

ADA rCDP iOS SDK

Use rCDP iOS SDK if you are building a native iOS application.

→ Supports event tracking and customer profile management
→ Enables push notifications and in-app notifications
→ Compatible with Objective-C and Swift

ADA rCDP Android SDK

Use rCDP Android SDK if you are building a native Android application.

→ Supports clickstream tracking and profile enrichment
→ Enables push notifications and location tracking
→ Integrates with Firebase services

ADA rCDP React Native SDK

Use rCDP React Native SDK if you are building a cross-platform mobile application.

→ Provides a wrapper over native SDKs
→ Enables event tracking and profile management
→ Supports both Android and iOS platforms

How Mobile Integration Works

All ADA rCDP Mobile SDKs integration follow a consistent flow to ensure reliable event tracking and data collection:

Obtain configuration details such as the API key or app ID from rCDP.
Add the ADA rCDP Mobile SDK to your mobile application.
Configure dependencies, permissions, and required platform settings.
Initialize the SDK during application launch using the configuration details.
Capture user interactions and events such as app launches, screen views, in-app actions, and transactions.
Send events and user profile data to rCDP (handled automatically by the SDK).
Verify the integration using logs or debugging tools to ensure events are being captured and sent correctly.
ADA rCDP process and activate the data in real time.

Tip: Initialize the SDK as early as possible in the application lifecycle to ensure complete session tracking.

What You Can Track

Using mobile integration, you can capture a wide range of user interactions that form the foundation for personalization and analytics:

App launches and session activities
Screen views and navigation events
Product interactions and in-app actions
User identity events such as login, registration, and profile updates
Transactions and conversion events

These events enable real-time segmentation, personalization, and customer journey orchestration across channels.

ADA SDK Binary Footprints

The ADA rCDP Mobile SDKs are modular and lightweight by design, adding minimal weight to your application's release build.

iOS: The SDK is distributed as an XCFramework (~855 KB total), bundling binaries for physical devices as well as simulator architectures used only during development and testing. In a standard Release/App Store build, Xcode includes only the device binary, bringing the effective footprint to approximately 215 KB.

Android: The SDK is distributed as a single AAR of approximately 220 KB. When R8/ProGuard is enabled in the release build, unused code and resources are stripped, further reducing the footprint in the final application.

React Native: Implemented as a wrapper over the native iOS and Android SDKs, so the effective binary impact matches the underlying native platform.

Note: Simulator binaries in the iOS XCFramework are used only for development and testing and are never shipped to end users. Final binary impact should be validated on the target application's release configuration during implementation.