Web Analytics & Conversion Tracking Checklist

After completing any tracking implementation, it’s crucial to follow a thorough process to ensure accuracy and effectiveness. This checklist will guide you through the necessary steps to validate both client-side and server-side tracking, helping you spot any issues early. By following these best practices, you can ensure that your data is reliable and that your web analytics and conversion tracking are set up for optimal performance. Consistently using this checklist will lead to more accurate insights and better decision-making for your campaigns.

 GA4 – Ecommerce Tracking

Client-Side Checklist:

• GA4 Configuration tag loads on All Pages with correct Measurement ID

• Enhanced Measurement enabled, but Form Interaction turned OFF

• Google Signals enabled (⚠️ No user data acknowledgment if consent banner is not present)

• Events tracked: view_item, add_to_cart, begin_checkout, purchase

• Each event includes all key parameters: value, currency, items, tax, shipping, coupon

• purchase event must include value and purchase parameters

• Events appear in DebugView and Real-time reports.

• items array data matches frontend product info

• No duplicate events fired in GTM Preview Mode

• UTM parameters tracked properly (if required by client)

Server-Side Checklist:

• Events and parameters sent from client side properly

• GA4 Server Container receives all events with correct parameters

• GA4 Server Tag configured with the correct Measurement ID

• Debugged using Tag Assistant & Server Logs

• Server events visible in GA4 DebugView with accurate data

• value, currency, items not missing in server event payload

KPIs:

• Accuracy Rate (100% match with frontend activity)

• Conversion Match 80%+ (Website dashboard vs GA4 Dashboard)

• Parameter Completion 100% (all expected parameters present)

• Revenue Match 80%+ (GA4 vs website revenue dashboard)

GA4 – Service-Based Tracking (Form Submission)

Client-Side Checklist:

• GA4 Configuration tag loads on All Pages with correct Measurement ID

• Enhanced Measurement enabled but Form Interaction toggled OFF

• Events tracked: form_submit or custom (e.g., generate_lead, form_start)

• Use unique event names per form (if multiple forms exist)

• Triggers based on: Page URL, Form ID, Form Class, Button Click, Click Class, Custom Event or iFrame event

• Parameters captured: form_name, form_id, form_type (as applicable)

• Events show in DebugView and Real-time reports with correct parameters

• “Thank You” page fires only once (if using redirect-based thank you)

• No event duplication on page reload (implement reload-prevention script)

Server-Side Checklist:

• Client-side data sent correctly to server

• The server container receives all form submission events with correct details

• GA4 Server Tag correctly configured

• Debug with Tag Assistant & Server Logs

• Events appear in GA4 DebugView with all expected parameters

Google Ads – Ecommerce

Client-Side Checklist:

• Google Ads Conversion Tag implemented with correct Conversion ID and Label

• Fires only on order success page or purchase event

• Additional conversions tracked: add_to_cart, begin_checkout

• Parameters dynamically passed:  value, currency, transaction_id

• Enhanced Conversions set up with user data (if available)

• Remarketing Tag implemented (if requested)

• Mark:
  • add_to_cart and begin_checkout as secondary conversions

  • purchase as primary conversion

• Verified in Tag Assistant and browser Network tab

• Ensure the purchase event is nno firing on cart or checkout pages incorrectly

• gclid passed and saved in cookies → check for _gcl_au

Server-Side Checklist:

• Required parameters sent from client side

• Google Ads server conversion tag configured with proper Conversion ID/Label

• value, currency, and transaction_id received server-side

• Enhanced Conversions (hashed email/phone) sent via Server GTM

• Use Server Tag Assistant to validate EC and server events

• Confirm visibility under Google Ads → Tools → Diagnostics → Active status

KPIs:

• Conversion Match Accuracy Rate (browser vs server parity)

• Conversion Value Accuracy Rate (revenue match)

Google Ads – Lead Form Tracking

Client-Side Checklist:

• Google Ads Conversion Tag implemented with correct Conversion ID and Label

• Triggered only on successful form submission

• value is static or dynamic per lead (as per use case)

• Enhanced Conversions set up (if email/phone is available)

• Tag Assistant:
  • No warnings

  • No duplicates

• Single fire per submission, not when form is opened

Server-Side Checklist:

• Required event/parameter setup on client side

• Google Ads tag correctly configured server-side

• Enhanced Conversion via server with hashed email/phone

• Validated through Tag Assistant and GTM server logs

KPIs:

Conversion Accuracy Match Rate %

Meta Pixel + Conversion API (CAPI)

Client-Side Checklist:

• Pixel fires for standard events:
  • PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead

• Parameters passed:
  • value, currency, content_name, content_ids, event_id

• Pixel Helper confirms:
  • One fire per action

  • No duplicates on dynamic pages

• User data (email, phone) hashed before being sent

• event_id included for deduplication

• Events appear in Meta Events Manager → Test Events

Server-Side Checklist:

• All required data received from client side through GA4/Tags

• Server Tag for Meta CAPI configured properly

• Server Tag Assistant shows correct event & parameters

• Events received and deduplicated in Meta Events Manager

• event_name and event_id match browser-side

• Match Quality in Events Manager = Green

• Server logs confirm event was successfully sent

KPIs:

• Match Rate %

• Deduplication Accuracy %

• Server Event Fire Count

TikTok Pixel + Events API

Client-Side Checklist:

• TikTok Pixel installed with correct Pixel ID

• Standard events tracked:
  • PageView, ViewContent, AddToCart, CompletePayment

• Parameters included:
  • content_type, content_name, content_id, quantity, value, currency

• Validated via Tag Assistant and TikTok Test Events Tool

• Pixel Helper shows no duplicate fires

Server-Side Checklist:

• Events sent via sGTM with:
  • event_id, value, currency, and matching parameters

• TikTok Events API tag is configured properly

• Events visible in TikTok Business Test Tool

• event_id matches browser side for deduplication

KPIs:

• • Event Match Rate (browser + server)

• Server Consistency %

Snapchat Pixel + CAPI

Client-Side Checklist:

• Snap Pixel installed correctly on all pages

• Pixel ID is accurate and verified

• Standard events tracked:
  • PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, PURCHASE

• Parameters included:
  • item_ids, item_category, price, currency, transaction_id, number_items, client_dedup_id

• Hashed user data for event match included (email/phone)

• Snap Pixel Debugger: No errors, no duplicates

• Events match real user actions (not triggered prematurely)

Server-Side Checklist:

• Events sent via Snap CAPI Tag in sGTM

• All required fields auto-sent: event params, user data

• event_id passed from browser for deduplication

• Validated through Snap Test Event Tool

• Hashed identifiers: email, phone (if available)

KPIs:

• • Event Delivery Status (Success vs Dropped)

• Match Quality Score

• Deduplication Rate

Pinterest Tag + CAPI

Client-Side Checklist:

• Pinterest Tag installed with valid Pinterest Tag ID

• Events triggered:
  • PageVisit, AddToCart, Checkout, Lead, SignUp

• No page-load errors or accidental tag fires

• Validated via Pinterest Tag Helper: Events are accurate, no duplicates

Server-Side Checklist:

• Events sent via Pinterest Conversion API using sGTM

• Required fields:
  • event_name, event_time, event_id, user_data

• User data hashed properly (SHA256): email, phone, IP, user-agent

• event_id matches browser side for deduplication

• Debug via Pinterest Events Manager

KPIs:

• Event Health Score

• Hash Validation Score

• Server Sync Rate

LinkedIn Insight Tag + CAPI

Client-Side Checklist:

• LinkedIn Insight Tag fires on all pages

• Conversion tags fire on specific triggers:
  • Thank You Pages, Form Submission, or Button Clicks

• A tag fires only once per conversion

• No duplicate events on reloads

• Validated via browser console/network tab

Server-Side Checklist:

• CAPI events sent using the authorized LinkedIn API Token

• Required fields:
  • conversion_id, event_name, event_time, event_id, user_agent, ip

• Hashed user data: email, phone, etc.

• Deduplication via event_id

• Debug using LinkedIn Event Insights Tool (or server logs)

KPIs:

• • API Match % (Browser vs Server accuracy)

• Conversion Delay Time

• Attribution Success Rate

Bing Ads + Microsoft Clarity

Client-Side Checklist:

• UET Tag is installed and verified on all pages

• Conversion Goals configured and triggered on the correct user actions

• Microsoft Clarity installed and tested to ensure it does not interfere or block tracking tags
  (Clarity is for session recordings; verify it’s not overlapping with UET behavior.)

KPIs:

• Goal Conversion Match % (vs expected actions or GA4 goals)

• UET Tag Status = Active in Microsoft Ads

• Attribution Delay % (Time from event to appearing in Microsoft Ads UI)

🔚 Other Ad Platforms (Twitter, Taboola, Quora, etc.)

Client-Side Checklist:

• Base tag installed with correct Pixel ID / Account ID

• Event tags implemented for key actions:
  • Lead, Purchase, PageView, etc.

• Parameters passed correctly:
  • content_name, currency, value, transaction_id (if supported)

Server-Side Checklist (If Supported):

• Postback URL or Conversion API setup via sGTM

• Required API credentials and conversion parameters verified

• Test events sent and validated using platform-specific tools or logs

KPIs:

• Postback Delivery Rate (Server-side hits delivered vs dropped)

• Conversion Event Accuracy (parameter match vs frontend)

Attribution Success Rate (server conversions reflected in ad dashboard)