Adobe Analytics

nitesh__anwani · 5/28/25

Hi folks,

We recently migrated our app's Adobe Analytics implementation from the legacy Adobe Mobile SDK to the newer Adobe Experience Platform (AEP) SDK.

During testing, we observed a significant change in how visitor IDs are tracked. Previously, visitor identity was maintained using the AID (Analytics ID), whereas the AEP SDK now uses the MID (ECID).

This has introduced a challenge in app update scenarios:

Existing users have an AID from the previous SDK.
After updating to the new version of the app, they are assigned a new MID.
In the first call after the update, both the old AID and the new MID are passed together. (In some case we do observe that the AID is passed in all hits along with the MID)

However, when analyzing the data for the test session, it appears that these are being counted as two separate unique visitors, resulting in a discrepancy in the unique visitor count for returning users.

I came across Adobe documentation that explains how a similar issue is managed on the web using s_vi cookies, but I couldn’t find any guidance on how this is handled in mobile apps using the AEP SDK.

Any insights, recommendations, or experiences on how to properly manage this transition and maintain continuity in visitor identification on mobile would be highly appreciated.

Thanks in advance!

-Nitesh

gautham_madala · 5/28/25

To address this, Adobe provides an idMigrationEnabled setting in the Web SDK to facilitate the transition by reading existing visitor ID cookies. However, for mobile applications, there isn't a direct equivalent setting in the AEP Mobile SDK. The AEP Mobile SDK generates a new ECID upon installation or when the app is updated, and this ID is stored in the device's persistent memory. If the app is uninstalled or the ECID is reset (e.g., via the resetIdentities API), a new ECID is generated.