Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

trackAction in mobile app is causing pageViews to increment

Avatar

Level 2

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);

 

Screenshot 2021-01-20 at 18.28.55.png

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

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

View solution in original post

0 Replies

Avatar

Level 2
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.

Avatar

Correct answer by
Employee Advisor

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

Avatar

Level 2

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?

Avatar

Employee Advisor
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.