How to Track Google Ads Offline Conversions via Webhooks and GCLID

Relying solely on browser-side purchase or form-fill conversions forces Google Ads Smart Bidding algorithms to optimize for lead quantity rather than actual pipeline revenue. In high-ticket e-commerce, SaaS, and B2B workflows, the real conversion event happens offline days or weeks later inside a CRM: a lead status changing to Qualified Opportunity, a contract signed, or a deal marked Closed-Won.

Without passing these pipeline milestones back to Google Ads, the algorithm treats low-quality spam leads with the same weight as enterprise contracts. Furthermore, as client-side signals face friction from consent banners—as detailed in our troubleshooting guide for Consent Mode v2 unassigned traffic—server-to-server and API-driven conversion imports have become mandatory for ROAS protection.

This technical guide walks through capturing the Google Click Identifier (gclid), storing it deterministically across your lead lifecycle, and dispatching conversion adjustments back into the Google Ads API via automated webhooks.

The Architecture of Offline Conversion Stitching

The conversion loop requires three persistent milestones:

1. Capture: The browser extracts the gclid query parameter on arrival and saves it to a first-party cookie or persistent local store.
2. Sync: The identifier passes silently through hidden form fields into your CRM alongside contact properties.
3. Dispatch: When a deal reaches a target lifecycle stage, a webhook triggers a server request (via Zapier, Make, or custom API endpoints) delivering the gclid, timestamp, conversion value, and currency back to Google Ads.

Step 1: Capture and Persist GCLID in the User’s Session

Visitors frequently browse multiple pages before submitting a lead form. If your tracking script only checks the URL query parameter on the specific form page, the gclid is lost during internal navigation.

To mitigate this, execute this lightweight script via Google Tag Manager on all pages. It inspects the URL, captures any active gclid, and persists it into a first-party cookie named gclid_val with a 90-day retention window:

JavaScript

function setGclidCookie() {
  var urlParams = new URLSearchParams(window.location.search);
  var gclid = urlParams.get('gclid');
  
  if (gclid) {
    var date = new Date();
    date.setTime(date.getTime() + (90 * 24 * 60 * 60 * 1000));
    var expires = "; expires=" + date.toUTCString();
    document.cookie = "gclid_val=" + gclid + expires + "; path=/; SameSite=Lax; Secure";
  }
}
setGclidCookie();

If you are using managed cloud endpoints—such as the setups evaluated in our Stape vs. AWS Server GTM infrastructure comparison—you can alternatively write this cookie directly via HttpOnly server headers to bypass browser storage restrictions entirely.

Step 2: Inject the Value into Hidden Form Fields

Configure your web forms (HubSpot, Marketo, Gravity Forms, etc.) with a hidden input named gclid.

Then, trigger this JavaScript snippet on DOM Ready to read the cookie and inject the string into the input prior to form dispatch:

JavaScript

function populateGclidField() {
  function getCookie(name) {
    var value = "; " + document.cookie;
    var parts = value.split("; " + name + "=");
    if (parts.length === 2) return parts.pop().split(";").shift();
  }
  
  var gclidValue = getCookie("gclid_val");
  var hiddenField = document.querySelector('input[name="gclid"]');
  
  if (gclidValue && hiddenField) {
    hiddenField.value = gclidValue;
  }
}
populateGclidField();

Step 3: Configure the Webhook Conversion Payload

When your sales pipeline transitions a deal to an approved conversion stage (e.g., Contract Signed), your CRM emits an outbound webhook. The endpoint constructs a JSON payload conforming to the Google Ads API uploadClickConversions specification:

JSON

{
  "conversions": [
    {
      "gclid": "TeSt_9843",
      "conversionAction": "customers/1234567890/conversionActions/987654321",
      "conversionDateTime": "2026-09-24 14:32:00-04:00",
      "conversionValue": 12000.0,
      "currencyCode": "USD"
    }
  ],
  "partialFailure": true
}

Critical API Payload Requirements:

• conversionDateTime formatting: Must include the timezone offset (e.g., -04:00 or +02:00). Omitting the offset will lead to payload rejection.
• Upload latency windows: Uploads must occur within 90 days of the original ad click. Furthermore, sending a conversion within 4–6 hours of the initial click often fails because Google’s ad-click processing queue requires a brief indexing window.

Step 4: Verification and QA via Google Ads Diagnostics

1. Navigate to Google Ads > Goals > Conversions > Summary.
2. Select your offline conversion action and open the Uploads tab.
3. Review the execution log:
   • Successful uploads: Confirm the click IDs match historical CRM lead records.
   • Upload errors: Common errors include CLICK_NOT_FOUND (invalid or expired test GCLIDs) and CONVERSION_ALREADY_EXISTS. Much like deduplicating events with our client-side GA4 local storage method, Google Ads will reject repeated uploads possessing the exact same gclid and timestamp.

Frequently Asked Questions

What happens if iOS users do not have a GCLID due to tracking restrictions?

For traffic arriving via iOS or environments where GCLID parameters are omitted, configure Enhanced Conversions for Leads. This framework relies on hashed first-party user data (SHA-256 encoded email addresses and phone numbers) to stitch conversions when click IDs are absent.

Can I pass offline conversions to other ad networks simultaneously?

Yes. If your CRM also stores click identifiers from other sources (such as Meta’s fbclid), you can broadcast conversion events simultaneously using our Meta CAPI deduplication pipeline to keep cross-channel ROAS aligned.

How often should offline webhooks be dispatched?

While batch uploading once daily via CSV is possible, real-time webhooks (or hourly batched API calls) are strongly recommended. Faster feedback loops allow Google’s Smart Bidding models to adjust target CPA and ROAS bids before market conditions shift.

---