Google Tag Manager

Google Analytics allows you to track standard events that occur on your store (e.g. page views, purchases, etc.). If you want to track anything extra (e.g. a conversion tracking tag), then Google Tag Manager provides a way to do this without needing a developer to write custom code for you.

In this article, we’ll show you how to install Google Tag Manager on your Payhip store.

Install Google Tag Manager on your Store

To get started with Google Tag Manager, you can follow these instructions: Set up and install Tag Manager

Once you get to step 2.4 and have launched the Install Tag Manager box (shown below), complete the following steps.

Please note that you will need to be using a custom domain to add Google Tag Manager to your store.

A screenshot of the Install Google Tag Manager modal.

Step 1. Install the <script> snippet

To add the code inside the <head> tags:

  1. Launch the store builder by going to Store in the top navigation bar, then clicking Launch Your Store Builder (or by clicking Account > Store Builder).
  2. Click Change Store Style > Advanced.
  3. Paste the code under Header HTML/JS Code Injection.
  4. Save and publish your changes.

A screenshot of the Header HTML/JavaScript Code Injection field in Payhip's store builder

Step 2. Install the <noscript> snippet

This snippet is for just in case a visitor to your store doesn’t have JavaScript enabled. To add this to your store:

  1. Launch the store builder by going to Store in the top navigation bar, then clicking Launch Your Store Builder (or by clicking Account > Store Builder).
  2. Click Change Store Style > Advanced.
  3. Paste the code under Footer HTML/JS Code Injection.
  4. Save and publish your changes.

A screenshot of the Footer HTML/JavaScript Code Injection field in Payhip's store builder

Google Tag Assistant

Once you’ve added some tags, you can use Google Tag Assistant to verify that everything is installed correctly and your tags are working.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.