Inventory
Checking installed containers, tags in code and plugins. We determine what to leave, move or disable so that the same script does not run several times.
Manage tags without random code insertions. We set up Google Tag Manager, events and post control so that changes can be checked and tracked.
When needed
There are several counters on the site, it is not known who added them, the events are duplicated, or each tracking change requires an insert search in the templates. The service is suitable both for a new container and for organizing an existing one.
Composition of work
Checking installed containers, tags in code and plugins. We determine what to leave, move or disable so that the same script does not run several times.
Configuring rules for agreed actions. Where the click does not confirm the result, we use the successful operation event transmitted by the site.
We describe data for the developer: event names, identifiers, amounts, currency and required parameters. GTM does not generate missing order data by itself.
We test in Preview / Tag Assistant, check the terms of consent, create a version with a description of the changes. After publication, we repeat the control scenarios.
Collaboration result
Organized container, clear tag names, list of trigger rules and audit log. We provide instructions for publishing and returning to the previous version; access remains under business control.
Preparation
Container access, list of advertising and analytics systems, test scripts and developer contact required. If a consent banner is used, we check how it conveys the user's choice.
Cost
The number of tags and events, the complexity of the site, the state of the current container, the presence of dataLayer. Server GTM, separate infrastructure and consent platform implementation are not automatically included in the base scope.
After getting acquainted with the task, we agree on the composition of work, terms and cost before the start of cooperation.
Examples from practice
Sequence of work
We describe the necessary events, parameters, sources and conditions of operation together with those responsible for the site.
Implementing agreed settings. We check for positive and false positives, duplication and data transfer.
We publish a verified version of the container with a description of the changes. We transfer access and the procedure for checking new tags, duplicates and terms of consent.
Nope. A developer may be required to install the container, reliably pass business events, and patch the site. GTM makes it easy to manage tags after preparing the foundation.
Yes. First, save the current configuration and check dependencies. We publish the changes after testing so as not to lose the necessary events.
Tagging and reporting are different jobs. Before starting, we agree whether GA4, advertising conversions and reports are also needed.
Let's start with the conversation
A few words about the business and the task. Let's discuss what next step would be useful.