Skip to content

Integration: Configuring the tracker

To start using, first install the tracking code on your site. The tracker is a small piece of JavaScript code that monitors user actions and relays them to the analytics servers.

To install, add this tag to all pages you would like to track (replacing ###### with your site id, e.g. Your Site ID is your key to Most commonly, it looks like the domain of your website, but the Site ID should never include www, http, or https, : or /.

<script id="parsely-cfg" src="//" async="" defer=""></script>

Add the tracker either directly to your HTML page templates or via our partner implementations: Google Tag ManagerSitecoreGatsbyTealium, and Adobe Launch. Note that an integration via Segment is not currently supported. We also provide examples of how to load the tracker via JavaScript.

Are you looking to track a file that is not HTML (.pdf, .doc, .xls, etc.)? See how to Track Files.

For WordPress sites, we provide a WordPress plugin that adds both the tracking code and supported metadata automatically for you.

For any dynamically loaded content (such as infinite scroll or image galleries), you may need to configure dynamic tracking to manually send pageview events, rather than relying on the automatic pageviews of the standard tracker.

A note on staging sites and test environments

You should never include the tracker with your primary site id on staging, development, testing, or QA pages. Instead, contact to get a test site id to use in those environments

Where should I place the tracker?

The tracker should be placed within the <body> of the page (not in the <head> tag). The ideal place to put the tracker is as the last element before the closing </body> tag. If your website uses a template system, this is usually in the “footer” template.

Verification and troubleshooting

In most cases, customers are able to accomplish both integration steps quickly and without hassle. In order to validate your integration, we recommend the following:

If you run into trouble, give the following a try:

Additional integration steps

While the above two integration steps will provide you with a fully functional analytics dashboard, there are a number of further steps you may want to take to enhance your core integration, depending on your needs.

Tracking campaign data

Collecting data from other platforms

Collecting video/audio data from embedded players

  • If you use a supported player, read the specific documentation to see if any additional scripts or configuration is necessary for to automatically detect video events.
  • Otherwise, define a strategy for the tracker to discover and detect video events.

Tracking Conversions

  • Understand how your content drives Conversions by tracking those events in your dashboard.

Customizing data collection

Configuring other tools

Last updated: May 25, 2023