Title: Migrate to Google Tag Manager
Author: joshhanson
Published: November 4, 2024
Last modified: November 12, 2025

---

 1. [Installation resources](https://docs.parse.ly/installation-resources/)
 2. [Installation tools](https://docs.parse.ly/installation-resources/installation-tools/)
 3. [Google Tag Manager](https://docs.parse.ly/installation-resources/installation-tools/google-tag-manager/)
 4. Migrate to Google Tag Manager

#  Migrate to Google Tag Manager

When changing your Parse.ly integration method, it’s important to take steps to 
limit the impact on your data during the transition period. We want to avoid either
of the following situations:

 1. **Double-counting pageviews** by setting the tracker by two different systems at
    the same time.
 2. **Missing pageviews** by removing the first tracking method before implementing
    the second method.

This guide outlines how you can use [trigger exceptions](https://support.google.com/tagmanager/answer/7679318)
in Google Tag Manager (GTM) to gracefully handle this transition.

## Implementation steps

1) [Add the Parse.ly tag template to your workspace.](https://docs.parse.ly/gtm-tracking-for-web-containers/#h-adding-the-template)

2) [Create and configure “Tracker” tag type from template.](https://docs.parse.ly/gtm-tracking-for-web-containers/#h-tracker)

3) Create a _DOM Element_ variable with the following:

 * Selection Method: **CSS Selector**
 * Element Selector: `script[src*="cdn.parsely.com"]`
 * Attribute Name: `src`

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

4) Create a trigger with the same trigger type as your Parse.ly tag firing trigger
from step 2. If using a Custom Event trigger, make sure the same event name is used.
Under the _This trigger fires on_ setting, choose “Some […]” and in the conditions
select the variable from step 3 | **does not equal** | `null`.

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

5) Open the Parse.ly tag from step 2. In the _Triggering_ section click the **Add
Exception** button and choose the trigger you created in the previous step.

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

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

6) Using GTM’s preview mode, test the workspace on a staging environment with an
existing Parse.ly tracker implemented.

When the existing tracker is present the GTM tag should not fire.

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

When the existing tracker is removed, the GTM tag should fire.

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

7) Publish the container.

8) Remove the existing tracker implementation. (If you are using the WordPress plugin,
navigate to the plugin settings in your wp-admin, under the _Disable JavaScript_
option select **Yes, disable JavaScript tracking** and then save changes.)

Last updated: November 12, 2025