Tech docs
Integration Docs


#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:

#Will this tag break or slow down my site?

No! Here are some principles behind our JavaScript serving infrastructure and the code itself.

  • Our code is compressed and minified. Both at the JavaScript minification level and at the gzip level (by our servers).
  • We serve from global servers. As detailed in our  Servers and Infrastructure page, JavaScript is served using a global DNS provider and a global CDN provider with edge locations scattered all over the United States and even across Europe, Asia, and South America.
  • 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.

Our JavaScript code is written so that it is the very last script that loads on your page.

We host our DNS servers ( with a global, distributed DNS system, which has no downtime and extremely fast resolution times across the globe. Our JavaScript code itself is hosted in a global content delivery network (CDN) with edge locations in every global region.

Our code itself is optimized to not impact user experience in any unintended way. It also automatically leverages asynchronous JavaScript loading technologies in newer browsers. For older browsers, we use a sophisticated loading process that loads a few bytes of data from a high-speed CDN (a "bootstrap" file) and then uses an asynchronous JavaScript loading library (the LABjs library) to ensure that none of our other assets block your page load.

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.

Our team is staffed by JavaScript experts who know the pain and frustration with crappy third-party JavaScript integrations. We therefore have taken a lot of care to make our tracking code integration a no-brainer, safe decision.

Check out our public Pingdom report showing our uptime and global response times.

#How is HTTPS supported?'s tracker fully supports tracking on HTTPS pages. When tracking under HTTPS,'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 page, a code bundle is downloaded from'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 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 ( cookie settings.

#What version of the 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 webpage. Type PARSELY.version to print the version number of the tracker, which will look something like "1.3.0".

If your site uses a legacy integration, PARSELY.version may be undefined. In that case, type or copy/paste PARSELY.config.bundle.match(/[\d\.]+/)[0] into the console instead.

#How to check if the JavaScript Tracker was implemented properly

After you have signed up for a account, the next step is integrating the Javascript tracker on your site. There are 2 ways to check for proper implementation:

The 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

  • If the implementation of the Javascript tracker was successful, you will see:


Great job! Now you can move forward to implementing the Metadata tag

  • If the implementation of the Javascript tracker was unsuccessful, you will see:

parsely_chrome_inspect_metadata If either of these options shows you are not integrated properly, please reach out to and we'll help you get up and running in no time.

rocket emoji