Configuring and Implementing AEP Mobile SDK
This article is the 1st post of the AEP Mobile SDK blog series.
Through this post, we are going to cover the steps one needs to configure and install the new AEP Mobile SDK. I will also conduct a deep-dive on mobile data tracking APIs. After going through this blog, you will be able to:
Alright, let’s get started.
1. Configure Mobile property in Tags
- Log into Experience Cloud > Tags > Create a “Mobile Type” Property
- Give it a name e.g. “Sandbox Mobile Tracking” and save it.


- Install Adobe Analytics Extension, and provide valid report suites and tracking server information.
Note: Do not install Adobe Analytics Mobile Services Extension.


- Now, create a library, and add your resources in it and build it.
2. Install Mobile SDK v5 in your app
- Once you have built your library, go to the environments tab in Tags.


- Copy Gradle dependencies and paste it in Gradle Scripts folder > build.gradle (Module:bus) > Inside dependencies { } > Sync.


- Now, copy the Initialization code and paste it in your main class:
- Import all the dependencies at the top,
- MobileCore functions inside onCreate() and Register Extensions snippet inside try{}.
Note: Adobe recommends to import SDKs, and register extensions as early as possible during the app launch process. Hence, our initialization code should go in main class, not in main activity.


3. Track data into Adobe Analytics
- To track Lifecycle data, you need to invoke the following APIs:
- To track data into Adobe Analytics standard and propriety variables like pageName, eVar, prop, etc. you’ll need the following APIs:
- The last step is to map your context data variables with your Adobe Analytics variable via processing rules. Following screen grab shows how one should do it.


Isn’t configuring AEP Mobile SDK simple?
These simple and straightforward steps will let anyone quickly configure their mobile property in Tags, install it on the app, and track data in Adobe Analytics. From here, you can take your implementation to a whole different level, depending on your project and business requirements.
That’s it from this blog, and in the next one, I will deep dive more into Tags and cover its advantages over Mobile SDK 4.x.
You can also check out the recording of the webinar, we recently held, on migrating mobile implementation from SDK 4.x to new AEP Mobile SDK.
I hope you enjoyed this blog, and should you have any questions, let us know by emailing us at info@softcrylic.com.