Kreative Clan — Tracking Setup

What good tracking guarantees

Four things must be true before we spend

The audit tells us what's wrong today. This plan fixes it — so every reported conversion is real, attributable and consent-safe.

Clean signal

One container, one data layer, no dead legacy tags polluting conversions or audiences.

Real conversions

A conversion fires when someone actually enquires — not when a page merely loads.

Attributable

Every ad click from Meta, LinkedIn and Google is captured under the right account.

Consent-safe

Tags respect your cookie banner via Consent Mode — accurate and compliant.

Conversion events

What we track, and exactly when it fires

A shared event map across GA4 and every ad platform, with a naming convention so reports read the same everywhere.

Event name	Fires when	Platform(s)	Counts as	Value
generate_lead	Enquiry / contact form submitted (thank-you state)	GA4 · Meta · LinkedIn · Google Ads	Primary conversion	Assigned
stand_enquiry	"Book a stand / exhibit" form completed	GA4 · Google Ads	Primary conversion	Assigned
brochure_download	Media pack / brochure downloaded	GA4 · Meta	Secondary	—
call_click	Click on a `tel:` link	GA4 · Google Ads	Secondary	—
whatsapp_click	Click on a WhatsApp link/button	GA4 · Meta	Secondary	—
scroll_90	90% page depth on key pages	GA4 only	Engagement	—

How it's built

The implementation, step by step

Open each stage. This is what we configure in your GTM container before go-live.

Foundation

Data layer & event model

One clean source of truth all tags read from.

dataLayerGTM

Every meaningful action pushes one clean event to the data layer before any tag reads it. This is the single source of truth all platforms share.

On a successful form submission, push: dataLayer.push({event:'lead_submit', form_id:'...', form_name:'...', value: 0}).
GTM listens for the lead_submit custom event and fires the GA4, Meta, LinkedIn and Google Ads conversion tags from it — never on page-load.
Enhanced conversions: pass hashed email/phone from the confirmation step where available, under consent.
One container, one GA4 config tag, one consent check — no duplicate base pixels.

If a second GTM container exists, we consolidate to one. Two containers double-fire conversions and inflate retargeting audiences.

Hygiene

Container clean-up

Retire legacy tags and de-dupe pixels.

AuditNaming

Before launch we audit the container and retire anything that pollutes conversions or audiences.

Remove legacy / duplicate pixels and orphan tags left by previous agencies.
De-dupe base pixels so each platform loads once.
Fix triggers that fire on page-load instead of on completion.
Confirm all tags sit under our GA4 property and ad accounts, not a personal/old account.
Set a clear naming convention: Platform | Type | Action (e.g. GA4 | Conv | generate_lead).

Send back

Read-only access to your GTM container and GA4 property is enough for us to audit everything and prepare the fixes.

Privacy

Consent mode & privacy

Compliant firing tied to your banner.

Consent v2PDPL

Tags respect consent so tracking is both accurate and compliant.

Google Consent Mode v2 wired to your cookie banner — tags wait for consent, model the gap.
Marketing tags (Meta, LinkedIn, remarketing) fire only after marketing consent.
Analytics stays privacy-safe by default; no PII in event parameters.

This pairs with the Compliance & Data page — see how consent, PDPL and retention are handled.

Pre-launch tracking QA

Sign-off checklist

We tick these in a debug session before a single ad goes live. Try it — the bar fills as boxes are checked.

Tracking verified0%

GTM consolidated to a single containerGA4 config tag fires once, correct propertygenerate_lead fires on submit, not page-loadMeta / LinkedIn / Google Ads conversions de-dupedEnhanced conversions + Consent Mode v2 liveLegacy / orphan tags removedTest lead flows end-to-end into each platformUTM parameters present on all ad destination URLs

Turn your pixels into clean, real conversions