A very good question. Generally, a product/ web analyst first identifies the website elements and events they need to track in GA. H/she creates and documents the events schema to ensure high analytics data quality before sharing with the developer in Excel/ Sheets. The developer now goes through the tracking setup process of writing datalayer codes, creating variables, tags, triggers and QA in GTM and GA.

After a decade of GA implementations, we have figured out there are scores of such event tracking needs that can be fairly automated on top of GTM right from standard codes to tags and triggers creation with 100% accuracy. An analyst can install these predefined tracking templates on their own with zero or limited developer dependency and save hours of effort and money. They don’t even need to login to GTM. In short, Tagmate is automation of your GTM setup, but not an alternative.

‍

Relax, your customer data is safe. Tagmate does not do event logging when the GTM container is published. The only data that gets stored in Tagmate servers are the templates and user defined parameters, if any that you have activated and pushed to GTM. This is to ensure there is no duplication of same event tracking templates and to maintain high analytics data quality. We comply with all policy guidelines listed here.

Once you have deactivated your Tagmate account, we will delete all the projects and configurations except your user profile details. The latter is only to re-engage you with our boring or quirky blogs and newsletters, obviously with your consent.

‍

a) You need to have edit/publish access to your GTM container which Tagmate will authorize and connect for all implementation or migration activities.

b) You need to have a basic understanding of how GTM works and publish containers for active data collection.

c) Additionally, for UA to GA4 migration, if you need to list UA custom dimensions in Tagmate, you will also need to have edit access to your GA property.

‍