Title: Test Integration
Author: joshua
Published: July 21, 2022
Last modified: April 17, 2026

---

 1. [Installation resources](https://docs.parse.ly/installation-resources/)
 2. [Parse.ly Integration](https://docs.parse.ly/installation-resources/parsely-integration/)
 3. Test Integration

#  Test Integration

By this point, you should have installed [the Parse.ly tracking code](https://docs.parse.ly/tracking-code-setup/).
Now it’s time to test your integration. We will review each of the events trigged
by our script.

We’ve written this article with all audiences in mind so that everyone can see what’s
happening for themselves.

## Getting Started

### Open DevTools

Regardless of the event you’re testing, they process always begins by opening your
browser’s Web Development Tools with any of the following methods. Alternatively,
you can use a tool like [Omnibug](https://omnibug.io/). For Dev Tools:

 1. Use a keyboard shortcut
 2.  *  Windows/Linux
        - `Ctrl` + `Shift` + `I` or
        - `F12` for most browsers and full-size keyboards
     *  Mac
        - `Cmd` + `Option` + `I` (Mac) or
        -  `Fn` + `F12` for most browsers and compact keyboards
 3. Use a context menu
 4.  * Right click anywhere on the page in your browser
     * Click “Inspect” or “Inspect Element”
 5. Find DevTools in your browser menu
 6.  * Click the 3 vertical dots or 3 horizontal lines in the upper right corner
     * Look for any combination of “Tools” “Web” Developer”
     * Safari users will need to first enable these tools in menu: Safari > Preferences
       > Advanced

### Navigate to DevTools > Network

With DevTools open, look for a “Network” tab and click to open it. We’ve circled
the Network tab in orange in the lower-right corner of the screenshot, below.

[[

## Is the tracking code loaded?

You may use any of the following methods to see if the tracking code is loaded on
a URL.

### Locate the tracking code in your HTML

 1. Navigate to the Elements tab of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 2. Click on something in the Elements tab to ensure this pane is active
 3. Use keyboard shortcut `CTRL`+`F` (Windows) or `CMD` + `F` (Mac)
 4. Enter one of the following to search for the tracking code:
 5.  * `cdn.parsely`
     * `p.js`

**Pro Tip**

Tracking code loaded via our GTM tag template will contain `/p.js?gtm_ver=`.

Tracking code loaded via the WordPress plugin will contain `/p.js?ver=`.

### Enter `PARSELY` in the Console

 1. Navigate to the Console tab of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 2. Enter `PARSELY`
 3.  * If successful, the Parse.ly object will return.
     * If unsuccessful, you will see an error message saying “Uncaught ReferenceError:
       PARSELY is not defined”

### Use the Open-in-Parse.ly Bookmarklet

See our [Open-in-Parse.ly bookmarklet documentation](https://docs.parse.ly/tools-features/open-in-parsely/)
for details.

## Pageview

### Trigger the pageview

By default, we send a pageview event whenever someone loads your page. To verify
that we’re doing this on your website, perform the following:

 1. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)(
    if you haven’t done so already)
 2. In the filter field, type `action=pageview`
 3. Navigate to a url on your website or refresh the page, if you’re already on the
    url of interest.
 4. Navigate to additional pages, ensuring that one (and only one) pageview fires with
    each page load.

### Examine the pageviews

By now, you should have seen one (and only one) item appear in the list. Let’s review
the screenshot below for expected results and what they mean:

 1.  The filter field where you type `action=pageview`
 2.  The list of network events. By using the filter, we have fewer distractions.
 3.  Click on the “Payload” tab to see the pertinent information
 4.  idsite – this value should match your Parse.ly Site ID.
 5.   * If you see `genericconfigfree` then it means that you have the tracking script
        on your page but that something is wrong with it. Only use Site IDs provided
        by Parse.ly Support and check for typos throughout the entire script.
      * Ensure you’re not using your [sandbox](https://docs.parse.ly/sandbox/) Site
        ID in your production environment and vice versa
 6.  url – the url that triggered the pageview. Must be a “full url” not a relative
     path.
 7.  urlref – the referring url. This will be blank if the reader manually typed in
     the url into their browser. Must be a “full url” not a relative path.
 8.  data – a place where you can [send custom audience segment data](https://docs.parse.ly/setting-up-audience-segments-parsely/#segments-based-on-custom-data)
     to Parse.ly (if purchased)
 9.  title – the headline that will appear in your Parse.ly Dashboard
 10. date – the publication date that will appear in your Parse.ly Dashboard
 11. action – the event that Parse.ly triggered on your site
 12. metadata – the metadata that you’re sending to Parse.ly that we will display in
     your Dashboard

![DevTools with 11 items numbered so the user can test their Parse.ly integration](
https://docs.parse.ly/wp-content/uploads/sites/5/2023/09/SCR-20230922-mrgo.png?w
=981)

### Next Steps

 * If you encountered something unexpected, please review the [Troubleshooting](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-troubleshoot)
   section.
 * If you’ve successfuly tested pageviews, then you’ll likely want to proceed to
   the next step of the integration process, i.e., sending [metadata](https://docs.parse.ly/metadata/).

### Troubleshoot

| Symptom | Potential Cause | Remedy | 
| No pageview appears in the list | [The tracking script](https://docs.parse.ly/tracking-code-setup/) is not on the page
 | If using [the wp-parsely plugin](https://docs.parse.ly/wordpress-plugin-setup/), reconfigure [Track Post Types As](https://docs.parse.ly/wordpress-plugin-setup/#h-additional-configuration) settingsIf using the plugin on a multisite, ensure that you’ve installed on all sitesIf the url is on a subdomain hosted by a third-party, contact them to add the tracking code | 
|  | No navigation since loading DevTools  | Navigate to a new pageRefresh the page | 
|  | There’s a typo in the filter | Erase the filter and look again | 
| Pageview fires once but not when navigating to other pages | Site is a SPA but doesn’t have the SPA tracker | Review the [SPA documentation](https://docs.parse.ly/single-page-application/) and contact support@parsely.com to request the SPA tracker. | 
| More than one pageview appeared in the list while navigating | The tracking script is loaded more than once | If using GTM and wp-parsely plugin, set the plugin `Disable JavaScript` setting to `Yes`Examine your code and look for the tracking code. Try searching with for `cdn.parsely.com/keys`. Eliminate the source of the extra script(s). | 
| idsite says `genericconfigfree` | Invalid Site ID | Check the spelling of your Site ID in the tracking script.Only use Site IDs provided by Parse.ly | 
| Triggered pageviews don’t appear in Dashboard | Domain mismatch | Ensure the Site ID matches the domain that’s sending pageviews. If you’re using the [sandbox](https://docs.parse.ly/sandbox/), provide testing domain(s) to support@parsely.com for allowlisting. | 
|  |  Filtered view | Modify your Dashboard filter(s) to view `Page Type: All Pages` |

If you encountered an unlisted symptom or the corresponding remedies did not solve
your problem, please contact support@parsely.com.

## Heartbeat

If pageviews are working, then there shouldn’t be a need to test heartbeats. But
we’re not going to stop you! To see Parse.ly heartbeats on your site, perform these
steps:

 1. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 2. In the filter field, type `action=heartbeat`
 3. Navigate to a url on your website
 4. Open a new tab in your browser
 5. Click on the original tab used in Step 3, you should see the heartbeat event in
    DevTools
 6. Click on the heartbeat event
 7. If needed, click the “Payload” tab to see the pertinent information
 8. Review the `inc` value – this is the number of seconds that elapsed while the reader
    was engaged with your page

![](https://docs.parse.ly/wp-content/uploads/sites/5/2023/09/Screenshot-2023-09-
29-at-4.25.12-PM.png?w=1024)

Want to learn more about how Parse.ly measures engaged time? Read [here](https://docs.parse.ly/parse-ly-measure-engaged-time/).
Do you want to customize engaged time behavior? Read [here](https://docs.parse.ly/engaged-time/).

## Videostart

### Prerequisites

 1. [Video analytics](https://docs.parse.ly/video-tracking-v2/) is a paid, add-on, 
    feature. If you haven’t purchased this feature, contact your Relationship Manager
    to schedule a demo.
 2. Ensure that you’ve completed the [basic integration](https://docs.parse.ly/parsely-integration/#h-dashboard)
    that includes:
 3.  * Installing [tracking code](https://docs.parse.ly/tracking-code-setup/)
     * Sending [metadata](https://docs.parse.ly/metadata/)
 4. Ensure that you’ve completed the [video analytics integration instructions](https://docs.parse.ly/video-tracking-v2/)
 5. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 6. In the filter field, type `action=videostart`
 7. Navigate to a url on your website that contains your video

### Trigger the videostart

 1. Complete the [prerequisites](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-prerequisites)
    in order to receive the videostart
 2. Play the video
 3.  * If your video contains pre-roll advertising, the videostart will trigger at 
       the beginning of pre-roll by default.
     * When integrating video, it’s up to your development team to decide when the 
       videostart should trigger. Most of our customers trigger the videostart after
       pre-roll.

### Review the videostart

Videostarts are similar to pageviews with the most notable difference being the 
metadata.

![](https://docs.parse.ly/wp-content/uploads/sites/5/2024/05/SCR-20240502-oohk.png?
w=1024)

## Video Heartbeat

If [videostarts](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-videostart)
are working, then it’s unlikely that you’ll need to test video heartbeats. To see
vheartbeats on your site, perform these steps:

 1.  Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
     of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 2.  In the filter field, type `action=vheartbeat`
 3.  Navigate to a url on your website
 4.  Play a video on your site
 5.  Open a new tab in your browser
 6.  Click on the original tab used in Step 3, you should see the vheartbeat event 
     in DevTools
 7.  Click on the vheartbeat event
 8.  If needed, click the “Payload” tab to see the pertinent information
 9.  Review the `inc` value – this is the number of seconds that elapsed while your
     visitor was playing your video
 10.  * Skipping ahead or rewinding the video does not affect our measurement of “minutes
        watched”.
      * Read more about engaged time [here](https://docs.parse.ly/parse-ly-measure-engaged-time/#h-parse-ly-s-engaged-time-measurement).

## Conversion

### Prerequisites

 1. [Conversions tracking](https://docs.parse.ly/conversions/) is a paid, add-on, feature.
    If you haven’t purchased this feature, contact your Relationship Manager to schedule
    a demo.
 2. Ensure that you’ve completed the [basic integration](https://docs.parse.ly/parsely-integration/#h-dashboard)
    that includes:
 3.  * Installing [tracking code](https://docs.parse.ly/tracking-code-setup/)
     * Sending [metadata](https://docs.parse.ly/metadata/)
 4. Ensure that you’ve completed the [conversions integration instructions](https://docs.parse.ly/set-up-conversion-tracking/)
 5. Navigate to a url on your website that contains a converting event

### Testing conversions

**Pro Tip**

Consider using your [sandbox](https://docs.parse.ly/sandbox/) instead of affecting
production data. Support cannot remove conversion events from your Dashboard.

 1. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 2. In the filter field, type `action=conversion`
 3. Trigger the converting event (load, submit, click)
 4. Click on the conversion event
 5. If needed, click the “Payload” tab to see the pertinent information
 6. Review the following values in the data object:
 7.  * `_conversion_type`
     * `_conversion_label`

## Custom Audience Segments

### Prerequisites

 1. Audience Segmentation is a paid, add-on, feature. If you haven’t purchased this
    feature, contact your Relationship Manager to schedule a demo.
 2. Ensure that you’ve completed the [basic integration](https://docs.parse.ly/parsely-integration/#h-dashboard)
    that includes:
 3.  * Installing [tracking code](https://docs.parse.ly/tracking-code-setup/)
     * Sending [metadata](https://docs.parse.ly/metadata/)
 4. Ensure that you’ve completed the [custom audience segments integration instructions](https://docs.parse.ly/setting-up-audience-segments-parsely/)
 5. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 6. In the filter field, type `action=pageview`

### Trigger a pageview (containing segment info)

 1. Navigate to a url on your website that contains the Parse.ly tracking code
 2. Examine the payload of the pageview
 3. Review the value of the data key and ensure it reflects the expected information

![A screenshot of Chrome Dev Tools with a red rectangle drawn around the extra data
sent for custom audience segments.](https://docs.parse.ly/wp-content/uploads/sites/
5/2023/12/SCR-20231211-lvjo.png?w=1024)

### Alternative

If you missed the pageview and want to see what data came with it, enter `PARSELY.
lastRequest.data` into the developer console.

![Running PARSELY.lastRequest.data in the developer console to see the data sent
in the last pageview.](https://docs.parse.ly/wp-content/uploads/sites/5/2023/12/
Screenshot-2023-12-12-at-1.55.48 PM.png)

## Custom Events

### Prerequisites

 1. The Data Pipeline (DPL) is a paid, add-on, feature where you can see custom events.
    Custom events are not visible in the Parse.ly Dashboard. If you haven’t purchased
    DPL, contact your Relationship Manager to schedule a demo.
 2. Ensure that you’ve completed the [basic integration](https://docs.parse.ly/parsely-integration/#h-dashboard)
    that includes:
 3.  * Installing [tracking code](https://docs.parse.ly/tracking-code-setup/)
     * Sending [metadata](https://docs.parse.ly/metadata/)
 4. Ensure that you’ve added custom events using our [Dynamic Tracking instructions](https://docs.parse.ly/dynamic-tracking).
 5. Navigate to the [Network tab](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-navigate-to-devtools-network)
    of [DevTools](https://docs.parse.ly/installation-resources/parsely-integration/test-integration?output_format=md#h-open-devtools)
 6. In the filter field, type `action=custom`

### Sending the Custom Event

 1. Navigate to a url on your website that contains your custom event
 2. Trigger the custom event in accordance with your design
 3. View the event in DevTools

Last updated: April 17, 2026