wiki/knowledge/google-ads/cordwainer-conversion-tracking-fixes.md · 839 words · 2026-02-19

Cordwainer Google Ads Conversion Tracking Fixes

Overview

During a February 2026 internal sync, the team identified that Cordwainer's Google Ads campaign was severely under-reporting conversions. The campaign showed strong engagement (7% CTR, 172 clicks on ~$300 spend) but only one recorded conversion — almost certainly a measurement failure rather than a true performance problem. Two root causes were identified and addressed.

See also: [1] | [2]


Root Cause 1: WP Rocket Firing Before GCLID Registration

What Happened

WP Rocket (a WordPress caching/performance plugin) was executing its page optimization routines before the Google Click ID (GCLID) had a chance to register in the browser. Because the GCLID is the mechanism Google uses to attribute a site action back to a specific ad click, any form submission or conversion event that fired before the GCLID was stored would be invisible to Google Ads.

What a GCLID Is

When a user clicks a Google Ad, Google appends a unique identifier — the Google Click ID (GCLID) — to the destination URL. This ID travels with the user's session. When a conversion event fires (e.g., a form submission), Google reads the stored GCLID to credit the originating click. If the GCLID hasn't been written to the browser yet, the conversion is lost.

Fix Applied

Mark updated the WP Rocket execution order so that the GCLID is registered before any conversion tracking fires. This was a configuration change within WP Rocket's settings — no plugin replacement was required.

Status: ✅ Fixed by Mark (prior to the 2026-02-19 sync)


Root Cause 2: Broken SMTP Causing Lost Form Submissions

What Happened

The site's SMTP (outbound email) configuration was misconfigured, resulting in 14 failed email deliveries in the preceding 30 days. This means that even when a visitor submitted a contact form, the notification email to the client was silently dropped. The client never saw the lead; the conversion was never confirmed.

Compounding this, the site was using an unreliable third-party form platform instead of Gravity Forms. The switch to Gravity Forms had been planned but not yet executed on the production site.

Fix Required

Gravity Forms is preferred because it integrates cleanly with Google Ads conversion tracking via thank-you page redirects or AJAX confirmation hooks, and it provides reliable delivery logging.

Status: 🔲 Pending — E-Shock to implement Gravity Forms on production site


Root Cause 3: Phone Conversions Not Tracked at All

What Happened

Phone calls are a primary conversion path for a memory care facility. Visitors who dial the phone number directly from the website generate zero conversion data unless a call tracking solution is in place. The campaign's single reported conversion almost certainly reflects only form submissions.

Fix Required

Implement CallRail on the Cordwainer site with the following configuration:

The team had previously deferred CallRail implementation until the site backend was stable. As of this sync, the backend is considered stable enough to proceed.

Status: 🔲 Pending — Sebastian to implement


Campaign Baseline (at time of diagnosis)

Metric Value
Spend ~$300
Clicks 172
CTR ~7%
Reported Conversions 1
Cost Per Click ~$2.98

The CTR and CPC are strong. Conversion volume is the only gap, and it is attributable to tracking failures rather than campaign underperformance.


Action Items from This Sync

Owner Task Status
Mark Fix WP Rocket / GCLID ordering ✅ Done
E-Shock (via Sebastian) Replace form platform with Gravity Forms on production 🔲 Pending
Mark / Sebastian Fix SMTP configuration 🔲 Pending
Sebastian Implement CallRail (no whisper, connect to Google Ads) 🔲 Pending

Generalizable Lessons

Sources

  1. Index
  2. Callrail Implementation