WPFix Pathtechnical workbench Send symptom
TrackingWordPress

Tracking failure path

WordPress GA4 and GTM tracking fixes for forms, clicks, and conversions

Form and lead tracking failures often come from AJAX submits, thank-you page assumptions, duplicate tags, plugin-injected tracking, consent behavior, or GTM triggers that do not match the real user path.

Send this symptomAll problem paths

TRIGGERS / WHEN

When this usually appears

  • after form plugin updates
  • after adding a consent banner
  • after switching thank-you page logic
  • after GTM or GA4 edits
  • after installing tracking plugins
  • after changing page builders or templates

ROOT PATHS / WHY

Where the failure often sits

  • form AJAX submit does not trigger a pageview
  • thank-you page not firing
  • duplicate GA4 tags
  • GTM installed twice
  • plugin injects tracking outside GTM
  • phone or email clicks not tracked
  • consent banner blocks tags
  • cross-domain path not configured
FIRST PASS

Checks closest to the symptom

container installation and duplicate scripts
form submit behavior
thank-you path and redirect logic
click triggers for phone, email, and buttons
GA4 event names and parameters
consent mode and blocked-tag state

WORDPRESS LAYER MATRIX

Plugin names are checks, not separate doorway pages

Use the affected layer to choose evidence. A plugin is not assumed guilty merely because it is installed.

LayerObserved symptomInspectKeep as evidence
Contact Form 7The form succeeds but no lead event appearsAJAX lifecycle event, DOM listener scope, consent state and duplicate tagsGTM Preview sequence, network request and GA4 DebugView event
Gravity FormsMulti-page or AJAX forms fire early, late or twiceConfirmation behavior, render/submission hooks, history changes and trigger deduplicationOne controlled submission with event order and parameters
WPFormsA success message appears without the configured conversionAJAX setting, confirmation path, plugin event hook and GTM trigger conditionsSuccessful request, visible confirmation and one destination event
MonsterInsights / plugin tagsGA4 counts differ or the base tag is installed twicePlugin measurement ID, GTM container tags, theme snippets and consent integrationTag Assistant inventory, network calls and DebugView source path

SPRINT OUTPUT

Fix or implementation-ready path

  1. map the real conversion path
  2. fix safe GTM triggers, GA4 events, form hooks, or plugin conflicts
  3. remove obvious duplicate tag paths where safe
  4. verify in DebugView or destination diagnostics

VERIFICATION

The change needs a second measurement

  • GTM Preview
  • GA4 DebugView
  • Google Tag Assistant
  • test form submission
  • browser console and network inspection

USEFUL INPUT

What helps reproduce it

  • site URL
  • form or conversion URLs
  • form plugin involved
  • GTM and GA4 access
  • what changed recently

SCOPE BOUNDARY

What this path does not promise

  • CRM implementation
  • marketing attribution strategy
  • monthly reporting
  • landing page rewrite
  • ad account restructure

RELATED FAILURE PATHS

Continue only when the symptom crosses a layer

WooCommerceWooCommerce conversion tracking fixes for GA4, GTM, Meta, and Google AdsWooCommerce revenue events are missing or unreliableIndexingWordPress indexing problems: what to check before rewriting contentWordPress pages are not indexing

START / Tracking

Have the URL and one exact symptom?

The remaining technical context can stay collapsed unless it helps reproduce the failure.

Send this symptom