Conversion Tracking Mastery Guide (2026): GA4, GTM, Google Ads, Meta & Consent Mode
If you cannot measure conversions accurately, every optimization decision is a guess. Conversion tracking connects ad spend to business outcomes — form fills, phone calls, purchases, app installs — across Google, Meta, and your analytics stack.
This guide covers the full tracking stack for 2026: GA4, GTM, Google Ads, Meta Pixel/CAPI, enhanced conversions, consent mode, and offline imports.
→ GA4 Metrics Reference · Enhanced Conversions Guide · Meta CAPI Guide · Consent Mode v2 Guide
Tracking stack overview
| Layer | Tool | Purpose |
|---|---|---|
| Tag management | Google Tag Manager | Deploy and manage all tags from one container |
| Web analytics | GA4 | On-site behavior, events, audiences, reports |
| Google Ads tracking | Conversion tag + enhanced conversions | Attribute conversions to ad clicks |
| Meta tracking | Meta Pixel + Conversions API | Attribute conversions to Meta ads |
| Consent | Consent Mode v2 | Respect user privacy choices, model gaps |
| Offline | Offline conversion imports | Close the loop on phone/COD sales |
| Call tracking | Dynamic number insertion or GTM | Attribute phone calls to campaigns |
GA4 event architecture
GA4 uses event-based tracking — every interaction is an event with optional parameters.
Recommended events for Nepal businesses
| Event | Trigger | Parameters | Priority |
|---|---|---|---|
generate_lead |
Form submission |
form_name, value
|
Critical |
phone_call_click |
Click-to-call button | phone_number |
Critical |
whatsapp_click |
WhatsApp button click | — | High (Nepal) |
purchase |
Order confirmation |
value, currency (NPR), items
|
Critical (e-commerce) |
add_to_cart |
Add to cart action |
value, currency, items
|
High (e-commerce) |
begin_checkout |
Checkout start |
value, currency
|
High (e-commerce) |
sign_up |
Account creation | method |
Medium |
file_download |
PDF/resource download | file_name |
Medium |
Full event reference: GA4 Metrics Complete Reference
GA4 conversion setup
- GA4 Admin → Events → Mark as conversion:
generate_lead,purchase,phone_call_click - Set conversion counting to “Once per session” for leads, “Every time” for purchases
- Link GA4 to Google Ads (Admin → Product Links → Google Ads)
- Import GA4 conversions into Google Ads OR use dedicated Google Ads conversion tags (recommended for accuracy)
Google Tag Manager setup
GTM is the deployment layer for all tracking tags.
Container architecture
GTM Container
├── Tags
│ ├── GA4 Configuration (fires on All Pages)
│ ├── GA4 Event — generate_lead (fires on form submit)
│ ├── GA4 Event — phone_call_click (fires on tel: link click)
│ ├── Google Ads Conversion — Lead (fires on form submit)
│ ├── Google Ads Enhanced Conversions (fires with conversion tag)
│ ├── Meta Pixel — PageView (fires on All Pages)
│ ├── Meta Pixel — Lead (fires on form submit)
│ └── Consent Mode defaults (fires before all other tags)
├── Triggers
│ ├── All Pages
│ ├── Form Submission — Contact Form
│ ├── Click — tel: links
│ ├── Click — WhatsApp links
│ └── Custom — thank-you page view
└── Variables
├── GA4 Measurement ID
├── Google Ads Conversion ID + Label
├── Meta Pixel ID
└── Enhanced conversion data (email, phone from form)
Dictionary reference: Google Tag Manager · Data Layer
GTM deployment checklist
-
GTM container snippet in
<head>and<body>on every page - GA4 Configuration tag firing on All Pages
- Consent Mode defaults configured (denied by default, update on consent)
- Form submission trigger tested in Preview mode
- Phone call click trigger tested on mobile
- Google Ads conversion tag firing on thank-you page or form submit
- Meta Pixel PageView firing on All Pages
- Meta Pixel Lead event firing on conversion
- GTM container published (not just previewed)
- Tag Assistant / GA4 DebugView confirms events
Google Ads conversion tracking
Setup options
| Method | Accuracy | Complexity | Recommended |
|---|---|---|---|
| Google Ads conversion tag (via GTM) | Highest for Google Ads | Medium | Yes — primary method |
| GA4 import | Good | Low | Secondary — for reporting alignment |
| Enhanced conversions | Highest (recovers lost data) | Medium | Yes — when running search/shopping |
| Offline import | Closes phone/COD gap | High | Yes — for service businesses |
Enhanced conversions
Sends hashed first-party data (email, phone, name) with conversion events to improve attribution when cookies are blocked.
Setup guide: Enhanced Conversions Setup Guide
Key points:
- Enable in Google Ads → Goals → Conversions → Settings
- Pass hashed email/phone via GTM data layer on form submit
- Requires 50+ conversions/month for meaningful impact
- Works with Consent Mode — modeled conversions fill gaps
Meta Pixel + Conversions API
Browser-side Pixel alone captures ~60–70% of events post-iOS 14.5. CAPI recovers the rest.
Dual tracking architecture
| Channel | Method | Captures |
|---|---|---|
| Browser | Meta Pixel (via GTM) | PageView, Lead, Purchase events |
| Server | Conversions API | Same events + offline conversions |
| Deduplication | Matching event_id
|
Prevents double-counting |
Full setup: Meta Conversions API Setup Guide
Dictionary: Meta Pixel · Conversions API
Event Match Quality (EMQ)
Meta scores how well your CAPI events match user profiles (0–10). Improve EMQ by sending:
- Hashed email (highest impact)
- Hashed phone number
- Hashed first name + last name
- Client IP address and user agent (automatic with CAPI)
- Facebook click ID (
fbc) and browser ID (fbp) from cookie
Target EMQ ≥ 6.0 for reliable attribution.
Consent Mode v2
Required for Google Ads remarketing in EEA/UK. Best practice everywhere for data quality.
| Consent type | Controls | Default |
|---|---|---|
ad_storage |
Advertising cookies | Denied |
analytics_storage |
Analytics cookies | Denied |
ad_user_data |
Sending user data to Google for ads | Denied |
ad_personalization |
Personalized advertising | Denied |
Setup guide: Consent Mode v2 Setup Guide
How it works: When users deny consent, Google models conversions using aggregated data instead of individual tracking. You retain ~70–85% of conversion visibility vs. ~0% without Consent Mode.
Offline conversion imports
Critical for Nepal service businesses where sales happen via phone, WhatsApp, or COD — not on the website.
Workflow
- Capture GCLID — store Google Click ID in hidden form field or CRM
- Log offline conversion — when sale completes (call, visit, delivery), record GCLID + conversion value + date
- Upload to Google Ads — via CSV upload or API (weekly cadence minimum)
- Google Ads attributes — conversion linked to original ad click
| Field | Required | Example |
|---|---|---|
Google Click ID |
Yes | EAIaIQobChMI... |
Conversion Name |
Yes | Offline — Job Completed |
Conversion Time |
Yes | 2026-08-11 14:30:00 |
Conversion Value |
Recommended | 4500 |
Conversion Currency |
Recommended | NPR |
Meta equivalent: Offline Event Set — upload customer list with event data via CAPI or Events Manager.
UTM parameter conventions
Consistent UTM naming prevents reporting chaos:
| Parameter | Convention | Example |
|---|---|---|
utm_source |
Platform |
google, facebook, tiktok
|
utm_medium |
Channel type |
cpc, paid_social, email
|
utm_campaign |
Campaign name | plumbing_emergency_2026 |
utm_content |
Ad variant | rsa_headline_a |
utm_term |
Keyword (search only) |
{keyword} (auto-tagging preferred) |
Dictionary: UTM Parameters
Rule: Google Ads auto-tagging (GCLID) handles search attribution — UTMs are for non-Google channels and email.
Debugging and validation
| Check | Tool | What to verify |
|---|---|---|
| GA4 events firing | GA4 DebugView | Event name, parameters, user properties |
| GTM tags firing | GTM Preview mode | Tag fire order, trigger conditions |
| Google Ads conversions | Google Ads → Conversions → Status | “Recording conversions” status |
| Meta events | Meta Events Manager → Test Events | Browser + server events, EMQ score |
| Enhanced conversions | Google Ads → Conversions → Diagnostics | Tag coverage percentage |
| Consent Mode | Tag Assistant → Consent | Default + update signals |
| Cross-platform | GA4 Acquisition report | Source/medium alignment with ad platforms |
Run this validation after every tag change — not just initial setup.
Tracking maturity model
| Level | Setup | Suitable for |
|---|---|---|
| 1 — Basic | GA4 pageviews + 1 conversion event | Pre-revenue startups |
| 2 — Standard | GTM + GA4 events + Google Ads conversion tag + Meta Pixel | Most SMEs |
| 3 — Advanced | Level 2 + enhanced conversions + CAPI + consent mode | NPR 50K+/month ad spend |
| 4 — Enterprise | Level 3 + offline imports + CRM integration + server-side GTM | High-volume service/e-commerce |
Most Nepal businesses should target Level 2 immediately and move to Level 3 when monthly ad spend exceeds NPR 50,000.
