۶Ƶ

Install ۶Ƶ Experience Platform Mobile SDKs tutorial_install_mobile_sdks

Learn how to implement the ۶Ƶ Experience Platform Mobile SDK in a mobile app.

Prerequisites

  • Successfully built a tag library with the extensions described in the previous lesson.
  • Development Environment File ID from the Mobile Install Instructions.
  • Downloaded the or .
  • Experience with (iOS) or (Android)

Learning objectives

In this lesson, you will:

  • Add the required SDKs to your project.
  • Register the extensions.
NOTE
In a mobile app implementation, the terms extensions and SDKs are nearly interchangeable.
iOS

Swift Package Manager

Instead of using CocoaPods and a Pod file (as outlined in Generate SDK install instructions), you add individual packages using Xcode’s native Swift Package Manager. The Xcode project already has all packages dependencies added for you. The Xcode Package Dependencies screen should look like:

Xcode Package Dependencies {modal="regular"}

In Xcode, you can use File > Add Packages… to add packages. The table below provides links to the URLs you would use to add packages. The links also direct you to more information about each specific package.

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 8-row-2 9-row-2
Package Description

The AEPCore, AEPServices, and AEPIdentity extensions represent the foundation of the ۶Ƶ Experience Platform SDK - every app using the SDK must include them. These modules contain a common set of functionality and services which all SDK extensions do require.

  • AEPCore contains implementation of the Event Hub. The Event Hub is the mechanism used for delivering events between the app and the SDK. The Event Hub is also used for sharing data between extensions.
  • AEPServices provides several reusable implementations needed for platform support, including networking, disk access, and database management.
  • AEPIdentity implements the integration with ۶Ƶ Experience Platform Identity services.
  • AEPSignal represents the ۶Ƶ Experience Platform SDKs Signal extension that allows marketers to send a “signal” to their apps to send data to external destinations or to open URLs.
  • AEPLifecycle represents the ۶Ƶ Experience Platform SDKs Lifecycle extension that helps collect application lifecycle metrics such as application install or upgrade information, application launch and session information, device information, and any additional context data provided by the application developer.
The ۶Ƶ Experience Platform Edge Network mobile extension (AEPEdge) allows you to send data to the ۶Ƶ Edge Network from a mobile application. This extension allows you to implement ۶Ƶ Experience Cloud capabilities in a more robust way, serve multiple ۶Ƶ solutions through one network call, and simultaneously forward this information to the ۶Ƶ Experience Platform.
The Edge Network mobile extension is an extension for the ۶Ƶ Experience Platform SDK. The extension requires the AEPCore and AEPServices extensions for event handling, as well as the AEPEdgeIdentity extension for retrieving the identities, such as ECID.
The ۶Ƶ Experience Platform Edge Identity mobile extension (AEPEdgeIdentity) enables handling of user identity data from a mobile application when using the ۶Ƶ Experience Platform SDK and the Edge Network extension.
The ۶Ƶ Experience Platform Consent Collection mobile extension (AEPConsent) enables consent preferences collection from the mobile application when using the ۶Ƶ Experience Platform SDK and the Edge Network extension.
The ۶Ƶ Experience Platform User Profile Mobile extension (AEPUserProfile) is an extension to manage user profiles for the ۶Ƶ Experience Platform SDK.
The ۶Ƶ Experience Platform Places extension (AEPPlaces) allows you to track geolocation events as defined in the ۶Ƶ Places interface and in ۶Ƶ Data Collection Tag rules.
The ۶Ƶ Experience Platform Messaging extension (AEPMessaging) allows you to send push notification tokens and push notification click-through feedback to the ۶Ƶ Experience Platform.
The ۶Ƶ Experience Platform Optimize extension (AEPOptimize) provides APIs to enable real-time personalization workflows in the ۶Ƶ Experience Platform Mobile SDKs using ۶Ƶ Target or ۶Ƶ Journey Optimizer Offer Decisioning. It requires AEPCore and AEPEdge extensions to send personalization query events to the Experience Edge Network.
۶Ƶ Experience Platform Assurance is a product from ۶Ƶ Experience Cloud to help you inspect, proof, simulate, and validate how you collect data or serve experiences in your mobile app.

Import extensions

Open in Xcode the project in the Start folder of the sample app.

In Xcode, navigate to Luma > Luma > AppDelegate and ensure that the following imports are part of this source file.

code language-swift
// import AEP MobileSDK libraries
import AEPCore
import AEPServices
import AEPIdentity
import AEPSignal
import AEPLifecycle
import AEPEdge
import AEPEdgeIdentity
import AEPEdgeConsent
import AEPUserProfile
import AEPPlaces
import AEPMessaging
import AEPOptimize
import AEPAssurance

Do the same for Luma > Luma > Utils > MobileSDK.

Update AppDelegate

Navigate to Luma > Luma > AppDelegate in the Xcode Project navigator.

  1. Replace the @AppStorage value YOUR_ENVIRONMENT_ID_GOES_HERE for environmentFileId with the Environment File ID value that you retrieved from tags in Generate SDK install instructions.

    code language-swift
    @AppStorage("environmentFileId") private var environmentFileId = "YOUR_ENVIRONMENT_ID_GOES_HERE"
    
  2. Add the following code to the application(_, didFinishLaunchingWithOptions) function.

    code language-swift
    // Define extensions
    let extensions = [
        AEPIdentity.Identity.self,
        Lifecycle.self,
        Signal.self,
        Edge.self,
        AEPEdgeIdentity.Identity.self,
        Consent.self,
        UserProfile.self,
        Places.self,
        Messaging.self,
        Optimize.self,
        Assurance.self
    ]
    
    // Register extensions
    MobileCore.registerExtensions(extensions, {
        // Use the environment file id assigned to this application via ۶Ƶ Experience Platform Data Collection
        Logger.aepMobileSDK.info("Luma - using mobile config: \(self.environmentFileId)")
        MobileCore.configureWith(appId: self.environmentFileId)
    
        // set this to false or comment it when deploying to TestFlight (default is false),
        // set this to true when testing on your device.
        MobileCore.updateConfigurationWith(configDict: ["messaging.useSandbox": true])
        if appState != .background {
            // only start lifecycle if the application is not in the background
            MobileCore.lifecycleStart(additionalContextData: nil)
        }
    
        // assume unknown, adapt to your needs.
        MobileCore.setPrivacyStatus(.unknown)
    })
    

The above code does the following:

  1. Registers the required extensions.
  2. Configures MobileCore and other extensions to use your tag property configuration.
  3. Enables debug logging. More details and options can be found in the .
  4. Starts lifecycle monitoring. See Lifecycle step in the tutorial for more details.
  5. Sets the default consent to unknown. See Consent step in the tutorial for more details.

Ensure you update MobileCore.configureWith(appId: self.environmentFileId) with the appId based on the environmentFileId from the tag environment you are building for (development, staging, or production).

Android

Gradle

You use the dependencies from the Generate SDK install instructions to add individual packages using Gradle’s integration with Android Studio, The Android Studio project already has all packages dependencies added for you.

  1. Select FolderOutline as the tool.

  2. Select Android view.

  3. Select Gradle scripts > build.gradle.kts (Module :app) from the left pane. Then, in the right pane, scroll until you see dependencies.

    Android Gradle Dependencies {modal="regular"}

In Android Studio, you can use File > Project Structure… to add module dependencies. Select Dependencies and then use Modules Add to add modules. The table below provides links to the URLs you would use to add dependency modules. The links also direct you to more information about each specific module.

table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2 6-row-2 7-row-2 8-row-2 9-row-2
Package
com.adobe.
marketing.mobile:
Description

The MobileCore and Identity extensions represent the foundation of the ۶Ƶ Experience Platform SDK. Every app using the SDK must include them. These modules contain a common set of functionality and services that all SDK extensions do require.

  • MobileCore contains the implementation of the Event Hub. The Event Hub is the mechanism used for delivering events between the app and the SDK. The Event Hub is also used for sharing data between extensions and provides several reusable implementations needed for platform support, including networking, disk access, and database management.
  • Identity implements the integration with ۶Ƶ Experience Platform Identity services.
  • Signal represents the ۶Ƶ Experience Platform SDK’s Signal extension that allows marketers to send a “signal” to their apps to send data to external destinations or to open URLs.
  • Lifecycle represents the ۶Ƶ Experience Platform SDK’s Lifecycle extension that helps collect application Lifecycle metrics, such as application install or upgrade information, application launch and session information, device information, and any additional context data provided by the application developer.
The ۶Ƶ Experience Platform Edge Network mobile extension (AEPEdge) allows you to send data to the ۶Ƶ Edge Network from a mobile application. This extension allows you to implement ۶Ƶ Experience Cloud capabilities in a more robust way, serve multiple ۶Ƶ solutions through one network call, and simultaneously forward this information to the ۶Ƶ Experience Platform.
The Edge Network mobile extension is an extension for the ۶Ƶ Experience Platform SDK. The extension requires the Mobile Core and Services extensions for event handling. And the Identity for Edge Network extension for retrieving the identities, such as ECID.
The ۶Ƶ Experience Platform Edge Identity mobile extension enables handling of user identity data from a mobile application when using the ۶Ƶ Experience Platform SDK and the Edge Network extension.
The ۶Ƶ Experience Platform Consent Collection mobile extension enables consent preferences collection from the mobile application when using the ۶Ƶ Experience Platform SDK and the Edge Network extension.
The ۶Ƶ Experience Platform User Profile Mobile extension is an extension to manage user profiles for the ۶Ƶ Experience Platform SDK.
۶Ƶ Places Service is a geo-location service that enables mobile apps with location awareness. And to understand the location context by using rich and easy-to-use SDK interfaces accompanied by a flexible database of points of interests (POIs). For more information, see the Places Service Documentation.
This service is the Places mobile extension for the Android 2.x ۶Ƶ Experience Platform SDK and requires the Core extension for event handling.
The ۶Ƶ Experience Platform Messaging extension powers push notifications, in-app messages, and code-based experiences for your mobile apps. This extension also helps you to collect user push tokens and manages interaction measurement with ۶Ƶ Experience Platform services.
The ۶Ƶ Experience Platform Optimize extension provides APIs to enable real-time personalization workflows in the ۶Ƶ Experience Platform SDKs using ۶Ƶ Target or ۶Ƶ Journey Optimizer Offer Decisioning. It depends on the Mobile Core and requires Edge Extension to send personalization query events to the Experience Edge Network.
Assurance (a.k.a. project Griffon) is a mobile extension for ۶Ƶ Experience Platform that allows integrating with ۶Ƶ Experience Platform Assurance. The extension helps to inspect, proof, simulate, and validate how you collect data or serve experiences in your mobile app. This extension requires MobileCore.

Import extensions

In Android Studio, navigate to app > kotlin+java > com.adobe.luma.tutorial.android > LumaApplication and ensure that the following imports are part of the source file.

code language-kotlin
import com.adobe.marketing.mobile.Assurance
import com.adobe.marketing.mobile.Edge
import com.adobe.marketing.mobile.Lifecycle
import com.adobe.marketing.mobile.LoggingMode
import com.adobe.marketing.mobile.Messaging
import com.adobe.marketing.mobile.MobileCore
import com.adobe.marketing.mobile.MobilePrivacyStatus
import com.adobe.marketing.mobile.Places
import com.adobe.marketing.mobile.Signal
import com.adobe.marketing.mobile.UserProfile
import com.adobe.marketing.mobile.edge.consent.Consent
import com.adobe.marketing.mobile.edge.identity.Identity
import com.adobe.marketing.mobile.optimize.Optimize

Do the same for app > kotlin+java > com.adobe.luma.tutorial.android > models > MobileSDK.

Update LumaApplication

In the Android view, navigate to app > kotlin+java > com.adobe.luma.tutorial.android > LumaApplication in Android Studio.

  1. Replace "YOUR_ENVIRONMENT_FILE_ID" in private var environmentFileId = "YOUR_ENVIRONMENT_ID_GOES_HERE" with the Environment File ID value that you retrieved from tags in Generate SDK install instructions.

    code language-kotlin
    private var environmentFileId = "YOUR_ENVIRONMENT_ID_GOES_HERE"
    
  2. Add the following code to override fun onCreate() function in class LumaApplication : Application().

    code language-kotlin
    // Define extensions
    val extensions = listOf(
       Identity.EXTENSION,
       Lifecycle.EXTENSION,
       Signal.EXTENSION,
       Edge.EXTENSION,
       Consent.EXTENSION,
       UserProfile.EXTENSION,
       Places.EXTENSION,
       Messaging.EXTENSION,
       Optimize.EXTENSION,
       Assurance.EXTENSION
    )
    
    // Register extensions
    MobileCore.registerExtensions(extensions) {
    // Use the environment file id assigned to this application via ۶Ƶ Experience Platform Data Collection
      Log.i("Luma", "Using mobile config: $environmentFileId")
      MobileCore.configureWithAppID(environmentFileId)
    
      // set this to true when testing on your device, default is false.
      //MobileCore.updateConfiguration(mapOf("messaging.useSandbox" to true))
    
      // assume unknown, adapt to your needs.
      MobileCore.setPrivacyStatus(MobilePrivacyStatus.UNKNOWN)
    }
    

    The above code does the following:

    1. Registers the required extensions.
    2. Configures MobileCore and other extensions to use your tag property configuration.
    3. Enables debug logging. More details and options can be found in the .
    4. Starts lifecycle monitoring. See Lifecycle step in the tutorial for more details.
    5. Sets the default consent to unknown. See Consent step in the tutorial for more details.

Ensure you update MobileCore.configureWith(environmentFileId) with the environmentFileId based on the Environment File ID from the tag environment you are building for (development, staging, or production).

SUCCESS
You have now installed the necessary packages and updated your project to register the required ۶Ƶ Experience Platform Mobile SDK extensions that you are going to use for the remainder of the tutorial.
Thank you for investing your time in learning about ۶Ƶ Experience Platform Mobile SDK. If you have questions, want to share general feedback, or have suggestions on future content, share them on this

Next: Set up Assurance

recommendation-more-help
9fed61f5-c338-47ad-8005-0b89a5f4af8b