trackAction in mobile app is causing pageViews to inc...

[fredrambert]

Hi All, 

has anyone else run into issue where trackAction calls are incrementing pageviews ? 

final Map<String, Object> contextData = new HashMap<String, Object>() {{
put(Key.SCREEN_NAME, screenName);
put(Key.SECTION, section);
put(Key.DLC_CLICKED, true);
put(Key.DLC_FILE_TYPE, content.getExtension());
put(Key.DLC_NAME, content.getTitle());
put(Key.DLC_PROPERTY_ID, placeId);//content.getPlaceId());
}};
trackAction(action, contextData);

[ankitnagarsheth]

You can explicitly set the mapping on https://mobilemarketing.adobe.com/ so that contextData variable is mapped to eVar/prop/event. More info at https://experienceleague.adobe.com/docs/mobile-services/android/analytics-android/actions.html?lang=... 

[fredrambert]

Hi Ankit. thanks for the note. I'm not sure this identifies the issue we are having though. Basically, we are triggering trackAction, however as you can see above, these actions are also triggering page views. This doesn't seem right as we expect that only trackState would increment page view counter.

[Khurshid_Alam · Accepted solution]

Check if a processing rule is setting Page Names. If Page Name is set in processing rules, custom link increment page views.

[fredrambert]

Thanks Khurshid. That was indeed the issue.

[tcrewes1]

Thanks Khurshid_Alam, this explains a lot. Do you know why this is the case? It seems odd to add a pageView to a track Action just because PageName gets set? I haven't seen this in the documentation anywhere. Is there anywhere this is referenced?

[Khurshid_Alam]

Page Name is stripped off from hits with custom links. Since you are adding a Page Name, you are actually asking the servers to add a Page View. This is indeed not documented. I stumbled upon this behavior while troubleshooting a similar issue.

[tcrewes1]

Thanks @Khurshid_Alam, that's good to know for the future. Appreciate your help.