Google Tag Manager Express Setup
Pre-Integration Checklist
impact.com has three tags you need to load into your GTM container: the Universal Tracking Tag (UTT), Identify Function, and the trackConversion function. You want the Universal Tracking Tag (UTT) to load first, followed by the Identify Function, then fire the trackConversion function. You will also need to set up a page view trigger to ensure these tags fire correctly.
The Universal Tracking Tag
Follow the instructions below to load the impact.com UTT tag into the GTM container.
Universal Tracking Tag
From the top navigation bar, select [User profile] → Settings → General. Paste your entire unique UTT code into this field.

Before the closing
</script>tag, add the following line:dataLayer.push({'event':'UttLoaded'});We will get to what this function does shortly. Your final impact.com UTT script should look similar to this:

Next, select Triggering panel → All Pages.

Navigate back to the tag preview screen and select Save.

Your dashboard tag workspace should look similar to this:

Set up data layer variables
Once you have the key that you would like to work with, you can proceed to create a data layer variable.
For this scenario, the keys used will be the customer id and customer email values from the customer details data layer.
Follow the instructions below to create data layer variables in your GTM workspace:
Below the Triggers menu, select Variables.
Under User-Defined Variables, select New.

Select Variable Configuration. Then select Data Layer Variable as the variable type.

In the Data Layer Variable Name field, enter the key exactly as it was written in the code (e.g.
customerId, not customer Id.).Because the data layer in this example is a well-structured nested data layer and has child keys, use the key name of the parent and child elements for the Name. Separate the key names with a dot and give your variable a name as a reference to the key you are using.
In the Set Default Value hit the space bar, select Save.

Because the customer is not always signed in, GTM would append the value
undefinedin cases where thecustomerIdkey is not populated. To counter this we've instructed you to set the default value in the Set Default Value field to a single blank space, this will pass a blank value instead ofundefined.
In most cases you should leave the Data Version set to the default value of Version 2.
Save the variable.
Repeat these steps for every data layer key (i.e. customer email key) that you would like to have as a variable in Tag Manager.
Preview the container to save the changes. You will publish the container at a later stage.
The page view trigger


Implementation
The final step in the impact.com tag placement journey is to publish the GTM container. Doing this will publish your tags to your production or staging environment, wherever you have placed the GTM tags. If you are deploying to your production environment, you will have to move the GTM tags to your production site pages.
You have options to configure different environments from within GTM, for example, if you wanted different environments to test like "Staging" and a production environment, "Live".
Steps to implement
Follow the steps below to publish your GTM container.
Select Publish and Create Version at the top of your GTM container.
Optionally, give the version a name as well as a description for the workspace changes.
Optionally, select the environment. If you are moving from staging to live, this step is required.
Select Publish.

Once you have fully integrated the impact.com API, you can begin end-to-end testing to ensure everything is working properly. Learn how to proceed with End-to-End Testing.
Last updated













