Troubleshoot your discrepancy

Step 1

Are you seeing a data discrepancy between Parse.ly and another tool (e.g. Google Analytics, Adobe Omniture) for post traffic or video traffic?

Post traffic. Video traffic. Both.

Step 2

Is the discrepancy related to pageviews and unique vistors or referrer data?

Pageviews or unique visitors. Referrer data.

Step 2

Is the issue related to the number of video starts or engaged time?

Video starts. Engaged time.

Solution

Troubleshoot the post traffic discrepancy first. Once that's resolved, move onto troubleshooting the video traffic discrepancy.

Step 3

Is the number of pageviews or unique visitors in Parse.ly higher or lower than in the other tool?

Higher. Lower.

Step 3

Is Parse.ly displaying more direct traffic than the other tool?

Yes. No, I'm having another issue.

Solution

In your browser, open the pages featuring the affected video. Follow these instructions (note: search for a videostart instead of a pageview) to verify that a videostart fires for the video and that the metadata associated with the videostart is accurate.

After that, verify the videostarts are firing with the correct metadata on pages where the video is autoplayed as a part of a queued loop. This ensures that the videostart will be associated with the correct data, regardless of video's position is in the loop.

If the problem persists, please here contact our support team.

Solution

When engaged time for a video seems higher or lower than expected, it's usually because trackPlay and trackPause events haven't been implemented correctly. Please check that these events are firing accurately by consulting these help docs. If they are and the problem with engaged time persists, contact our support team.

Step 4

Follow the instructions in this help doc. Can you confirm that only a single pageview is firing on the pages where see the discrepancy?

Yes, only one pageview is firing. More than one pageview is firing.

Step 4

Follow the instructions in this help doc. Can you verify that pageviews are firing properly on the pages where you see the discrepancy?

Yes, pageviews are firing properly. No, pageviews aren't firing properly.

Solution

Sounds like we need to get a human involved. Please contact our support team.

Step 4

Do you have Google AMP or Facebook Instant Articles (FBIA) pages that should be tracked in Parse.ly and included in the number of pageviews or unique visitors?

Yes. No.

Solution

Please double check that the Parse.ly tracking script 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.

Solution

It sounds like dynamic tracking hasn't been properly implemented, resulting in the Parse.ly JavaScript tracker firing multiple pageviews when it shouldn’t be.

Please consult our integration help docs to make sure dynamic tracking is set up correctly. If that doesn't solve the problem, contact our support team.

Solution

Sounds like we need to get a human involved. Please contact our support team.

Solution

Sounds like we need to get a human involved. Please contact our support team.

Solution

Sounds like we need to get a human involved. Please contact our support team.

Solution

Please check our help docs to make sure AMP and FBIA tracking is implemented correctly. If the problem persists despite fixes to FBIA and AMP tracking, please contact our support team.

Thanks for your question, we will get back to you shortly!
Do you have an urgent support question?