Skip to content
Google Tag Manager expertise

Google Tag Manager consultant

Do your tags fire when they should, with the right data? I audit, structure and maintain your Google Tag Manager containers: a clear data layer, tested tags, consent respected. My expertise rests on 10 years of GTM for large accounts in insurance, telecom, banking and retail.

10 years
of Google Tag Manager, from static sites to SPAs
4
large accounts supported: insurance, telecom, banking, retail
2
web analytics solutions fed through GTM: GA4 & Piano Analytics

In practice

On contract within your team
3 to 12 months, renewable, on site or remote.
As a fixed-price project
Container audit, GTM and GA4 setup, server-side tracking package. The price is quoted before starting.
Based in Brussels
On site in Brussels, Liège, Luxembourg, Lille and Paris. Remote everywhere else.
With or without your developers
I specify the data layer, they implement it. IT unavailable? I collect without them.

My references

  • AXA
  • Proximus
  • BNP Paribas Fortis
  • Vanden Borre

When to call a Google Tag Manager consultant

6 situations that justify an outside look at your container.

A redesign or a new site is coming

The tracking plan and the data layer specification are prepared before launch. Tracking is tested in pre-production.

A container nobody dares to touch

Years of tags added without rules, unreadable names, duplicates. The audit maps every tag, every trigger and every variable before any cleanup.

Your ad pixels are not installed

Your campaigns show clicks but not yet the conversions on your site. I install the Meta, Google Ads, TikTok or LinkedIn pixels. Your events feed them.

Your GTM is not set up server-side

Your ad campaigns and GA4 miss part of the conversions. This loss degrades your ad budget and your analysis. A server container reduces it.

Your developers are not available

I set up event collection without IT involvement so that your decisions are not blocked.

You want to improve your customer journey

You want to improve your site's conversion rate and you need precise behavioural data on your visitors to answer specific questions.

What I take on in Google Tag Manager

6 interventions, from audit to handover. Each can be ordered on its own or included in a contract, with a defined deliverable.

Container audit

Mapping of tags, triggers and variables, detection of duplicates, obsolete tags and unmanaged scripts, measurement of the container's weight and the resources it consumes.

Deliverable: a documented container and a prioritised cleanup plan.

Tracking plan and data layer

The KPIs defined with the business teams become events, parameters and naming conventions. The data layer, specified for your developers, ensures stable collection independent of design.

Deliverable: the tracking plan and the data layer specification.

Tags, triggers and variables

Clicks, forms, scroll, ecommerce and lead gen funnels, including on single-page applications. Each event is populated with data, built then tested before publishing.

Deliverable: a readable container and tested events.

Consent and GDPR

Consent Mode v2 connected to your cookie banner, advertising tags fired after the visitor's choice, personal data removed from URLs before sending.

Deliverable: consent verified tag by tag.

Free cookie banner

Ad pixels and server-side

Meta, Google Ads, TikTok and LinkedIn pixels fed by your events, a server container hosted in the European Union and conversions APIs connected server-side.

Deliverable: conversions passed to each platform.

Server-side tracking package

Architecture and governance

Multi-container architecture for groups with several (sub)domains, shared naming conventions and cross-domain tracking.

Deliverable: organised containers and their guide.

No native data layer: collecting from the HTML

When the site provides no data layer and your developers are not available, I work with the data myself: HTML elements, history changes, DOM mutations. Data specific to your pages, your events or your user profiles will be extracted, with more configuration.

The data layer remains the target. I specify it for your developers and collection from the page ensures continuity in the meantime.

12 alerts that justify an intervention on your container

The flaws I find most often in Google Tag Manager containers. The site works, the data is wrong.

  1. GTM code installed twice

    The container code appears twice on the page, or a Google tag is placed both in the code and in GTM. Events are counted twice.

  2. Pages without a container

    Confirmation pages, subdomains, a funnel hosted elsewhere: the code is missing. The journey seems to stop while the visitor keeps going.

  3. Tags fired before consent

    A tag without a consent condition fires as soon as the page loads. The data collected is non-compliant.

  4. An "all clicks" trigger with no condition

    It evaluates every click on the site and consumes resources. Reports fill up with noise events.

  5. Fragile CSS selectors

    A trigger based on a design class breaks at the next redesign. A dedicated ID or attribute holds up over time.

  6. Data layer read too early

    The tag fires before the data is pushed. The value reaches the analytics tool empty.

  7. SPA view changes not tracked

    Without a history trigger, a single-page application only sends its first page. Every funnel step is missing.

  8. HTML tags never reviewed

    Scripts pasted over the years, sometimes with no known owner. They generate JavaScript errors and load unmanaged third-party code.

  9. An unreadable container

    Tags named "copy of...", no folders, unnamed versions, publishing without preview mode. Nobody knows what is active or why.

  10. Tags of old tools still active

    The pixel of a vendor or an abandoned tool keeps sending your visitors' data and makes pages heavier.

  11. Personal data passed to tags

    Emails or file numbers present in the URL or the data layer go to analytics and advertising tools. I clean them before sending.

  12. No server container

    Google Tag Manager is configured on the web side only. Ad blockers and browsers hide part of the conversions from ad platforms. The server container reduces this loss.

4 GTM situations solved

A context, a fix, an effect on tracking.

Insurance, single-page funnels

A funnel measured with no data layer and no IT

Quote simulators and subscription funnels, maintained by external vendors and with no native data layer. I configured GTM to rebuild the whole journey, from the visitor's first choice to the final request, based on information specific to the site's code.

Insurance, multi-container

A container weighed down by years of additions

Several containers, redundant tags, triggers that evaluated every condition permanently. After mapping each tag, the tracking logic was reviewed to reduce the container's weight and the resources it consumed. An SEO gain obtained through tracking.

Retail, ecommerce tracking

A supply chain adapted through ecommerce data

Activation and extraction of the ecommerce data layer of a Shopify site. Creation of a set of ecommerce reports based on product appeal and internal searches. The owner now anticipates upcoming buying trends and manages stock better.

Service, Meta Pixel Ads

Optimised Meta campaigns

Conversion tracking fixed, pixel setup improved through user_data and a clear improvement of the EMQ score from 6 to 9.3/10, lowering the CPA.

My complete configuration process

5 steps, from audit to a team that is autonomous on its container.

  1. Audit of the existing setup

    Containers, tags, triggers, variables, data layer and consent management reviewed.

  2. KPIs and tracking plan

    Workshop with the business teams: which objectives, which events, which parameters. The naming conventions and the data layer specification follow from it.

  3. Implementation

    Tags, triggers and variables built in a readable container: folders, explicit names, commented versions. Consent Mode v2 connected to your cookie banner (or if you don't have one, here is a free one).

  4. QA and validation

    Each event is tested then checked in the web analytics solution and in each advertising platform.

  5. Documentation and handover

    Up-to-date tracking plan, commented container, a guide to keep tagging safely. Your teams stay autonomous.

2 ways to work together

A single point of contact, from audit to handover.

On contract within your team

3 to 12 months, renewable, on site depending on the city: tracking governance, GTM architecture, tracking plan and support for the teams.

See the freelance profile

As a fixed-price project

Container audit and fixes, GTM and GA4 installation, server-side tracking package. The price is quoted before starting.

The questions I get about Google Tag Manager

They make your data collection reliable. They audit the container, define with the business teams the events to measure, specify the data layer, configure the tags and test every event. They then document the container so your teams can carry on.

On a contract, the day rate is discussed during the interview: it depends on the duration, the on-site rhythm and the scope. As a project, the price is often quoted after a first conversation, depending on the need. There is no standard price.

You talk directly to the person who builds your container. An agency also bills for its structure: project managers, offices, sales prospecting, sometimes subcontracting with its margin. It is justified when the need goes beyond tracking (media, creative, development).

Largely, yes. Google Tag Manager captures most interactions directly in the HTML: clicks, forms, funnel steps. Data specific to your pages or users can often be captured without IT, with more configuration.

Yes. On a single-page application, content changes without a reload. Tracking then relies on history changes, DOM mutations and events pushed to the data layer. I have instrumented insurance simulators, banking funnels and telecom applications.

The audit decides. A healthy container is fixed and kept, including to migrate to server-side tracking. A container that has become unreadable is replaced: a new, optimised configuration starts on good foundations.

No. Google Tag Manager collects the data and distributes it to the tool of your choice. I have used it with GA4 and Piano Analytics, as well as with the Meta, Google Ads, TikTok and LinkedIn pixels. For Adobe Analytics, the reference tool is Adobe Launch.

Yes, when it gets heavy. Redundant tags and triggers that evaluate every condition permanently consume resources. The audit maps the container, merges or splits it depending on the impact on performance and limits calculation to what is strictly necessary.

Doubts about your Google Tag Manager container?

A free first call to look at your container, your tags and the priority fixes. Reply within 48h.

Get in touch