There are several new features and benefits of using the Experience Platform Mobile SDK. These SDKs offer extensions to augment core SDK functionality, server-side configuration, and new Adobe Experience Cloud solution functionality. The following table highlights some of the improvements in the Experience Platform Mobile SDK:
| Core Features | Experience Platform SDK | 4x SDK |
|---|---|---|
| Server-side, dynamic configuration | ✔️ | |
| Programmatic configuration | ✔️ | ✔️ |
| Configuration UI | Launch | Mobile Services |
| Partner SDK extensions | ✔️ | |
| Lifecycle metrics | ✔️ | ✔️ |
| GET/POST postbacks | ✔️ | ✔️ |
| Rules & Data Elements | ✔️ |
| Solution | Experience Platform SDK | 4x SDK |
|---|---|---|
| Adobe Analytics | ✔️ | ✔️ |
| Adobe Analytics - Media Analytics | ✔️ | ✔️ |
| Adobe Analytics - Mobile Services | Messaging and Marketing Links | ✔️ |
| Adobe Audience Manager | ✔️ | ✔️ |
| Adobe Campaign Classic | ✔️ | |
| Adobe Campaign Standard | Push and in-app messaging | Push only |
| Adobe Target | ✔️ | ✔️ |
| Places Service | ✔️ | |
| Project Griffon (BETA) | ✔️ |
If you need access to Experience Platform Launch, see User Permissions. If you create a web property, you can also create a mobile property. If you do not see the option to create a mobile property, turn off your ad blocker, and refresh the page.
If your apps send data to the same Analytics report suites, use the same extensions, rules, data elements, and so on. We recommend that you group all of these mobile apps into the same property. If your apps send data to different Analytics report suites, or user different extensions per app, create separate mobile properties. If you group your mobile apps into one property, you can also split them into separate properties over time.
To delete a mobile property from Experience Platform Launch, see Delete a property.
{% hint style="warning" %} If you delete a mobile property, you cannot undo this action! {% endhint %}
The Experience Platform SDK is available through Cocoapods and Gradle, and Github. For more information, see Get the SDK.
Implementing two the SDKs in your app is not recommended, supported, or even technically feasible.
The Experience Platform SDK migrates the locally stored user contexts from the 4x SDKs. Using both SDKs can cause severe data quality issues and user cliffing. For more information, see Upgrade to the Experience Platform SDKs.
For a complete list of supported platforms, please see Latest SDK Versions.
- Android versions 4.0 or later (API levels 14 or later)
- iOS versions 10 or later
- React Native versions 0.44.0 or later
- Flutter versions 1.10.0 or later
| Extension | iOS (KB) | Android (KB) |
|---|---|---|
| Core | 504 | 168 |
| Adobe Analytics | 54 | 21 |
| Adobe Audience Manager | 40 | 13 |
| Adobe Target | 77 | 27 |
| Profile | 20 | 8 |
| Adobe Campaign Standard | 60 | 30 |
| Places | 36 | 20 |
| Places Monitor | 10 | 19 |
The size values in the table are provided as indicative estimates, with the following considerations:
- Mobile Core, which includes the Lifecycle, the Identity, and the Signals extensions, is required for all other extensions. The final app size increase can be calculated by adding the Mobile Core size to each of the enabled extensions. For example, the iOS app distribution using the Target and Analytics extensions will have a total size increase of 635 KB. (Core: 504 KB + Analytics: 54 KB + Target: 77 KB).
- The iOS (SDK extension versions 2+) estimates are based on Xcode’s App Thinning size report for one architecture. The Android (SDK extension versions 1+) size estimates listed refer to unsigned apps and do not account for proguarding.
Android developer documentation recommends that to make your APK file as small as possible, enable shrinking to remove unused code and resources in your release build. For more information, see Shrink, obfuscate, and optimize your app. Shrinking is accomplished by using ProGuard. The Experience Platform Mobile SDK for Android comes with default ProGuard rules that are included in the Core AAR package (see proguard.txt). We recommend that you use this default package when you implement.
Add the following rule to your custom ProGuard rules file, typically labeled proguard-rules.pro. For more information, see Shrink, obfuscate, and optimize your app.
-keep class com.adobe.marketing.mobile.* {
<init>(...);
}How you implement push notification tracking and measurement with the SDK depends on the Experience Cloud solution being used. Specifically, for:
- Adobe Campaign Standard extension, see Adobe Campaign Standard Push Tracking.
- Adobe Campaign Classic extension, see Adobe Campaign Classic Push Notifications Tracking.
- Adobe Analytics - Mobile Services extension, see Set Up Tracking for Mobile Services Push Notifications.
Lifecycle metrics are out-of-the-box metrics that are automatically collected when the SDK is first implemented in your app. For more information, see Lifecycle.
For more information, see Processing Rules Tips and Tricks.
A launch is measured by the SDK when a user opens the app for the first time or returns to the app after having been out of the app for longer than the specified timeout value. The typical timeout is 5 minutes (300 seconds) in lifecycleTimeout configuration setting.
A visit is a server-side calculation by Adobe Analytics and is based on the first and last data hits that are sent by the SDK without exceeding a visit timeout. Typically, session timeouts are set at 30 minutes for a report suite. Although visits come from traditional web analytics, these hits still provide valuable insights into how users enter and exit from your app.
Yes. To capture data in multiple report suites, see Report Suites.
- Visit the SDK community forum to ask questions
- Contact Adobe Experience Cloud customer care for immediate assistance