Installing UsabilityTools using Google Tag Manager

From wiki.usabilitytools.com
Jump to: navigation, search

Google Tag Manager is a 100% free tag management system. Instead of editing site code every single time you can add HTML/JavaScript snippets through GTM. All you have to do is install the Tag Manager script once and make all of your updates after logging in to your Google account.

Contents


Step 1: Get Ready

Create an account on the Google Tag Manager website. You will be asked to create a “Container”, which is a box where you can put all of the tage for your website. After you create a ‘container’ you’ll get a piece of code similar to this one:

GTM - Custom HTML.jpeg


Step 2: Install the Google Tag Manager Code + UsabilityTools Code

Make sure your provided Google Tag Manager script is placed on every page of your site. Here is a screenshot of installing the script in a Wordpress template (go to Appearance -> Editor and change the header.php file):

GTM - Wordpress Install.png


Step 3: Set Up a Tag for the UsabilityTools JavaScript Snippet in your Google Tag Manager account

  • After logging in to your Google Tag Manager account, create a “Custom HTML Tag”.
  • Please refer to your projects’s ‘Collect’ tab to obtain your UsabilityTools JavaScript snippet, which you have to place in the “HTML” field:
  • Click the button to +Add a Firing Rule, so that you will tell Google to load our snippet on all of your pages:


GTM - Installing UT snippet.jpeg


Step 4: Create a Container Version and Publish

When you are ready, go to the Container Overview section on your left. Click the ‘Publish’ button to make sure all of the changes you made are live.

GTM - Publishing a container.jpeg


That’s It!

As always, you can log in to UsabilityTools to look for your first data insights, and to check that you’ve installed the script properly. To recap, there are 4 steps:

  1. Create a tag containing the JavaScript snippet and/or API calls.
  2. Create a rule that tells on which pages to load those tags.
  3. Create a version to save a history of your changes.
  4. Publish the version so that it is actively running on your site.