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

# Product Tracking Instrumentation

> Product event tracking instrumentation skill

Production-grade event tracking instrumentation that goes far beyond "add GA4." It designs a clean event taxonomy (entity + action + context), generates SDK code for GA4, Meta Pixel, Meta CAPI, PostHog, and Mixpanel, and enforces a consent-first cookie gate by default. Server-side CAPI with hashed PII recovers the 30-50% of browser signal lost to iOS 14.5+ tracking restrictions.

## Use cases
- Setting up GA4 + Pixel + CAPI tracking from scratch for a new site
- Revising a messy taxonomy with duplicate or inconsistent events
- Adding server-side CAPI to recover post-ATT signal loss
- Building a privacy-compliant cookie consent gate (default denied)
- Deduplicating Pixel and CAPI events with a shared event_id
- Adding cohort tracking with first-touch source metadata

## Benefits
- One dataLayer source of truth eliminates double-counted conversions
- Recover 30-50% of lost browser signal with dual Pixel + CAPI fire
- Stay privacy-compliant with default-denied consent and IP anonymization
- Measure true campaign ROI with cohort-level retention and LTV

## What’s included
- Snowplow-pattern event taxonomy generator with canonical events
- TypeScript SDK that fans one event out to four platforms
- Consent Mode v2 GTM container template (four consent categories)
- Meta CAPI server route with SHA256-hashed PII and deduplication
- Accessible cookie consent banner with equal-weight choices
- Consent audit log migration plus a 12-mistake anti-pattern table

## Who it’s for
Engineers and growth teams instrumenting product analytics and ad conversion tracking across ikas, Wix, WordPress, Next.js, or Shopify.

## How it runs
Half-broken tracking is worse than none, because you trust it. Four layers go in: taxonomy, typed SDK, GTM fan-out, server side, each gated by consent and validated live before launch.
1. Profiles the client before writing a line: platform (ikas, Wix, WordPress, Next.js) decides the tag injection method, traffic volume decides the tool economics, PII risk and current consent state decide how strict the gates must be.
2. Layer 1, taxonomy: every event is designed in the Snowplow hierarchy of entity plus action plus context, producing a canonical list (product_view, cart_add, checkout_begin, purchase, lead_submit) instead of fifty inconsistent event names that make analysis impossible.
3. Layer 2, SDK codegen: typed track functions that push through a single dataLayer source of truth, each carrying a consent gate, a unique UUID event_id and first-touch cohort fields. Direct gtag calls alongside are banned, because dual firing inflates conversion rates by half.
4. Layer 3, GTM fan-out: one dataLayer event drives four parallel tags (GA4, Meta Pixel, PostHog, Mixpanel) under Consent Mode v2 with default DENIED, so nothing fires before opt-in and double counting is structurally impossible.
5. Layer 4, server side: a Meta CAPI route fires the same event_id with SHA256-hashed email and phone, recovering the 30 to 50 percent of browser signal lost to iOS tracking prompts, while a consent audit log lands in the database with 5-year retention.
6. Pre-live gate: five compliance checks (default-denied consent, IP anonymization, hashed PII only, four-layer Consent Mode, retention limits) plus live browser validation of every canonical event, then an Ads-versus-GA4 conversion comparison before sign-off.

## FAQ
### Does it cover platforms beyond GA4, like Meta or product analytics tools?
Yes, the TypeScript SDK fans one event out to GA4, Meta Pixel, Meta CAPI, PostHog, and Mixpanel from a single dataLayer source of truth. It is built for ikas, Wix, WordPress, Next.js, and Shopify setups.

### How does the CAPI part actually recover signal lost to iOS tracking limits?
It adds a server-side Meta CAPI route that fires alongside the browser Pixel with SHA256-hashed PII, deduplicated through a shared event_id. Because the server call bypasses browser-level blocking, it recovers the 30-50% of signal lost after iOS 14.5 ATT.

### Can it skip the cookie consent gate if I just want full data?
No. The consent gate ships default-denied with Consent Mode v2 and four consent categories, and that is by design for KVKK and GDPR compliance. It will not instrument tracking that fires before consent.

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

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