Building an AT Internet tag template in GTM

Data Architecture 28 January 2021

Use fifty-five’s new templates to implement AT Internet’s tool using GTM

TMS has become a staple when implementing web analysis solutions. They make it easier to roll out and manage data collection, especially when they feature implementation templates. These templates make certain features more accessible and reduce the need for coding. Up until now,  AT Internet users could include templates when using different TMSs (like TagCommander or Telium), except in Google Tag Manager.

To fill their client’s unmet needs, fifty-five created and published GTM compatible templates, in collaboration with AT Internet. Continue reading for a detailed description of our work and to learn how these templates can be beneficial for your company!

The lack of template makes for a difficult integration

Here’s the problem : without pre-existing tag templates in GTM, users looking to implement AT Internet’s solution through this TMS need to use JavaScript code. This means it is difficult for project management teams to tailor the tool to their specific needs, as they are often not comfortable coding, and therefore need to call upon an integrator to help them. The goal here is to make project management teams more independent and more flexible, thereby letting them become more efficient when it comes to data collection projects.

fifty-five’s method: templates made specifically for AT Internet, and compatible with GTM features

At fifty-five, we always start by looking at our clients’ concrete operational hurdles to inform and guide our innovations. This is why we devised a solution to make it easier for non-technical teams to integrate AT Internet tools. Users of GTM can make their own tags and variables templates. We worked back from this feature to create our solution.

AT Internet’s SmartTag can be broken down into 3 features:

  • A JavaScript file, which contains the call to the SmartTag’s custom library.
  • The creation of a tracker, including the tag’s configuration variable.
  • A feature that sends hits to the solution (Page, clicks, etc.).

We therefore chose to create a variable template which includes default settings (the JavaScript file and tracker settings). This variable is then used in a tag template, with the default settings on page hits, clicks, and other events included. If need be, the user can overwrite the default settings via the tag if a value needs to be adjusted to a specific need.

The result: simple and flexible integration

We therefore created: 

  • A variables template for the default setup.
  • A tag template to define which information to send for any specific page, click, or event.

This is a true time saver for our clients, as they only have to fill in the blanks, and they will rarely, if ever, need to code in JavaScript. Anyone on the team can set up the tag.

The people at AT Internet went through the developments to confirm the templates’ longevity. AT Internet also regularly updates the tag and variable so all users can enjoy the solution’s latest additions.

This allows for increased flexibility, autonomy, and efficiency when it comes to data collection projects!
To find out more, you can check our interview on AT Internet’s blog and read our detailed explanation of the template.

Would you like another cup of tea?