Adobe Experience Platform Mobile SDK

First of all, I would like to congratulate those who have successfully migrated their tag management system from DTM to Tags (formerly Adobe Launch). And those who have not should treat this as one of their top priority engagements because you can no longer create new properties in DTM, even your existing ones will soon turn to read-only, and later, DTM servers will be put to sleep.

Now, the next big thing which lies on our path is migrating mobile implementation from Mobile SDK v4 to AEP Mobile SDK as Adobe has announced the end of support for the Mobile SDK v4.

As per Adobe:

Support for the Mobile version 4 SDKs will end on August 31, 2021.

Now is the time to get your ducks in a row and start planning to migrate your mobile implementation to this brand new AEP Mobile SDK.

Adobe Experience Platform Mobile SDK goes by various names such as Mobile SDK v5, AEP Mobile SDK, Launch Mobile SDK, etc.

AEP Mobile SDK gives customers an easy to configure and implement solution to power their entire mobile lifecycle. Along with Experience Platform Launch, it lets customers seamlessly integrate Adobe solutions such as Adobe Campaign, Audience Manager, Analytics, and Target, as well as third party solution using extensions.

How should one pick up and get started with it? I am going to publish a series of blogs to share the knowledge on how to implement and debug the new SDK.

The plan is to publish three blogs to cover all the basic aspects of mobile app tracking, such as configuration, implementation and debugging.

This mini-series is going to comprise of following blog posts:

1. Blog 1: Configuring and implementing AEP Mobile SDK
   • Launch configurations
   • Install Mobile SDK in your app
   • Start tracking data
     • Lifecycle
     • States and Action
   • Map variables via processing rules
2. Blog 2: Using Tags as a TMS in Mobile Apps with AEP SDK
   • Using rules to attach context data
   • Using data elements
3. Blog 3: Configuration and Debugging with AEP Assurance (formerly Project Griffon)

A few things to note while going through these blogs:

1. I am going to use Adobe’s Bus Booking Android sample app for demo purposes, the reason being simplicity. I wanted to keep it as simple as possible from a code perspective.
2. Consider this post as an index or jump point to the rest of the blogs, which I am going to publish soon, one by one.

Finally, I must say, I am quite excited to kick off this series, and I hope you will like it. I will try my best to cover up as maximum as possible, yet keeping it concise and not boring.

Happy Mobile Tracking!