The Pfizer customer ID details of portal metrics are inconsistent with the total number, more detail please refer to attached picture:
Sign in to like this content
I think you are missing some details of your table:
"breakdown total number of Pfizer customer ID is 2653" - this isn't a correct statement... the first 5 rows (page 1 of 26) adds to 2653... you haven't counted the other 25 pages of results. The circled value at each level of the breakdown is showing the total for each breakdown and they all show the same thing, meaning there is no loss.:
To use a similar example, your table, showing 3 months of data, and a prop (rather than an eVar so that "unspecified" isn't returned) could result in the following totals:
For the visits, this could mean that users start their visit as not-logged in (unspecified) then log in during the visit. The Total at the top is de-duplicated data from your breakdowns and is completely expected in such a scenario.
A simple explaination... I come to your site and hit you "Home Page", then I also hit your "About Us Page", then I hit your "Contact US Page".
If you had a similar breakdown as above, but using Page (instead of user ids), you would have total Visits of 1 (since I did all actions in that one visit). But each page, because they are your breakout, would show a visit for each page..... you can't add the visit for each page together and expect to see a total of 3 visits.... that would over count your stats.
^ this is exactly what you should see if you were looking at my visit (as described above) individually.
Without knowing your implementation, that is nearly impossible for us to help with such a specific question.. However, we can offer you help in tracking it down.... what other data are you collecting on all your hits? You could try breaking that down by "page" to find the page it's being set on, or maybe you have an eVar tracking the full url, you could try that... However, be mindful of the expiry settings on your eVar, as you may end up looking in the wrong place if the eVar maintains the value through the visit... you might want to pair it with the metric "instance of eVar X" to get specifically where the value is being set.
The key is to identify where on your site "-1" is being set, then focusing testing in that area to determine what is going wrong. How are you pulling the ID? Are you extracting it from a cookie? Are your developers providing you with a data layer? Is there a chance that something is being set incorrectly and its coming to you... is it possible your code to process that ID, if the data isn't yet available is causing it to be sent to Adobe like this?
Since you are using an eVar, which by nature has a customizable "expiry" (i.e. hit, visit, week, etc) Adobe will populate your report with "unspecified" if there is absolutely no value. You can customize this behaviour in your report by using the filter (at the eVar level) and unselecting "Include unspecified (none)"
This is a personal choice and you may find it useful in some instances (like here where you are looking at your logged in user id, vs non-logged in)
The "-1" may also represent non-logged in users as you say, but somewhere in your implementation you are passing a literal "-1" value, and that is why this is showing up... See my points in #2 on how to track that down.. it may even be possible that the "-1" is coming from user who were logged in, then logged out? Again, without knowing your implementation we can only speculate on that.
Good luck tracking down that -1.
Sign in to like this content