---
title: Analytics Tracking
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/analytics-tracking/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/analytics-tracking/
last_updated: 2026-06-20
---

# Analytics Tracking

> Set up, improve, or audit analytics tracking and measurement.

A GTM-first analytics implementation playbook that turns business questions into a clean, decision-grade measurement layer. It architects GA4 event models, dataLayer contracts, and Google Ads conversion pipelines so every tracked event answers a real question, no noise, no inflated metrics. Built for modern stacks where server-side rendering changes when and how tracking fires.

## Use cases
- Setting up GA4 + Google Tag Manager from scratch on a new site
- Wiring lead tracking for phone clicks, WhatsApp, and form submissions
- Importing conversions into Google Ads for ROAS measurement
- Auditing an existing setup for duplicate pageviews and inflated metrics
- Type-safe dataLayer integration in a Next.js App Router project
- Fixing tracking that fires on validation errors instead of real successes

## Benefits
- Trustworthy data you can actually make ad-spend and CRO decisions on
- No more deploy-blocked tracking: marketing manages tags without code releases
- Clean conversion counts that survive cross-channel attribution scrutiny
- Faster pages because tracking scripts load without breaking Core Web Vitals

## What’s included
- A measurement-plan framework that ties each event to a KPI and report column
- Object-action event naming convention and GA4 conversion setup checklist
- Type-safe GTM wrapper and Next.js App Router script-loading pattern
- GTM container structure with triggers, variables, and tag organization
- GA4 DebugView and GTM Preview validation checklist
- Anti-pattern catalog covering duplicate events, PII leaks, and performance traps

## Who it’s for
Growth engineers, marketers, and developers who need conversion tracking they can defend to a finance team or a client.

## How it runs
If an event cannot name the business decision it serves, it does not get tracked. From that filter outward, the whole measurement setup is built in six moves:
1. Starts from decisions, not data: every proposed event must answer which business decision it serves, and if it cannot, the event is rejected. Active or planned Google Ads makes conversion tracking the first mandatory item.
2. Writes the measurement plan before any code: business goal to KPI to event name in object_action format (Google recommended events like generate_lead first) to parameters to GTM trigger to the exact report column the data will feed.
3. Implements the code side as dataLayer.push only, through a typed central analytics utility; all tag management lives in the GTM container so marketers can change tags without a deploy, and scripts load with the afterInteractive strategy so Core Web Vitals stay intact.
4. Installs the sector event set: generate_lead, phone_clicked, whatsapp_clicked and direction_clicked for local service businesses, fired only after a real success state, marked as GA4 conversions and imported into Google Ads where campaigns run.
5. Hardens the GA4 property itself: data retention raised from the 2-month default to 14 months, enhanced measurement on, conversion events flagged with the right counting method, and the Ads link established.
6. Validates before production: GTM Preview shows the tags firing, GA4 DebugView shows correct parameters, one click produces exactly one event, no email or phone number leaks into any parameter, and the whole flow is re-checked on mobile.

## FAQ
### Is Google Tag Manager required, or can I implement tags directly?
The playbook is GTM-first because that is where the event model and dataLayer contract stay maintainable as a site changes. You can hardcode tags, but you lose the clean layer that keeps tracking defensible later.

### Why bother with a dataLayer contract instead of just wiring tags in GTM?
Tags wired ad hoc drift into noise and inflated metrics nobody can defend to a client or finance team. The dataLayer contract is what ties every event back to a real business question instead of a vanity number.

### Does it cover Meta Pixel and other platforms too?
Its core is the GA4 event model and the Google Ads conversion pipeline. Other platform pixels can read from the same dataLayer, but the playbook is built around the Google stack.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [AI for data analytics](https://forgehouse.ai/guides/ai-data-analytics/)