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

Unintended extra pageviews using WebSDK

Avatar

Level 4

Hello gang... We've been running with the WebSDK for a bit now and all has seemed just fine. We've been impressed with the performance as well as the relative ease of implementation. Note that we use the NPM module directly, incorporated into our front-end build process.

 

Throughout testing as well as live data in Analytics nothing has seemed amiss. However in looking at our raw Data Feeds out of Analytics, there are extra "phantom" hits that are being treated as pageviews. There are few if any actual variables set in the Data Feed for those rows, except for some default Adobe ones like page URL, hit time, etc.

 

And when looking at just raw pageviews in Workspace with no reporting dimensions or segments applied, they can be seen. Our pre-implementation testing and evaluation never included just looking at data this way.

 

Unfortunately it looks as though these phantom pageviews correlate almost perfectly with the extra calls we make to just retrieve personalizations from Target. It seems that even though I don't set xdm.web.webPageDetails.pageViews.value, the hit is still being treated as such.

 

Is this in fact the case? And if so, is there some way to stop this from happening. It is absolutely undesirable. A pageview should ONLY be registered in Analytics if it is explicitly stated as such in the XDM.

 

1 Accepted Solution

Avatar

Correct answer by
Level 4

Here is the recommended short term solution, intended to be used as part of the alloy onBeforeEventSend callback. I've just implemented something based on this and it has alleviated the extra pageviews for now, throwing the "phantom" hits into the Custom Links report

https://gist.github.com/jfkhoury/b390688267854c75d75245ed0c12253b

View solution in original post

7 Replies

Avatar

Community Advisor

This definitely sounds like a bug with Web SDK. You should bring this up with Adobe Client Care. They can then get the Web SDK product team to look into it with their Analytics colleagues to fix it.

Avatar

Level 4

@jgrubbs I faced a similar issue. AA was counting a page view even when I had not set "web.webPageDetails.pageViews.value" as '1'. I think this is because AA fires a page view event if pageName is present. I am going to try and remove the page name value in those "phantom" calls and give it a try. Let me know if you could get rid of that in the Target call and whether it makes a difference.

Avatar

Level 4

Hi there... Yeah I did confirm it was the Target calls generating the extra pageviews.

 

I tried setting tinkering with the pagename, both by ensuring that xdm.web.webPageDetails.name was undefined and even setting up a processing rule to delete Pagename, neither of which was successful unfortunately.

 

I tried setting xdm.web.webPageDetails.pageViews.value to 0 and even -1, both of which failed as well.

 

I've been in contact with Adobe and our CSM, and have been informed that a fix is in the works. There is a short term solution available as of this morning which involves transforming these hits into webInteractions. That of course will not stop us from using up our contractual server calls, but it does at least prevent the accumulation of these unwanted pageviews.

 

Avatar

Correct answer by
Level 4

Here is the recommended short term solution, intended to be used as part of the alloy onBeforeEventSend callback. I've just implemented something based on this and it has alleviated the extra pageviews for now, throwing the "phantom" hits into the Custom Links report

https://gist.github.com/jfkhoury/b390688267854c75d75245ed0c12253b

Avatar

Level 1

Hi, where do we set this page view event in? which code? I have multiple page load rules and custom link rules?