Google Chrome’s developer tools are your friend in this endeavor. To see whether or not Parse.ly pageviews are firing, navigate to one of your article pages in Chrome and open your developer tools by hitting Command + Shift + C on Mac or Ctrl + Shift + C in Windows/Linux. If you have an ad-blocker installed, make sure to disable it.
Click into the “Network” tab in Developer tools and filter for “action=pageview”. Then, refresh the page and see whether you see a pageview being sent (the request would begin “?rand=”). Click on the request and switch over to the “Payload” tab and look at the “Query String Parameters” section. You should see something like this:
Note that url and urlref values can’t be relative paths (e.g. “/article” as opposed to “https://www.example.com/article”)—they have to be full URLs.
Checking for videostarts
To confirm that you’re tracking videos correctly, follow a similar workflow: Filter for “action=videostart” in your developer tools, press play on a video in your browser, and see if a “?rand” request appears below. Click on that request and switch to the “Payload” tab and look in the “Query String Parameters” section. Check to see whether the “url” field matches the page on which the video is played, and confirm that the “metadata” field includes the attributes listed here.
Last updated: January 20, 2023