Objective

Pull a recent converted Litify Intake with a GCLID and explain how the received guidance was incomplete or operationally wrong for Google Ads offline conversion tracking.

Selected recent converted lead

Intake: INT-26053055395
Salesforce Id: a0CUV00006kWLBq2AO
Status: Converted
Created: 2026-05-30 11:52:26 UTC
Converted date: 2026-06-01 20:37:53 UTC
Retainer signed date: 2026-06-01 19:48:59 UTC
GCLID_Custom__c: blank
GCLID__c: populated
Email and phone: populated, not pasted in this note

This record appears in the latest local Google Ads Data Manager export as a Litify - Signed Retainer (Web Form) row with conversion time 2026-06-01T15:48:59-04:00.

Counts pulled live

Converted Intakes with GCLID_Custom__c populated: 0
Converted Intakes with GCLID_Custom__c blank and GCLID__c populated: 62
Converted Intakes in the last 90 days with GCLID_Custom__c blank and GCLID__c populated: 14

What was wrong or incomplete

The API-name confirmation itself was correct: GCLID_Custom__c exists and is the correct destination for the fixed custom website form going forward.

The operational problem was that the guidance treated this as only a simple server-side payload-field issue. In reality, there were three separate layers:

  1. Frontend attribution: stale browser storage could override the fresh URL gclid.
  2. Website handler mapping: the handler needed to write the live browser gclid into GCLID_Custom__c.
  3. Downstream OCT automation: existing converted/signed records and prior export logic still show GCLIDs in legacy GCLID__c.

So if Drew's automation only queries GCLID_Custom__c, it will miss current historical converted examples such as INT-26053055395. If it only queries GCLID__c, it will miss newly fixed custom-form submissions going forward. The safe transition is to read GCLID_Custom__c for the custom form and coalesce with GCLID__c only where legacy lanes still depend on it.

OCT impact

Offline conversion tracking depends on a usable click identifier at the exact moment a real business event happens. For this pipeline, the row needs at minimum:

conversion_action
gclid
conversion_date_time

Email and phone can help enhanced matching, but they do not replace a missing or wrong GCLID unless a separate enhanced-conversions fallback is intentionally configured.

If the wrong field is read, Google Ads receives blank GCLID rows or no rows at all, so signed/converted cases never train Smart Bidding. If a stale browser GCLID is saved, the upload can attribute the conversion to the wrong click, fail to match inside the lookback window, or teach Google Ads from polluted data. Either way, the system undercounts the ads that actually produced signed cases and over-trusts weaker signals such as raw form submissions.

Skill update made