Offline conversion tracking in Google Ads means sending Google the outcomes your website tag can’t see: a lead that qualified, a deal marked Closed Won, a contract signed after a call. You keep the click identifiers from the original visit, and when the outcome happens you upload it so Google can credit the campaign and bid toward it. The lead-form tag knows a form was sent. It doesn’t know what happened to the lead afterward.

The plumbing changed in 2026. Uploads through the Google Ads API are closed to new integrations, enhanced conversions for leads needs an on-site tag, and each route identifies the conversion action differently. This guide covers the routes that are open today, the prerequisites, the matching keys, one worked upload, and how to check what Google actually accepted.

Flow diagram: a form captures the gclid, the CRM stores it with the deal, the deal closes weeks later, and the conversion is uploaded back to Google Ads.
The loop only closes if the click identifiers survive every step in between, including the CRM field that stores them.

Pick an upload route that’s still open

Google’s offline import notice (checked 2026-10-17) says that starting June 15, 2026, offline conversion imports and enhanced conversions for leads uploads “will be migrated to the Data Manager API and blocked in the Google Ads API”. Developer tokens that sent no request between January and June 2026 don’t get legacy access.

I ran into this on a client account on 2026-06-26. A first-time UploadClickConversions call returned CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE, with the message “New integrations for uploading click conversions should use the Data Manager API.” If your integration never uploaded through the Google Ads API, don’t start there.

The routes that work for a new setup:

Route Good fit What you configure
File or Google Sheets import Low volume, a CRM export once a day A template with the exact conversion name
Google Ads Data Manager connectors A CRM Google already connects to The connection and field mapping in Google Ads
Data Manager API Your own code sends the outcome OAuth or a service account, the conversion action ID
Server GTM tag that calls Data Manager You already run a server container Stape’s Data Manager API Conversion Events tag and connection

Stape’s own connection needs a paid plan (its tag can also run on your own Google credentials). Stape’s connection guide (checked 2026-10-17) says the Data Manager API connection “is available for sGTM containers on the Pro subscription plans and higher”.

Prerequisites before the first upload

  • Auto-tagging has to be on, or ad clicks don’t carry a gclid at all. Some iOS traffic arrives with gbraid or wbraid instead, so store those too.
  • The action type has to match. The Data Manager offline events guide requires type UPLOAD_CLICKS, shown in the interface as “Website (Import from clicks)”.
  • If you’ll send hashed email or phone, accept the customer data terms first. You accept them under Goals > Settings when you turn on enhanced conversions for leads.
  • Give a new action a few hours. Google’s import help (checked 2026-10-17) says: “After creating a new conversion action, wait for 4-6 hours before uploading conversions for that conversion action.”

Click IDs and user data are matching keys, not routes

The GCLID and enhanced conversions for leads (ECL) aren’t two competing upload methods. They’re two ways for the same upload to find the click.

A GCLID match needs the identifier captured on the landing page, kept with the lead in a hidden form field or a server record, and sent back with the outcome. If it’s lost anywhere between the form and the CRM, that row has nothing to match on.

ECL matches on a normalized, SHA-256 hashed email or phone. It isn’t upload-only. Google’s ECL setup guide (checked 2026-10-17) needs a Google tag or GTM user-provided data tag on the lead form, firing after submission, so Google sees the hashed data at the moment of the lead. With that tag in place, the GCLID becomes optional in the upload: Google lists it as “Required if you are not implementing a tag to collect user-provided data”. It still recommends sending it when you have it.

So the setup I use stores the click IDs and the consent state when the form is submitted, deploys the user-provided data tag on the form, and uploads the closed lead with both the click ID and the same normalized email or phone.

The conversion is identified differently on each route

A conversion label belongs to website tag actions. Import actions are addressed another way:

Route How the row names the action
File or Sheets import The Conversion Name, with “the same spelling and capitalization” as the action
Data Manager API productDestinationId, the conversion action ID
Stape’s Data Manager tag Conversion Event ID, the ctId value in the action’s URL under Goals > Conversions > Summary
Legacy Google Ads API The resource name customers/{id}/conversionActions/{id}

The account fields are just as easy to swap. In Data Manager, operatingAccount is the Ads account that owns the action, and loginAccount is the account the credential reaches it through. That’s the manager ID when access runs through an MCC.

One worked upload

For each closed outcome, send these fields. The required and recommended split below follows Google’s import help and the Data Manager guide, both checked 2026-10-17.

Field Status Notes
Conversion action Required Name, action ID or resource name, by route
Conversion time Required With a time zone, after the click
Click ID (gclid, gbraid or wbraid) Required unless the row matches on ECL user data with the form tag in place Send it whenever you have it
Hashed email or phone Recommended Normalize, then SHA-256
Order or transaction ID Recommended Deduplication and later adjustments
Value and currency Recommended Decimal value, ISO currency
Ad User Data and Ad Personalization consent Recommended The state you stored, never a default of granted

The time zone trips most file uploads. Google’s import help says to “set the Time Zone value in the ‘Parameters’ row, the ‘Conversion Time’ column, or both.” A file row looks like this. The values are illustrative, and the column names must match the template you download from Google Ads:

Parameters:TimeZone=America/Sao_Paulo
Google Click ID,Conversion Name,Conversion Time,Conversion Value,Conversion Currency,Order ID,Ad User Data,Ad Personalization
Cj0KCQjw-EXAMPLE,Closed Won,2026-10-16 15:42:00,1500,BRL,deal-48213,Granted,Denied

For the API route, the Stripe conversion tracking guide shows a full Data Manager request. On 2026-06-09 I validated that shape with validateOnly: true on a client account and got HTTP 200 with a requestId back.

Illustration of a GCLID conversion import template with three columns: Google Click ID, Conversion Name and Conversion Time.
Illustration of the GCLID file template, not a capture. Google's import help says the import fails if the Google Click ID column is removed; an ECL upload matches on hashed user data instead.

Upload the outcome you want Google to find more of

An upload only steers bidding when the action is one the campaign bids on. Google’s primary and secondary actions page (checked 2026-10-17) says secondary actions are “for observation only”, with one exception: “if the secondary action is part of a custom goal, in which case it’s used for bidding.” Once the action does feed bidding, Google learns from what you send. Upload every form fill and it learns to find form fillers, spam included. Upload a CRM stage that also holds duplicates, cold leads and test records, and the conversion count climbs while revenue stays flat.

Pick a stage your sales team actually uses as a qualification gate, and filter out test records and existing customers before the row leaves your system. When the outcome is a payment, trigger on the processor’s verified webhook rather than the success page. The Stripe guide covers that validation.

Check what Google accepted, then adjust

Read three places. For file imports, Google says “It can take 24-48 hours for data to fully process and reflect in your reports.” For the Data Manager API, a 200 only means received: rows rejected later show up through requestStatus:retrieve, and on 2026-09-26 I saw a request still PROCESSING minutes after the send. Then check the action’s diagnostics in Google Ads for match and rejection details.

When a deal falls through after you uploaded it, what you can do depends on the route. In the Data Manager API, sending the same transactionId to the same action with a new value is handled as an adjustment. Google’s Data Manager upgrade guide (checked 2026-10-17) also says the API “doesn’t support conversion retractions”, and that after a restatement “the conversion count will remain the same”. Restating a lost deal to zero changes its value but leaves it counted.

A full reversal needs an adjustment route that supports it. Google’s adjustments guide (checked 2026-10-17) describes RETRACT for a full reversal and RESTATE for a new value, matched by order ID, accepted within 54 days, and best uploaded at least 24 hours after the original conversion.

What it costs

Google doesn’t charge for imports. A file or connector route costs nothing beyond the time to run it. A server container on Stape costs US$20 a month on Pro, or US$17 a month billed annually, for up to 500K requests (checked 2026-10-17), and Pro is the minimum plan for its Data Manager connection. The server-side GTM guide compares hosting options, and the Google Ads server-side troubleshooting checklist covers the setup traps once rows start flowing.

ATA’s Google Ads container for this upload path is in development, so the CRM-side qualification rule above is still yours to define.