Level 2

Solved

Abobe SDK for mobile - screenview

Forum|Forum|7 months ago
July 29, 2025
2 replies
1417 views

Hello,

Does anyone know the proper way to track screenviews in a mobile sdk implementation?

We are using edge, datastreams, and schemas. We need to track screenviews and clicks in adobe analytics.

I see the recommended event types for web clicks and web pageviews in the documentation, but nothing for mobile.

We successfully see our props and eVars in the report suite, but no "visits" or "pageviews"

- Should I follow the event type recommendations for web?

- Do I have to send an event, such as event1 to get a screenview?

Analytics

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

In Adobe Analytics, they really don't distinguish "page view" from "screen view"... the verbiage is shared for web and apps.

Your App data should look just like your Web data, with a few differences.

For one, your mobile app should be setting an "App ID" (something that doesn't exist on your website).

In our implementation, I use dimensions to help give context to the traffic..

Responsive Breakpoint - in this I track the breakpoint experience... so on web, I will track the "desktop", "tablet", "mobile" breakpoints, then I added "app|mobile" and "app|tablet" into our apps
Site Type - for context, we have a lot of subdomains that support extended content... so I track values like "core", "obituaries", "classifieds", etc, for our apps, I use "app"

I make sure that ALL dimensions match the data (values / formatting / etc) between web and app, so that everything properly rolls up into the same row for reporting.

Using these, I can separate our web traffic from our mobile app (I could also use the existence of "App ID").

- Should I follow the event type recommendations for web?

Yes, I can literally take our web calls and app calls and look at them side by side, and they will match (aside from obvious data differences)

- Do I have to send an event, such as event1 to get a screenview?

Only IF you are using a custom event on web in addition to standard PV metric. As in, I would match your web as close as possible.

Now, I do realize that your app and web may have slightly different features or behaviours.... such as "swipe left and right" to get to additional content, or maybe changing dark mode, font size, etc.... these are the things that you will have to create "App Only" dimensions or actions to track.. but it shouldn't be too hard to figure out the similarities and differences and determine the best way to track those differences while joining the similarities for everything else.

Jennifer_Dungan

Accepted solution

Community Advisor and Adobe Champion

In Adobe Analytics, they really don't distinguish "page view" from "screen view"... the verbiage is shared for web and apps.

Your App data should look just like your Web data, with a few differences.

For one, your mobile app should be setting an "App ID" (something that doesn't exist on your website).

In our implementation, I use dimensions to help give context to the traffic..

Responsive Breakpoint - in this I track the breakpoint experience... so on web, I will track the "desktop", "tablet", "mobile" breakpoints, then I added "app|mobile" and "app|tablet" into our apps
Site Type - for context, we have a lot of subdomains that support extended content... so I track values like "core", "obituaries", "classifieds", etc, for our apps, I use "app"

I make sure that ALL dimensions match the data (values / formatting / etc) between web and app, so that everything properly rolls up into the same row for reporting.

Using these, I can separate our web traffic from our mobile app (I could also use the existence of "App ID").

- Should I follow the event type recommendations for web?

Yes, I can literally take our web calls and app calls and look at them side by side, and they will match (aside from obvious data differences)

- Do I have to send an event, such as event1 to get a screenview?

Only IF you are using a custom event on web in addition to standard PV metric. As in, I would match your web as close as possible.

Now, I do realize that your app and web may have slightly different features or behaviours.... such as "swipe left and right" to get to additional content, or maybe changing dark mode, font size, etc.... these are the things that you will have to create "App Only" dimensions or actions to track.. but it shouldn't be too hard to figure out the similarities and differences and determine the best way to track those differences while joining the similarities for everything else.

B

BertBruAuthor

Level 2

Thank you so much for your response! Here's more context

This report suite will only have mobile data, so we don't need to differentiate. I just wanted to know how to properly send the mobile data. Good to know that we can follow the recommendations for web
We are more than happy to stick to the _experience schema.
I came across this (screenshot below and link here:https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/overview#:~:text=To%20properly%20handle%20page%20views%20and%20link%20events%2C%20the%20following%20logic%20is%20applied%20to%20data%20send%20to%20the%20Adobe%20Experience%20Edge%20network%20and%20forwarded%20to%20Adobe%20Analytics.) Where it seems like it's referencing something outside of the _experience schema
- It looks like the above is referencing this field group outside of _experience
- I see a similar one inside of experience
- Also eventType is completely outside of the _experience tree, so I am completely confused about that.
- Sorry for the layered questions, this shows my level of confusion.

Jennifer_Dungan

Community Advisor and Adobe Champion

Okay I am back with more question.

if i send a custom xdm structure from the map, can I map it to evars and props or are there rules to follow?

Asking because the map below in my datastream doesnt work (didnt show up in reporting)

programDetails.degreeLevel

=>

_experience.analytics.customDimensions.props.prop33

but this worked (showed up in reporting)

_experience.analytics.customDimensions.props.prop35

=>

_experience.analytics.customDimensions.props.prop35

Don't hold me to this, but from my understanding, yes, you should be able to map it...

Interesting... I mean, I will be honest, I haven't don this myself..

I have some questions for you though:

1. Are you only using AA or do you also have, or plan to have CJA?

2. If the answer to question 1 is "just AA, no plans for CJA", are you just trying to get your mobile app to track to AA using the newest AEP SDK? And you are trying to find the easiest path to that end?

If you are just using AA, and are trying to get data into AA easily (also taking your comment from https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-questions/how-to-map-json-from-mobile-sdk-to-adobe-evars-props-and-events/m-p/767437#M58431 as part of my understanding), then I may have some very good news / info for you, using the same model we're about to implement for AA in our mobile apps.... however, it's definitely not designed for CJA.....

FarazHusain

Adobe Employee

Apart from what @jennifer_dungan mentioned, you can check out this particular documentation - https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/initial-configuration/create-schema

Basically you have to setup a custom field group as defined above and then https://experienceleague.adobe.com/en/docs/platform-learn/implement-mobile-sdk/app-implementation/events and add something like below:

This is a good documentation for tracking screen views for Mobile SDK implementation using Edge, but this one is for iOS; a similar setup would be for Android. I have tried and tested this one, and it works.

Jennifer_Dungan

Community Advisor and Adobe Champion

Lol, I should have mentioned that we are using the data.__adobe.analytics model rather than the full XDM Schema!

Since we are not likely to have CJA anytime soon, we decided to not redesign everything and stick with our context variables and processing rules....

So there is no separate model in that... I don't know if using the Analytics Bridge (so that you can continue using trackState and trackAction) would also result in not having the separate app schema....

FarazHusain

Adobe Employee

Yes, if we use Analytics Bridge/Edge Bridge, one can continue to send the data via trackState and trackAction APIs, and in the case of Edge Bridge, the schema setup is optional.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded