Beslist Tag Implementation Guide

On this page, we are pleased to assist you with implementing the Beslist tag on your webshop through Google Tag Manager.

In this step-by-step guide, we will be performing the following actions:

  1. Installing the Beslist Tag within Google Tag Manager.
  2. Creating a tag from the template.
  3. Configuring the configuration tag.
  4. Configuring the conversion tag.
  5. Activating the Beslist tag.

After completing this guide, the Beslist tag will have been successfully implemented on your webshop!

In addition to this guide, we also have a list of appendices to further assist you in case you encounter any difficulties during the steps outlined in the guide.

Appendix A:

If you are unable to use the Gallery in step 1, we explain in this appendix how you can download the file from Github yourself.

Appendix B:

If you encounter difficulties linking the correct variables in step 5 or have not yet created the necessary variables, we explain in this appendix how to do so. We use Google Analytics 4 as the basis for this.

1. Implementing the Beslist tag template

The Beslist Tag is included in the Gallery of Google Tag Manager. Follow these steps:

  1. Navigate to “Templates” in the menu at the bottom left-hand side.
  2. Under “Tag Templates,” click on the “Search in Gallery” button at the top right.
  3. Click the magnifying glass icon at the top right to initiate the search.
  4. Search for “Beslist.”
  5. Select the found template.
  6. Click “Add to Workspace” at the top right, then click “Add.”
  7. Click “Save” at the top right.

If you have completed all of these steps successfully, you will notice that the Tag Template has been added to your Google Tag Manager container with the name “Beslist event.”

2. Creating tags

In the previous step, you added the template to your Google Tag Manager container. As mentioned earlier, this template serves as a blueprint for the tag. In this step, you will create a tag based on this template.

To start with this, first navigate to tagmanager.google.com and select the container of your webshop. Here, you can go to Templates via the left menu and then click on New Tag Template. In the image below, you can see where to do that.

Next, the Template Editor will open itself, where you will choose the options menu indicated by the symbol with the 3 vertical dots. In this menu, click on Import and select the Template File from step 1. In the image below, you can see where to do that.

Attention!

Make sure you have downloaded the correct file named template.tpl and not accidentally named template.tpl.txt. This can sometimes happen if you chose to download the file from Github. If the file does not have a .tpl extension, the import will not succeed.

After you have loaded the Template File, the Template Editor will be filled with the tag information. There is no need to make any further changes, just click the Save button. After clicking Save, the button will change from blue to gray. If this is successful, you can close the Template Editor using the X button in the top left corner. In the image below, you can see where to do that.

If everything went well, you will see that the Tag Template has been added to your Google Tag Manager container. It will be named Beslist event.

3. Creating a tag

In the previous step, you added the template to your Google Tag Manager container. As mentioned earlier, this template is just a blueprint for the tag. In this step, you will create a tag from this template.

To get started, go to the Tags menu and click on New tag. In the image below, you can see where to do that.

When you click this button, a side menu will open. In this menu, you will have the option for Tag Configuration or Tag Triggering. In this step, select the Tag Configuration option. In the image below, you can see where to do that.

Tip!

Tag Configuration is used to specify how a tag should behave, such as tracking page views or capturing button clicks.

Tag Triggering is used to specify where and when the tag should be activated on the website.

Once you click on Tag Configuration, another menu will open asking you which Tag Type you want to configure. Since you previously added the Tag Template, you now have the option for our Beslist event template. Click on this Tag Type. In the image below, you can see where to do that.

You will now have the following screen in front of you. Leave this screen open and proceed to the next step.

4. Tag Configuration Setup

4.1 The configuration tag configuration

In this step, you will continue setting up the basic configuration tag. This tag will track new sessions. A new session can be initiated, for example, when a user arrives on your website from a link on beslist.nl. These sessions are used to accurately attribute conversions.

You will need to perform a few steps on this page:

  1. Give the tag a name, we recommend “Beslist – Configuration Tag“.
  2. Enter your advertiser ID.
    1. In this example, we use “1234” as the ID. For your webshop, you have received your own ID from Beslist. If you are unsure what it is, please check with your Beslist Account Manager.
  3. Leave the rest as is, so the event type remains as “configuration“.

In the image below, you can see how the configuration will look like.

Do not click save yet, but proceed to the next step where you will set up the trigger.

4.2 The configuration tag trigger

In this step, you will implement the trigger for the configuration tag. In the screen where you left off in the previous step, you will find this section at the bottom. Click on this section to set up a trigger.

Choose the All pages (Page View) option as the trigger, as indicated in the image below.

Attention!

The All Pages trigger is built-in by default in Google Tag Manager. If there is a privacy protocol for your website that excludes certain pages, create a custom trigger for them.

Always ensure that you operate within your appropriate consent level.

4.3 Check the configuration tag

If everything is correct, the configuration tag should now look like the image below, indicating that it was successful.

Don’t forget to click the blue Save button to complete the configuration. Once you click Save, the side menu will close automatically, and the tag will be visible in the list of tags, as shown in the image below.

5. Conversion Tag Implementation

5.1 The conversion tag configuration

In this step, you will implement the conversion tag. The process will be similar to step 4. Go to the Tag page again and click on New Tag. Choose the Tag Configuration section and select the Beslist event custom template again.

You will need to perform a few steps on this page:

  1. Give the tag a name, we recommend “Beslist – Conversion Tag”.
  2. Enter your advertiser ID.
    1. In this example, we use “1234” as the ID. For your webshop, you have received your own ID from Beslist. If you’re not sure what it is, please inquire with your Beslist Account Manager.
  3. Select conversion as the event type.
  4. Click the Add Row button 3 times.

In the image below, you can see how the configuration will look like.

As a continuation of the previous step, you will add 3 contextual parameters to the tag configuration. These parameters will indicate the conversion value, the transaction identifier, and whether the transaction is inclusive or exclusive of VAT.

It is important to use the exact same naming for the parameter name as indicated in the table below. The parameter name is case-sensitive.

In the 3 parameter fields, you will fill in:

Parameter name Description
value This parameter represents the conversion value. For purchases, it should contain the transaction revenue.
transaction_id This parameter carries the unique transaction ID, sometimes referred to as an order ID, of the transaction. Beslist uses this parameter for validation and to associate purchases with your webshop.
including_vat This parameter indicates whether the value parameter includes or excludes VAT. If the amount is inclusive, enter: true. If the amount is exclusive, enter: false.

If you have succeeded, you will see the tag configuration as follows.

Attention!

In this example, double handlebars notation is used for the value and transaction_id.

This notation indicates a reference to a variable within Google Tag Manager. In this case, these variables refer to dataLayer variables from the ecommerce object of Google Analytics 4.

If you’re unsure how to set this up for your case, refer to Appendix B for a practical example.

5.2 The conversion tag trigger

In this step, you will implement the trigger for the conversion tag. On the screen where we left off in the previous step, scroll down to this section. Click on this section to set up a trigger.

Choose the Purchase Event option as the trigger, as indicated in the image below.

Attention!

In your webshop, this may be a completely different trigger. For example, you may have implemented your own trigger that fires on the Thank You Page.

Whatever your trigger is, make sure that the value and transaction_id variables are available when the trigger fires.

5.3 Checking the conversion tag

If everything went well, the conversion tag should now look like the image below, indicating that it was successful.

Don’t forget to click the blue Save button to complete the configuration. Once you click Save, the side menu will automatically close, and the tag will be visible in the list of tags, as shown in the image below.

6. Going Live

When you navigate to the main page of Google Tag Manager (Overview), you will see that some changes have been made due to the actions taken in the previous steps. These Workspace Changes are not live yet. To go live with the Beslist tag, click on the Submit button on the Overview page.

From there, you can choose to create a new version or create a new version and publish it immediately. Depending on the structure and workflow applicable to your Google Tag Manager container, choose the option that suits you best.

If you create a new version first, don’t forget to publish it yourself or have the appropriate person publish it.

Once the version with the configured Beslist tag is live, the implementation is successful!

Appendix A: Template Download

Navigate to the GitHub repository via this link. Then click on the green button labeled “Code” and download the Zip file. Unzip this file locally and save the template.tpl file. You can use this file to continue with Step 1.

Appendix B: Google Analytics 4

If you are using Google Analytics 4, in this appendix, you can learn how to set up the variables for the conversion tag.

Documentation for the GA4 implementation structure can be found at this link.

Creating Parameter Variables with GA4 Implementation
If the dynamic variables do not exist yet and you are using the GA4 implementation, you can add the variables yourself in order to dynamically send them later.

1.) This link leads to the standard implementation of the GA4 data layer for ecommerce. If the data layer is implemented in this way, you can add the variables yourself using the following link. It is important to note that it refers to the purchase event. 2.) This link describes how to create a variable that retrieves data from the data layer. It is important to note that it retrieves transaction_id and value. If you follow the GA4 implementation, the variables will likely look like the example image below.

Your data layer may be set up slightly differently from the standard GA4 implementation, but with the documentation from the second link, you can still retrieve the correct variables from the data layer.

Depending on how the data layer is structured, you may need to create different references, for example:

  1. ecommerce.purchase.actionField.transaction_id
  2. ecommerce.purchase.transaction_id

The variables that are created can then be added to the conversion tag in step 5.1.