Guidance Needed: Migrating from Tealium to Adobe SDKs with Two Different Org IDs (AA v5 + AEP) | Community
Skip to main content
Level 4
June 15, 2026
Solved

Guidance Needed: Migrating from Tealium to Adobe SDKs with Two Different Org IDs (AA v5 + AEP)

  • June 15, 2026
  • 3 replies
  • 152 views

Body:

Hi everyone, We’re in the middle of migrating our mobile apps from Tealium to Adobe’s mobile SDKs, and we’ve run into a challenge with Org IDs that I’m hoping to get some guidance on.

Current Setup

We currently have two different Adobe Org IDs in use:

  1. Adobe Analytics v5 SDK (Legacy)

    • Data flows directly into Adobe Analytics

    • Uses Org ID #1

  2. AEP Mobile SDK (New)

    • Data flows into Adobe Experience Platform

    • Uses Org ID #2

The Problem

During the migration, we need both data streams to continue:

  • Data must still flow into Adobe Analytics (Org ID #1)

  • Data must also flow into AEP (Org ID #2)

However, since the AEP Mobile SDK is tied to a single Org ID, we’re unsure how to architect the migration so that both systems receive the same events.

Questions

  1. Is it possible to send events to AEP using MobileCore.trackAction / sendEvent, and then use Event Forwarding to route those events into Adobe Analytics (Org ID #1)?

  2. Is this the recommended approach for customers who need to support two Org IDs during a transition period?

  3. Are there any limitations or known issues with forwarding AEP events to Adobe Analytics via Edge + Event Forwarding?

  4. Is there any alternative best‑practice approach for dual‑Org setups during migration?

We need to maintain data continuity in both systems until the migration is fully complete, so any guidance or architectural recommendations would be greatly appreciated.

Thanks in advance for your help.

Best answer by Jennifer_Dungan

There is.. but it’s not terribly clear… the biggest issue I had was the fact that it was like “find the item you want and add it”… great… there’s multiple items with similar names, which one should I be using??

 

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/home

 

 

I haven’t specifically seen anything showing a clear migration from trackState / trackAction to SendEvent; but at least that principle is clearer… rather than distinguishing between the type of calls in the code, the data that is sent is actually the determining factor.

 

https://experienceleague.adobe.com/en/docs/experience-platform/collection/js/commands/sendevent/overview

 

 

 

Here is also a Mapping Document for the XDM Object that will be helpful;

https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/xdm-var-mapping

 

So for instance… a “State” (i.e. Page View” would pass traditional “page” data (xdm.web.webPageDetails.name or xdm.web.webPageDetails.URL), whereas an “Action” would have “interaction” values (xdm.web.webInteraction.type, xdm.web.webInteraction.name, xdm.web.webInteraction.URL)

Of course there are grey areas, as in, in both my web and mobile app implementation, I have the server value on ALL calls (xdm.web.webPageDetails.server) - in my case, I am not using the XDM Schema, but mapping it with Context Variables, but the underlying principal is the same.

 

Adobe Analytics calculates a “page view” when it has a pageName or pageURL… I am not sure about CJA, but I would expect it to be similar, or maybe it finally has a dedicated event. This you will have to test to make sure your actions aren’t inflating anything.

3 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 15, 2026

Hi ​@jaishal,

I haven’t dealt with this scenario, but it sounds extra tricky…

 

Have you talked to your account reps to see if Adobe has thoughts on how to handle this? I am surprised no one flagged this as an issue when the decision was made to set up a new org…

If you can’t get help from your account reps, you could also try reaching out to client care… 

 

Event forwarding sounds like a logical solution.. though expensive… but you may not have many other options…. I wonder if you could also set up a custom solution using the Ingestion API to send data to your AA implementation (without relying on the SDK)? I feel that no matter which solution you choose, you will basically be re-doing your Adobe Analytics (Org 1) implementation and it will require a full regression test… 

 

Good Luck!

jaishalAuthor
Level 4
June 22, 2026

Okay can you help with the below:
 

One of our apps is currently using Tealium SDK and we are in process of migration to AEP SDK. What are the things to keep in mind? Also this is the first time us using XDM schema so can you please guide us on that and also share some articles for migration and AEP XDM schema

Currently, they use

Analytics.sharedInstance.trackView(withTitle: Analytics.Screens.contactInformation, section: AppSections.home)

analytics.trackEvent(withTitle: Analytics.Actions.EbillCapture.performEBillEnrolAction)

 

Most probably will replace the above functions with sendEvent function but will appreciate your guidance on it

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 22, 2026

I will try to do what I can… we did replace our trackState/trackAction with Send Event (so we didn’t use the Edge Bridge. Also note, we don’t have Tealium, we just did a simple migration from the old ACP SDK to the AEP SDK.

 

For us, we did this because there was a few things that the XDM Stream supported that the older SDK and the track State/Actions didn’t support. But, as I said, we didn’t want to redo everything so we did a bit of a hybrid approach.

 

The first thing I need to ask… Do you plan on having CJA in the future? We have no such plans in the immediate future, so we could continue to leverage most of our original implementation (i.e. Context Variables).

But every implementation is different, and your specific needs may determine a different approach.

jaishalAuthor
Level 4
June 22, 2026

Is there any documentation of any sample schema’s created for mobile? Articles on migration from trackState/trackAction calls to send event calls?

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
June 22, 2026

There is.. but it’s not terribly clear… the biggest issue I had was the fact that it was like “find the item you want and add it”… great… there’s multiple items with similar names, which one should I be using??

 

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/home

 

 

I haven’t specifically seen anything showing a clear migration from trackState / trackAction to SendEvent; but at least that principle is clearer… rather than distinguishing between the type of calls in the code, the data that is sent is actually the determining factor.

 

https://experienceleague.adobe.com/en/docs/experience-platform/collection/js/commands/sendevent/overview

 

 

 

Here is also a Mapping Document for the XDM Object that will be helpful;

https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/xdm-var-mapping

 

So for instance… a “State” (i.e. Page View” would pass traditional “page” data (xdm.web.webPageDetails.name or xdm.web.webPageDetails.URL), whereas an “Action” would have “interaction” values (xdm.web.webInteraction.type, xdm.web.webInteraction.name, xdm.web.webInteraction.URL)

Of course there are grey areas, as in, in both my web and mobile app implementation, I have the server value on ALL calls (xdm.web.webPageDetails.server) - in my case, I am not using the XDM Schema, but mapping it with Context Variables, but the underlying principal is the same.

 

Adobe Analytics calculates a “page view” when it has a pageName or pageURL… I am not sure about CJA, but I would expect it to be similar, or maybe it finally has a dedicated event. This you will have to test to make sure your actions aren’t inflating anything.

manpreetkaur27
Adobe Support
Adobe Support
July 8, 2026

Thanks for sharing the documents, ​@Jennifer_Dungan 

manpreetkaur27
Adobe Support
Adobe Support
July 1, 2026

Hi ​@jaishal 
If the query has been addressed, please consider marking a best answer so it could help others who have a similar concern in the future.