User ID for mobile App | Community
Skip to main content
F
fern1
Level 5
November 23, 2022
Solved

User ID for mobile App

  • November 23, 2022
  • 1 reply
  • 3318 views

Hi!
Today I have a question regarding the User ID for the mobile App.

For our websites, we are using the experience cloud ID plugin and created a user ID evar, to get the ID using data layer (after the user login). 
However, how can we also get the ID from an app? Our dev team already did the setup so the app is sending us the ID but I don't know how to config it on the Adobe side since there is no experience cloud if plugin for mobile app. 
Should I also create an eVar for that and create a rule and data element for it in launch?

thanks in advance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jennifer_Dungan

Upon re-read, I was thinking you were asking about the user's MID / ECID... or are you actually talking about your user authentication id? You can have your developers set that value into a context variable and map it to your eVar.

 

Are you sending both Web and App traffic into one global suite? There is no need to set up a new eVar to track the User ID, you can map it into the same eVar.

 

One thing that I did is set up contextual eVars that I can use to create segments of data... such as "Experience" - on the website, I can pass "web" on the app I can pass "app" (these values are sent on all page views and actions)... so I can see all my data together in the global suite, but I have segments to see "web only" data, and "app only" data. I can use these as Virtual Report Suites, but I also use them in my Workspace segment dropdowns, or I use them in columns to visualize data side by side.

 

If you have the ability to easily separate the data, you definitely should be mapping the same data into the same eVars whether coming from the website or from the app (or from any other variant, like AMP)

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 23, 2022

Yes, this one is a bit baffling to me too... while the app is sending the MID value to the tracking server, you can't actually access it directly (or map the value into an eVar using processing rules).

 

I had our developers grab the MID value, set in in a context variable, and mapped that to a custom eVar with processing rules.....

 

However, you should be aware, that like a user using multiple browsers, the MID is going to be set to a different value in the website and in the app, even when accessing from the same device...

 

There is a way to append the mobile app MID to URL from the app, so that if the website is opened from the app (external link, or maybe an in-app webview) you can forcibly override the MID on the website to match the App (but there is no way to send the web MID to the app at this time.. it's only in one direction)

 

https://aep-sdks.gitbook.io/docs/foundation-extensions/mobile-core/identity/identity-api-reference#appendtourl-appendvisitorinfoforurl

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
November 23, 2022

Upon re-read, I was thinking you were asking about the user's MID / ECID... or are you actually talking about your user authentication id? You can have your developers set that value into a context variable and map it to your eVar.

 

Are you sending both Web and App traffic into one global suite? There is no need to set up a new eVar to track the User ID, you can map it into the same eVar.

 

One thing that I did is set up contextual eVars that I can use to create segments of data... such as "Experience" - on the website, I can pass "web" on the app I can pass "app" (these values are sent on all page views and actions)... so I can see all my data together in the global suite, but I have segments to see "web only" data, and "app only" data. I can use these as Virtual Report Suites, but I also use them in my Workspace segment dropdowns, or I use them in columns to visualize data side by side.

 

If you have the ability to easily separate the data, you definitely should be mapping the same data into the same eVars whether coming from the website or from the app (or from any other variant, like AMP)

    F
    fern1Author
    Level 5
    November 24, 2022

    Hey Jen!
    I was referring to the user authentication id.

    We do have a global suite but I just realized that it does not allow mobile app data, how can I change that? On data collection when I try to add the global report suite to the app property says that the report doesn't support mobile data. 

    Meanwhile, I´m trying to get the user ID directly on our app report suite. I created an eVar for that but how can I set its processing rule? is this correct? our dev team set up the user Id as a trackAction and named it "userid" 
    userid: (userid do user)

     

     

    Terms & ConditionsAccessibility statement

    Loading footer...