Include MobileAppID in LiveStream API | Community
Skip to main content
R
RobMulcahy
Level 1
March 18, 2026
New

Include MobileAppID in LiveStream API

  • March 18, 2026
  • 1 reply
  • 5 views

We have one app and several web properties tracked in abobe analytics. 

We use the LiveStream API to push our app and web data into an external repo. 

Mobile App ID is, in my opinion, the easiest and quickest way to segment out traffic to/within the app from the web properties.

But Mobile App ID is not one of the fields sent in the Livestream API! 

Please do the engineering work to change that and include mobileappID in the livestream. 

You may be saying to yourself, now why don’t you just track them in separate report suites.. great question! I didn’t make the decision to combine them in the same suite - that predates my time here. 

    1 reply

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    March 19, 2026

    Lol, I would never tell you to track your apps in a separate report suite… I am a true supporter of the “global suite”.

     

    I noticed the same thing on our implementation… I thought it was something we did, since we are using the Adobe Analytics Data model and not the full XDM…

     

    However, I worked with my developers to map that data in.

     

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

     

    xdm.application.version

     

     

    Now, in my case, I am using Processing Rules still to set all my dimensions… and ALL my rules were around the legacy “if a.appid is set”… which was a problem with the new designation…. so I just created a new rule at the top for “if a.x.application.name is set” then set the value of a.appid to a.x.application.name.. 

    I mention this in case you have a similar set up.

     

     

    Also, I have additional “lookup” dimensions that help support my global tracking.

    I have:

    • Responsive Breakpoint - which tracks desktop, mobile or tablet on web (based on the screen width) and app|mobile or app|tablet in our apps
    • Site Type - which tracks the “core” site, or the “app”, or any number of our offshoot (I work for a newspaper so we have an Obituaries subdomain, and a Classifieds subdomain and a Games subdomain, etc)

    So, while I can use the existence of the App ID to determine the mobile app, I also have other fields that I can rely on (and use to double check data integrity)

     

    Now, this isn’t something you can just throw into place in your implementation.. you will have segments and logic already created around the App Id, and ensuring that this information is collected is of utmost importance. And I agree, it should be there by default, so a big upvote from me… but in the meantime… you may have to take matters into your own hands.

      Terms & ConditionsAccessibility statement

      Loading footer...