Google Tag Manager

Google Tag Manager that makes tracking simpler

I set up and fix GTM so your tags, triggers, variables and dataLayer are logical, testable and documented. A good container makes tracking simpler, not more complicated.

The first 20-minute consultation is free for new clients.

Documented

the container still makes sense months later

GA4 + Google Ads

tracking and ad platforms work together

Analytics Mania

completed a hands-on Google Tag Manager course

A typical situation

Is your GTM container a help or a burden?

A container quickly becomes hard to manage when every new tracking request adds yet another random tag. Good GTM logic is clear, testable and recoverable.

The same event is tracked from several places

I check GTM, plugins and your website code so the same event isn’t tracked twice.

Nobody knows which tag is the right one any more

I tidy up names, versions and outdated tags.

You have a consent banner, but tags behave incorrectly

I check the consent default and update logic and GTM’s Consent Checks settings.

How it works

dataLayer, tags and destination platforms work together

GTM alone doesn’t guarantee good tracking. The dataLayer, triggers, tags and destination systems all need to handle the same event in the same way.

Why it matters

The dataLayer needs to pass the event and the required parameters reliably. If tracking relies on reading HTML elements on the page (the DOM), the next design change can break it.

Google Tag Manager: dataLayer, container and destination platforms The website sends a form_submit event to the dataLayer. In Google Tag Manager, a trigger, variables and tags use it to send the event on to GA4, Google Ads and Meta via the Pixel or Conversions API. The whole chain is checked in Preview and DebugView. Data layer (dataLayer) dataLayer.push({ event: 'form_submit' }) Google Tag Manager Trigger Variables Tags GA4 analytics Google Ads conversion Meta Pixel / CAPI check: Preview + DebugView

What’s included

What the Google Tag Manager service includes

I can help with auditing your existing container, building new tracking logic or setting up a specific conversion or integration.

Start

Container audit

I check existing tags, triggers, variables, versions, consent logic and double tracking.

Data layer

dataLayer and events

I set up stable event logic and the required parameters so tracking doesn’t depend on the page’s HTML structure.

Platforms

GA4, Google Ads and Meta

I set up or fix events for analytics and ad platforms, plus the remarketing tags you need.

Add-on

Consent and server-side tracking

I check the Consent Mode logic and, if needed, assess whether server-side GTM is really necessary in your situation.

If server-side GTM is justified, one hosting option is Stape (affiliate link). For a wider tracking audit, see the web analytics service; for Google Ads conversions, see Google Ads management.

Process

How we work together

We start with what needs to be tracked and where the data needs to go. Only then do I make changes in the container.

01

Goal

We define what needs to be tracked and which systems the data needs to reach.

02

Audit

I check the existing container, dataLayer and connected platforms.

03

Setup

I create or fix tags, triggers, variables and consent logic.

04

Test

In Preview mode, I check events, values and consent state.

05

Publishing

I save a version, publish changes only after testing, and document them.

Richard Pikmets, Google Tag Manager and web analytics specialist

An alternative to an agency

The same person knows both the container and its purpose

I’m Richard Pikmets. I work with both ad campaigns and web analytics, so I always look at Tag Manager as part of your whole tracking setup. I’ve completed the Analytics Mania Google Tag Manager and GA4 courses and hold a Google Analytics certification.

An agency is a good fit if…

  • you need a large custom server-side solution
  • the project involves several development teams and a data warehouse
  • GTM is just a small part of an enterprise data project

Working directly with me is a good fit if…

  • you need your existing container audited or fixed
  • you want to set up GA4, Google Ads or Meta events
  • you want one person to look at both the technical work and the marketing goal

Example

When the same GA4 event fires twice

This isn’t a client case study or a promise of results. It’s a simplified example of a common mistake and how I check for it.

BEFORE

GA4 receives the same form event from both GTM and a website platform plugin.

CHECK

I check GTM Preview, the browser’s network requests and plugins, and find that the event is sent from two places.

OUTCOME

I keep one verified data flow and document where the event is sent from going forward.

Pricing

What the price depends on

The workload depends on the state of your existing container, the number of events, whether a dataLayer is needed, your consent solution, ad platforms and whether the setup is client-side or server-side.

The audit and implementation can be separate stages. That way it’s clear which solution is really needed before the container is changed.

Audit

A check of your existing container’s structure, double tracking and consent logic.

One-off setup

Creating a new event, conversion or dataLayer logic.

Server-side setup

When a server-side setup is needed for specific tracking or an integration.

Frequently asked questions

Is GTM the same as Google Analytics?

No. GTM helps you manage tags and events technically. GA4 is one of the systems the data is sent to.

Can my existing container be fixed?

Yes. I usually keep the parts that work and fix problematic or outdated setups.

Do you set up Consent Mode?

Yes. I set up the consent default and update logic and the consent requirements for tags. See also Cookie Consent setup.

Will I have access when the work is done?

Yes. The container and accounts should belong to your company.

Is server-side GTM always better?

No. It can be useful, but it adds complexity and cost. I assess the need based on the specific tracking.

Can Meta Conversions API be set up through GTM?

Depending on the setup, yes – especially with server-side GTM. The choice has to fit your website and consent logic.

Is a dataLayer always needed?

Not for every simple event. For more complex or business-critical data, a stable dataLayer is usually better than reading data from the page HTML.

Do you document the changes you make?

Yes. Key events, tags and logic need to be clear later on.

Next step

Ask for a GTM consultation

Briefly describe what you want to track or what isn’t working right now. I’ll review the situation and suggest a suitable audit or setup.

  • which action you want to track
  • whether you already have a GTM container
  • what your biggest technical question is right now

info@praktilineturundus.ee · +372 5340 9139

Send a Google Tag Manager enquiry

Ask for a GTM consultationFirst 20 min free for new clients