Data Discrepancy

Last updated 7 years ago

First published 02 October, 2017

work

English Rating: ALL ages Shortest path: 3 nodes Longest path: 13 nodes Possible solutions: 13

Uday Varkhedkar

Are you seeing a data discrepancy between Parse.ly and another tool (Google Analytics, Adobe Omniture, etc.) for post traffic or video traffic? Video Traffic. Both. Post Traffic.
Start troubleshooting the discrepancy with post traffic. Once the post traffic discrepancy is resolved, we can help you troubleshoot video traffic discrepancies..
Is the discrepancy realted to pageviews/unique visitors or referrer data? Referrer Data. Pageviews or Unique Visitors.
Do the pageview or unique visitors numbers seem higher or lower than they should be on Parse.ly? They seem higher than expected. They seem lower than expected.
Can you verify that only a single pageview is firing on the pages you are seeing a discrepancy using the directions here (https://www.parse.ly/help/post/4332/can-confirm-site-sending-pageviews-parse-ly-2/)? Yes, only 1 pageview is firing. More than 1 pageview is firing.
Please contact our support team here..
Is dynamic tracking (as described here: https://www.parse.ly/help/integration/dynamic/) implemented on the page? Yes, dynamic tracking is implemented on the page. No, the page is using the standard tracking integration.
It is likely that dynamic tracking has been mis-implemented and as a result is firing multiple pageviews when it shouldn’t be. Please try to address the issue using the documentation found here (https://www.parse.ly/help/integration/dynamic/). If the problem persists, please contact our support team here..
Please contact our support team here..
Can you verify that pageviews are firing properly on the pages you are seeing a discrepancy using the directions here (https://www.parse.ly/help/post/4332/can-confirm-site-sending-pageviews-parse-ly-2/)? No, pageviews aren’t firing properly. Yes, pageviews are firing properly.
Please double check that the Parse.ly tracking script (found here: https://www.parse.ly/help/integration/basic/) is included and loading properly on the page, with the correct site-id value. If it is and issues persist, please contact our support team here. .
Do you have AMP or FBIA pages that should be tracked in Parse.ly and included in the number of page views or unique visitors? No. Yes.
Please contact our support team here.
Can you verify AMP and FBIA tracking with Parse.ly using the directions found here (YET TO BE WRITTEN)? Yes, AMP and FBIA pages seem to be tracking fine. No, FBIA and AMP articles are not showing up as described in the directions.
Please contact our support team here.
Please use these documents to ensure you have the correct tracking implementation of AMP and FBIA articles (AMP: https://www.parse.ly/help/integration/google-amp/; FBIA: https://www.parse.ly/help/integration/fbinstant/). If the problem persists despite fixes to FBIA and AMP tracking, please contact our support team here. .
Is Parse.ly displaying more direct traffic than the other tool? Yes. No, I am have another issue.
Please contact our support team here.
Are you using dynamic tracking or standard tracking for the page in question? Standard Tracking. Dynamic Tracking.
You can read more about how we track referrer data here (YET TO BE WRITTEN). If you believe that the issues go beyond the specific way we track referrer data, please contact our support team here..
You can find details on how to see the pageview event here (https://www.parse.ly/help/post/4332/can-confirm-site-sending-pageviews-parse-ly-2/). Please verify the urlref value in the pageview event as this determines the referrer associated with the pageview. If this looks fine, please contact our support team here. .
Is the issue related to the number of video starts or engaged time? The issue is related to videostarts. The issue is related to engaged time.
If you navigate to articles featuring the video and follow the directions here (https://www.parse.ly/help/post/4332/can-confirm-site-sending-pageviews-parse-ly-2/) (Note: Search for a ‘videostart’ instead of a ‘pageview’), check to see a videostart firing for the video and verify that the metadata associated with the video start is accurate. Additionally verify the videostarts are launching with the correct metadata on pages in which the video is autoplayed as a part of a queued loop. This will .
If engaged time for a video seems higher or lower than expected, it is likely related to ensuring proper use of the trackPlay and trackPause events detailed here (https://www.parse.ly/help/integration/video/#video-tracking-javascript-api). If the trackPlay and trackPause events seem to firing accurately and a problem with engaged time persists, please contact our support team here..