#How do I know if I've installed the tag correctly?
You can validate the presence of the tracking code and that the metadata is correctly specified by:
- Checking the URL with the Validator.
- Looking in the Parse.ly dashboard.
- Verifying pageviews are sending correctly.
#Will this tag break or slow down my site?
- We use an async approach. Our code loading system is specifically built to async-load the biggest asset after the page has already downloaded, parsed, and executed other assets. This is described in our Tracker technical document.
Once our tracking code is loaded, we install a small cookie (just a user ID) and asynchronously beacon back information to our analytics server. If our analytics server is down, all that happens is that the actions are no longer tracked -- there is no impact on the user experience otherwise.
Check out our public Pingdom report showing our uptime and global response times.
#How is HTTPS supported?
Parse.ly's tracker fully supports tracking on HTTPS pages. When tracking under HTTPS, Parse.ly's tracking tag automatically adapts the set of hosts used to ones with valid HTTPS certificates.
#How does tracking work?
Upon a visit to a Parse.ly-tagged page, a code bundle is downloaded from Parse.ly's global content delivery network. This code bundle retrieves information about the visit to that page, such as pageview and time spent. When combined with metadata, information about your site streams into the dashboard and APIs.
#What data is sent by default?
Several pixel fields are critical for Parse.ly to function at a basic level:
- url: current URL
- urlref: HTTP referrer (traffic source); can be blank
- action: action name (defaults to pageview)
- data: contains information on the UUID from cookie state
- idsite: the "site identifier", aka Site ID, for the website
Other fields are also helpful, such as:
- title: page title
- screen: screen resolution information
- date: client-side datetime in the browser
These are sent in a standard HTTP request, which also includes client information such as the browser User-Agent, client IP address, and third-party (parsely.com) cookie settings.
#What version of the Parse.ly tracker is currently on my site?
When troubleshooting, it can be useful to discover the version number of the currently integrated tracker code.
Open the Chrome DevTools Console (or a similar tool) on your Parse.ly-tracked
PARSELY.version to print the version number of the tracker,
which will look something like
If your site uses a legacy integration,
PARSELY.version may be
that case, type or copy/paste
the console instead.
The Parse.ly Validator Tool
The quickest and easiest way to check for proper integration is by pasting an article URL into our Validator Tool here.
Manually via the Google Chrome Inspector
To manually check if the tracker is installed on your website, go to an article page on your site in Google Chrome.
1. Right click on the webpage, and select “Inspect Element.”
2. Click "Console"
3. Type “PARSELY”
4. Hit Enter
Great job! Now you can move forward to implementing the Metadata tag
If either of these options shows you are not integrated properly, please reach out to email@example.com and we'll help you get up and running in no time.