This may sound a bit strange.. but do you have lifecycle metrics enabled
in your mobile app? I don't know if that will result in these results,
but I do know that the lifecycle metrics are tied to the mobile
launches, first launches, days since last launch, etc... it's possible
that the visit number for app uses these to calculate, and in their
absence it results in 0? The old SDK had lifecycle metrics enabled all
the time... the new SDK puts the power in your developers hands to
enable or not d...
Page views will be incremented each time a trackState for mobile SDK or
s.t() for analytics SDK are called. (AEP implementation will differ
tho). It also needs to be contain either the pageName or page URL or
both. If both are missing pageview will not be incremented.
As mentioned in previous reply, standard web page will send s.t() on
either Adobe pageBottom event or the DOM READY or PAGE LOAD ...
WOW! Thanks for letting us know... The data feed issue (with the
page_event) is likely more impacted when using something like the Media
Plugin... but this is really good to know. I will let our data team know
that this could be an issue in their processing (but we don't use the
Media plugin, we just did our own custom media events)
You're trending a row's numbers as-is. To AA, the "All Visits" column in
your table is just another metric column. It has no special meaning in
visualisations.A calculated metric might help you. Instead of using
"Page Views", create a calculated metric using the formula "Page Views /
Page Views Total". (For the denominator, you'll need to click the
metric's gear icon, then choose "Grand total".) If you use this
calculated metric, then you don't need the "All Visits" segment.
Do any of the answers below answer your initial question? If so, can you
select one of them as the correct answer? If none of the answers already
provided answer your question, can you provide additional information to
better help the community solve your question?