Expand my Community achievements bar.

SOLVED

Account Type segments from web property is showing up in Mobile App, but Mobile App doesn't have those segments available

Avatar

Level 1

Hi all, 


For our mobile app, when we pull data showing unique visitors based on Account Type, we have segments pulling in from the web property as well, but those segments are not available on mobile app. The mobile app allows you to log in/identify as only a user, co-user, or third party. The other segments of customer & agent are used on different web properties. 

See this chart as an example.

 

Mobile AppUnique Visitors
Account Type100,002
User (mobile app)75,000
Co-user (mobile app)20,000
customer (other web properties)4,800
3rdparty (mobile app)200
agent (other web properties)2


How would visitors from other web properties show up under Account Type in mobile app data? Account Type is used across web properties and mobile app, but wouldn't the data be separated out before it got to Analytics? If we just filter out the other web data that is not a part of mobile app, would we be missing any insights? The data is considerably less, but would this be an indication of users going from web to mobile app or vice-versa? 

Thank you for any insight you have! 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Unfortunately, this sounds like it will require a deep dive testing session to look at all your tracking calls and trying to figure out where the problem exists...

 

If you are using processing rules, there could be a problem there that is corrupting data, or something could be tracking incorrectly in either your web (identify as mobile app incorrectly) or in your mobile app... 

 

In short, without seeing your implementation and setup, it will be very hard for us to identify the issue... 

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Unfortunately, this sounds like it will require a deep dive testing session to look at all your tracking calls and trying to figure out where the problem exists...

 

If you are using processing rules, there could be a problem there that is corrupting data, or something could be tracking incorrectly in either your web (identify as mobile app incorrectly) or in your mobile app... 

 

In short, without seeing your implementation and setup, it will be very hard for us to identify the issue...