Mobile App SDK Setup: iOS, Android, React Native, and Flutter in Under 5 Minutes

• iOS SDK setup via CocoaPods or Swift Package Manager in three steps
• Android SDK setup via Gradle with minimal configuration
• React Native and Flutter wrappers for cross-platform teams
• RevenueCat integration that maps trials, purchases, renewals, and refunds to install source
• Server-side tracking captures conversions that ad pixels miss, even with ATT and SKAdNetwork limitations

The Grometrics SDK bridges that gap. It captures install source, tracks user journeys through onboarding screens, records paywall exposure, and ties every RevenueCat transaction back to the campaign and keyword that drove the install. You see real CAC, real ROAS, and real retention by acquisition source.

Most mobile analytics tools focus on event volume. They show you how many users opened a screen, clicked a button, or triggered an event. Grometrics is different. It is payment-attribution-first. Revenue is the primary metric. Every report starts with the question: which channel created paying customers?

• Install source attribution connects to RevenueCat transactions
• Onboarding funnel tracking shows where users drop before reaching the paywall
• Campaign-level ROAS uses real revenue, not platform-reported conversions
• First-party tracking works alongside SKAdNetwork, not around it

What the SDK does not do: The Grometrics SDK does not bypass Apple ATT or SKAdNetwork. It uses first-party, server-side tracking to capture conversions that identifiers and ad pixels miss. When identity signals are limited, attribution confidence decreases. That is a reality of mobile attribution in 2026, and Grometrics reports it honestly rather than claiming perfect attribution.

The initialization call requires your Grometrics project API key. You find this in your Grometrics dashboard under Settings. Pass the key, configure the RevenueCat integration, and the SDK automatically starts capturing install attribution and RevenueCat transaction events.

One important configuration step is enabling screen-level tracking. This records which onboarding screens each user sees, which paywall they encounter, and whether they convert. The SDK records these events on the device and syncs them to your Grometrics project for funnel analysis.

• Add pod 'Grometrics' to your Podfile
• Run pod install in your terminal
• Initialize Grometrics in application(_:didFinishLaunchingWithOptions:) with your API key
• Configure RevenueCat integration by passing your RevenueCat API key
• Enable screen tracking in your initialization options

API key location: Your Grometrics API key is in the dashboard under Settings. Create a separate key for each app environment (development, staging, production) to keep data organized.

Initialize the SDK in your Application class on app startup. The initialization call accepts your API key and a configuration object that enables RevenueCat integration and screen-level event tracking. The Android SDK handles background tracking automatically, capturing session events even when the app is not in the foreground.

Similar to iOS, you configure the RevenueCat integration during initialization. The SDK listens for RevenueCat purchase, renewal, and refund events and attributes them to the install source. This creates the source-to-revenue link that ad platforms cannot provide on their own.

• Add Grometrics Maven repository to project build.gradle
• Add implementation 'com.grometrics:android-sdk' to app build.gradle
• Initialize in Application.onCreate() with your API key
• Configure RevenueCat by passing your RevenueCat API key
• Enable screen event tracking in the configuration object

Minimum Android version: The Grometrics Android SDK requires Android API level 21 (Lollipop) or higher. This covers over 99 percent of active Android devices worldwide.

For React Native, install the Grometrics package via npm or yarn, then initialize it in your App.tsx or App.js entry point. The package automatically bridges to the native iOS and Android SDKs, so you get full install attribution and RevenueCat integration without writing platform-specific code.

For Flutter, add the Grometrics Flutter plugin to your pubspec.yaml, initialize it in your main.dart, and configure the RevenueCat integration the same way you would in a native app. The Flutter plugin handles platform channel communication automatically, giving you the same attribution depth as native implementations.

• React Native: npm install @grometrics/react-native and initialize in your app entry
• Flutter: flutter pub add grometrics_flutter and initialize in main.dart
• Both wrappers automatically bridge to native SDKs for full attribution
• Configure RevenueCat integration the same way as native apps

Cross-platform consistency: The React Native and Flutter wrappers expose the same API surface as the native SDKs. This means your reporting stays consistent whether you have iOS, Android, or both platforms in the wild.

These events flow into your Grometrics dashboard with the original install source attached. You can then see which Apple Search Ads keyword drove a trial, which Meta campaign produced a paying subscriber, or which organic channel converted best. The connection between install source and revenue event is the core value that ad platforms cannot give you.

The integration requires read-only access to your RevenueCat data. You generate an API key in RevenueCat with subscriber read permissions and paste it into your Grometrics SDK configuration. Once connected, the attribution data builds over time as new users convert.

• Generate a read-only API key in RevenueCat with subscriber read permissions
• Paste the key into your Grometrics SDK configuration
• Grometrics receives trial, purchase, renewal, and refund events automatically
• Events are attributed to the original install source for campaign-level reporting

RevenueCat permissions required: You only need the subscriber read permission in RevenueCat. Grometrics does not write any data to RevenueCat. It only reads transaction events to attach install source attribution.

Within the first hour, you will see install attribution data populate in your dashboard. Within the first day, you will start seeing conversion events as new users reach paywalls and complete purchases. Within the first week, you will have enough data to compare ROAS across campaigns and identify which channels are actually profitable.

The screen-level funnel data takes a bit longer to build because it requires users to progress through your onboarding flow. But even before you have significant funnel data, the install-to-revenue attribution gives you answers that most mobile app teams struggle to get.

• Install attribution appears within the first hour
• Revenue attribution appears within the first day
• Funnel data builds as users progress through onboarding
• Compare campaign ROAS within the first week

No additional tracking code needed: After the initial SDK setup and RevenueCat integration, Grometrics tracks everything automatically. You do not need to add any additional event tracking code to your app screens or flows.