Google Tag Manager consultant in a GTM workspace, with a website to server to GA4 and BigQuery data flow on a second screen

Google Tag Manager consultant for clean, consent-ready containers

A Google Tag Manager consultant designs and builds the container that sends your site's data to GA4 and the ad platforms, and ties each tag to the consent it needs. Waftr writes the specs first, then builds and tests in your GTM account. Server-side GTM is covered under server-side tracking.

Core Build in 3 to 4 weeks. Your web container rebuilt from written specs. Plan your GTM build

A starter kit for your next Google Tag Manager setup

We write three documents before building anything, and your team approves them first. Below is a simplified sample of each, built on GA4's recommended events and Google's own consent commands. Borrow freely.

Consent defaults

Runs first, above the GTM snippet

window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}

gtag('consent', 'default', {
  ad_storage: 'denied',
  analytics_storage: 'denied',
  ad_user_data: 'denied',
  ad_personalization: 'denied',
  wait_for_update: 500
});

Why it is written this wayConsent Mode only reads the gtag() form, and the command has to run before the container loads. wait_for_update holds Google tags for 500 ms while the banner restores a returning visitor's choice.

generate_lead

Runs after the form is accepted

window.dataLayer.push({
  event: 'generate_lead',
  lead_source: 'pricing_page',
  form_id: 'demo_request'
});

Why it is written this wayPush it when the server accepts the form. A click trigger also counts failed and repeated submits. generate_lead and lead_source are GA4's own recommended names, and form_id tells two forms on one page apart.

purchase

Runs on the order confirmation page

window.dataLayer.push({ ecommerce: null });
window.dataLayer.push({
  event: 'purchase',
  ecommerce: {
    transaction_id: 'T-10482',
    value: 129.00,
    currency: 'USD',
    items: [{
      item_id: 'SKU-2231',
      item_name: 'Annual plan',
      price: 129.00,
      quantity: 1
    }]
  }
});

Why it is written this wayThe first push clears the previous ecommerce object. Without it, items from an earlier event on the same page can carry into this purchase. GA4 uses transaction_id to drop the duplicate when someone reloads the confirmation page.

The events in a real spec come from the measurement plan agreed during GA4 implementation. The full spec for your site is delivered with the Tracking Build.

Name tags for the person who inherits the container

Containers outlive the people who build them. The container blueprint sets one naming pattern for each kind of item. GTM sorts its lists alphabetically, which lets the first word of a name do the grouping.

Sample naming convention for a Google Tag Manager container
Item	Pattern	Example	Why this pattern
Tags	`Platform - Type - Detail`	`GA4 - Event - generate_lead`	All GA4 tags line up together, and the last part matches the event name in the spec.
Triggers	`Type - Detail`	`CE - generate_lead`	The prefix says what fires the tag. CE is a custom event, PV a page view, CL a click.
Variables	`Type - Key`	`DLV - lead_source`	DLV marks a data layer variable, and the key is spelled exactly as the spec spells it.
Folders	`NN Platform`	`01 GA402 Google Ads90 Consent`	The numbers set the order. Consent and utility folders sink to the bottom.
Workspaces	`Owner - Change`	`dev - checkout data layer`	Anyone opening the container sees who is editing what before two workspaces collide.
Version notes	`What / Why / Approved by`	`Consent check on Meta Pixel / Fired before a choice / Web lead`	GTM stores each version. The reason for it lives only in the note.

Map each tag to the consent it needs

Consent Mode v2 passes four signals. Google's tags read them and adjust. Other vendors' tags ignore them, and GTM has to hold those back until the visitor allows them. The map settles that for each tag before anything is built.

WaitsGTM blocks the tag until the signal is granted
ReadsThe tag fires and adjusts to the signal
Not usedThe tag is not tied to the signal

Sample consent map showing how each tag relates to the four Consent Mode v2 signals
Tag	`analytics_storage`	`ad_storage`	`ad_user_data`	`ad_personalization`
GA4 configuration	Reads	Reads	Reads	Reads
GA4 events	Reads	Reads	Reads	Reads
Google Ads conversion	Not used	Reads	Reads	Not used
Google Ads remarketing	Not used	Waits	Waits	Waits
Meta Pixel	Not used	Waits	Waits	Waits
LinkedIn Insight	Not used	Waits	Waits	Waits

Shown for advanced Consent Mode. In basic mode, the GA4 and Google Ads conversion rows wait as well, and nothing reaches Google before consent.
Remarketing waits even though Google's tag can read the signals. Building ad audiences is its only job.
Meta and LinkedIn tags do not read Consent Mode. GTM's additional consent checks hold them until the visitor allows advertising.

How the banner sets these signals, and how we test each state, is covered under Consent Mode v2 setup. A Core Build writes the full kit for your container.

Plan your GTM build

What changed in two rebuilt containers

Two GTM implementations, with results exactly as published in their case studies. Under each number is the container work behind it.

NexTranslate
Consent checks on each tag

100%of tags wait for consent, verified by test
- Before the rebuild, GA4, Google Ads and the Meta Pixel fired before the visitor chose
- After the rebuild, Cookiebot banner sending Consent Mode v2 signals
- After the rebuild, A consent check on each tag in the container
Set up for GDPR, CCPA and the DPDP Act.
Read the NexTranslate case study
SaaS company
Form tags that fire

+20%Google Ads remarketing conversions on the rebuilt audiences
- Before the rebuild, Form tags that never fired
- Before the rebuild, A broken first event
- After the rebuild, Tag Manager reworked after a GA4 audit
- After the rebuild, Remarketing audiences rebuilt on clean data
A GA4 audit found both faults before the Build started.
Read the SaaS case study

When the web container is not enough

Tags in a web container run in the visitor's browser. Ad blockers stop some of them, and Safari limits cookies set by script to 7 days. A tidy naming convention changes none of that. When paid budgets depend on those conversions, the next step is server-side GTM or Google Tag Gateway, built as an Advanced Build in 5 to 8 weeks.

Compare server-side setups

How does a GTM implementation run?

A Core GTM implementation takes 3 to 4 weeks, from written specs to a published container. The Google Tag Manager expert who writes your specs also does the build. Nothing goes live until the changes have been checked in Preview and Tag Assistant with consent accepted, rejected and not yet given, and your team has approved the version.

Write the specs
The three kit documents above, written for your site. Your team approves them before any tag changes.
Build in a workspace
A separate GTM workspace your developers can open at any point. The live container stays untouched.
Test each consent state
Preview and Tag Assistant runs for each banner state. A tag that fires early is fixed here.
Publish and hand over
One version goes live with its note. A training call and written documentation follow.

Submit changesWorkspace: consent checks

Illustrative

Version name: v12 Consent checks on ad tags
Version description: Meta Pixel and LinkedIn Insight now wait for ad consent. Why: both fired before a choice. Approved: web lead.

Checked before publish

No choice yet: ad tags held
Reject: ad tags held
Accept: all tags fire
Approved by your team

Goes live only after approval

How a Google Tag Manager consultant scopes and quotes your build

The Audit findings Sheet is the starting point. Each fault on it becomes a line of Build scope or a line marked for your own developers, and the lines add up to one quote, fixed in writing before any work starts. There is no hourly rate.

What moves a GTM quote

Sites, properties and containersEach extra GTM container or GA4 property needs its own spec, blueprint and test runs.
Consent regionsEU, UK, US states and India can each need their own defaults and banner rules.
Server-side taggingGoogle Tag Gateway or a server container moves the work into an Advanced Build.
BigQuery exportRaw GA4 events land in your Google Cloud project, with the tables documented.
CRM or offline conversionsLeads and closed deals sent back to Google Ads from the CRM.

Tracking Audit
Quoted after a short call or the free scan
7 business days
A read-only review of the container and GA4, ahead of any rebuild. The fee is credited to a Build started within 30 days.
Where a GTM rebuild starts
Core Build
Quoted from the Audit findings
3 to 4 weeks
The web container rebuilt from the starter kit, with Consent Mode v2 and enhanced conversions.
Advanced Build
Quoted from the Audit findings
5 to 8 weeks
Adds server-side GTM or Google Tag Gateway, BigQuery export and offline conversion import.
Enterprise Build
Scoped and quoted per project
Timeline set in the scope
Several sites or brands under one governance plan.

Hosting for server-side GTM, on Google Cloud or Stape, is billed to you by the vendor. Ad-hoc hours are available only inside Tracking Care.

Before you hire a Google Tag Manager consultant

What does a Google Tag Manager consultant do?

A Google Tag Manager consultant designs and builds the GTM container that sends your website's data to GA4 and your ad platforms. The design comes first, as written documents your developers and marketers sign off. Then the consultant builds tags and triggers in a workspace and tests them before publishing. At Waftr, the specs and the build come from the same consultant.

What does a Google Tag Manager setup include?

A Core setup from Waftr includes the data layer spec, a container blueprint with naming and folders, a consent map, GA4 and Google Ads tags, Consent Mode v2 and enhanced conversions. Each tag is tested in Preview and Tag Assistant in all three consent states before publishing. Handover is a training call plus written documentation.

Do you write the data layer, or do our developers?

Both, in that order. Waftr writes the data layer spec event by event, with the exact names and values each tag will read. Your developers add the pushes to the site, because the code is theirs. Before any tag uses a value, we check it in GTM Preview.

Is Waftr a Google Tag Manager agency or a consultant?

Waftr is a consultancy. You work with a GTM consultant who writes the specs and builds the container, and each Build is quoted in writing from the Audit findings. Agencies that need Google Tag Manager work for their own clients can white-label Waftr's Audits and Builds through the partner program.

What should a GTM expert document before publishing?

Before the first publish, a GTM expert should have the data layer spec, the container blueprint and the consent map signed off. After that, each published version needs a note saying why it changed and who approved it. Without those notes, the next person inherits a container nobody can explain.

Do we need GTM 360?

Rarely. GTM 360 adds unlimited workspaces, approval workflows and zones that control what linked containers may fire. Those matter when several teams or agencies edit one container under strict change control. Most teams do well on the free version with a clear naming convention and a rule that nothing goes live without a version note.

Want the current container reviewed first? The Google Tag Manager audit checks it with read-only access in 7 business days. The free GA4 audit tool runs 8 public checks with no access at all.

Send us your container

Tell us what the container does today and where the numbers disagree. A few lines are enough to scope a Core or Advanced Build.

What to put in the message

Each line shows an example answer.

Container ID: GTM-XXXXXXX
Conversions that matter: demo requests
Consent banner: Cookiebot, or none yet
Where numbers disagree: GA4 against Google Ads
Who adds code to the site: an in-house developer

The Waftr team has 13 years in digital analytics, across 10+ industries and 50+ global teams, and holds Google Analytics, Google Tag Manager and OneTrust certifications.

Google Tag Manager consultant for clean, consent-ready containers

A starter kit for your next Google Tag Manager setup

Consent defaults

generate_lead

purchase

Name tags for the person who inherits the container

Map each tag to the consent it needs

What changed in two rebuilt containers

Consent checks on each tag

Form tags that fire

When the web container is not enough

How does a GTM implementation run?

Write the specs

Build in a workspace

Test each consent state

Publish and hand over

How a Google Tag Manager consultant scopes and quotes your build

What moves a GTM quote

Tracking Audit

Core Build

Advanced Build

Enterprise Build

Before you hire a Google Tag Manager consultant

Send us your container

What to put in the message

Plan your GTM build