Google Ads offline conversions for affiliate campaigns

A Google Ads offline conversion upload connects a verified conversion to the original Google ad click. It is useful when the important event happens outside the browser pixel path: an affiliate network approves a sale, a lead passes validation, or a backend confirms payment.

Tracked supports Google Ads offline click-conversion uploads using the Google click identifiers captured with the campaign visit. Its current provider path uses Google’s Data Manager API. The workflow is provider-specific. It is not a blanket claim of enhanced conversions or universal CAPI.

Still choosing your tracking setup? The Google Ads affiliate tracker buying checklist covers the evidence to verify before moving a campaign's spend.

“Google CAPI” usually means a Google conversion API path

“Google CAPI” is common search shorthand, but Google’s current product names are more precise. Google documents the Data Manager API for event ingestion, the Google Ads API for conversion management, the Google tag for browser measurement, and enhanced conversions for leads for offline imports that include approved first-party data.

Tracked’s shipped path uses the Data Manager API events:ingest method to send click-based offline conversion events. It sends the conversion timestamp, value, currency, Tracked conversion ID, available gclid/gbraid/wbraid, and an eligible consent signal. It does not send hashed customer identifiers, so it does not claim enhanced conversions for leads.

Read Google’s Data Manager API offline-conversions guide when a search result says “Google CAPI.” Use the provider’s exact product name when you configure a connection or troubleshoot a rejected event.

Google Ads postback vs. offline conversion import

An affiliate postback and a Google upload are two different hops.

1. Google appends a click identifier to the ad destination.
2. Tracked captures that identifier with the visit.
3. An advertiser or affiliate network calls Tracked’s inbound /postback after it confirms the conversion.
4. Tracked records the conversion and queues a Google offline event.
5. Tracked sends the event to Google’s Data Manager API, mapped to an enabled UPLOAD_CLICKS conversion action.

The /postback request is not a Google Ads outbound API. It accepts the callback fields that the sending network provides, while the later Data Manager request uses Google’s event contract. A successful callback response therefore proves that Tracked received the event, not that Google accepted or attributed the upload.

The attribution chain

An offline conversion path has four links:

1. For an eligible click path, Google supplies a click identifier such as gclid, gbraid, or wbraid with the landing-page request.
2. The tracker captures that identifier with the campaign click.
3. A later postback reports the verified conversion to the tracker.
4. The tracker uploads a conversion associated with the stored Google identifier.

If any link is missing, the conversion may still be real but Google cannot associate it with the original click.

Which Google click IDs matter?

Google documents three identifiers for click-conversion imports:

• gclid, captured from a Google ad click's landing-page URL;
• gbraid, used when a click on the web sends the visitor to an iOS app;
• wbraid, used when a click in an iOS app sends the visitor to a webpage.

The identifier depends on the ad and destination path. Store the value Google supplies rather than trying to manufacture or translate it.

Google’s offline conversion documentation also describes the conversion action, timestamp, value, currency, order ID, consent, batching, and diagnostics used by the upload API.

Step 1: capture the click identifier

The click identifier arrives as a query parameter when the ad and destination path support it. Check the final landing-page request and confirm Tracked stored the value with the campaign click; a URL-template preview alone does not prove capture. Tracked stores the identifier separately from descriptive UTMs.

That separation matters:

• UTMs describe the source, campaign, or creative;
• the Google click ID identifies the individual ad click used for attribution.

A campaign can use both. One does not replace the other.

If a landing page forwards visitors to another page or offer, pass only the parameters the destination needs. In Tracked, forwarding is macro-driven. Do not assume every incoming query parameter is automatically appended to every offer URL.

Step 2: receive the verified conversion

The strongest conversion source is the system that can confirm the business event.

For affiliate campaigns, that source is often an advertiser or network postback. It can report:

• the Tracked click reference;
• conversion type;
• revenue or payout;
• currency;
• timestamp;
• order or conversion ID.

Tracked records the inbound conversion first. Provider delivery runs separately, so a temporary Google failure does not need to turn a valid inbound conversion into an error.

Step 3: map the Google conversion action

Google requires a conversion action that exists in the relevant Ads account. For this offline path, the action must be an enabled UPLOAD_CLICKS action owned by the Google Ads conversion customer. The uploaded event must target that action rather than relying on a vague event-name guess.

Use separate actions when the business meaning differs. A lead, qualified lead, purchase, and refund are not interchangeable simply because they all arrived through the same campaign.

In Tracked, campaign event mappings connect the canonical conversion type to the provider action. A missing mapping should be treated as a setup issue, not silently sent as another event.

Tracked’s setup check also requires the Data Manager permission, a resolved conversion customer, at least one enabled action mapping, and evidence that a Google click was observed for the connected campaign in the last 90 days. That last check confirms that the connection has a usable click path; it is not a promise that every older click remains inside the account’s attribution window.

Step 4: upload value, currency, and time

Attribution needs more than an identifier. The upload should use the conversion time and the business value known by the verified source.

Check these fields before going live:

• conversion timestamp and timezone;
• conversion action;
• value;
• currency;
• order ID where available;
• consent state;
• test status.

Do not substitute click time for conversion time. The click explains where the visitor came from; the conversion timestamp explains when the business event occurred.

What Tracked sends today

Tracked’s Google delivery path supports Data Manager API offline-conversion uploads associated with gclid, gbraid, or wbraid. It queues the conversion after storage, applies the configured action mapping, includes available value and currency, and records delivery state. Requests are sent in batches of up to 200 events and can be polled for provider status.

The implementation is consent-aware and does not describe a denied-consent conversion as deliverable. It uses click identifiers rather than claiming an enhanced-conversions workflow based on hashed customer information.

That boundary keeps the product claim specific: Google Ads offline click-conversion upload is available. Enhanced conversions are a separate capability.

How to verify the setup

Use a test conversion before relying on production reporting.

1. Open the campaign URL with a valid test click identifier or the approved provider test path.
2. Confirm Tracked recorded the click under the correct campaign and provider.
3. Send the test conversion with a unique conversion ID.
4. Confirm the conversion attached to the intended click.
5. Check the mapped Google action, value, currency, and timestamp.
6. Inspect the delivery result rather than stopping at “queued.”
7. Check Google’s conversion diagnostics after its normal processing delay.

A successful inbound postback proves that Tracked recorded the conversion. It does not, by itself, prove that Google accepted the upload.

Common failure modes

Missing click ID

The visit was tracked, but the configured Google parameter was not present or stored. Verify the final ad URL and campaign provider settings.

Wrong conversion action

The campaign maps the event to an action from another account or to an action that is not configured for click uploads.

Duplicate conversion

The same business event was reported more than once without a stable order or conversion ID. Use a durable identifier and test retry behavior.

Consent prevents delivery

The conversion exists in Tracked, but the applicable consent state does not permit the provider upload. Treat that as an intentional skip, not a network outage.

The connection is not ready

The account may be connected while the delivery path is not configured. Check the Data Manager permission, conversion customer, enabled Import from clicks action, event mapping, and recent Google click evidence before debugging the postback.

Provider processing delay

The request was accepted but has not appeared in campaign reporting. Separate delivery acceptance from report availability.

Where Tracked fits

Tracked connects the ad click, hosted or routed page, offer click, verified conversion, and Google feedback path in one campaign workspace. The buyer can inspect the conversion journey and return to the page or routing configuration that produced it.

For a concrete affiliate-network example, the ClickBank-to-Google conversion guide traces both the Google click identifier and the separate Tracked offer-click ID through a ClickBank sale.

The practical rule

Capture the Google click identifier at arrival, accept the conversion from the system that can verify it, map the correct conversion action, and inspect the provider result. Do not call the setup complete merely because the inbound postback returned 200.

Frequently asked questions

Which Google click IDs can Tracked use for offline conversions?

Tracked’s Google click-conversion workflow handles the Google identifiers captured with an eligible campaign visit, including gclid, gbraid, and wbraid where applicable. The identifier still needs the correct conversion action, timestamp, value, currency, and consent state.

Is this the same as Google enhanced conversions?

No. This article describes click-based offline conversion uploads. It does not claim an enhanced-conversions implementation or imply that customer data is collected for matching.

Does a successful postback mean Google recorded the conversion?

No. The inbound postback proves only that Tracked received the event. Confirm that it matched the intended click, entered the Google delivery path, and received a provider result before treating the chain as verified.

Is “Google CAPI” the same as enhanced conversions?

No. “Google CAPI” is informal search language for a server-side Google conversion path. Enhanced conversions for leads are a specific Google workflow that supplements an offline conversion with approved, normalized, and hashed first-party data. Tracked’s current upload path uses click identifiers and does not claim enhanced conversions.

Google’s Data Manager API events overview, offline-conversions guide, events:ingest reference, and Google Ads offline-conversion documentation are the source references for the current terminology and payload boundary.

Start free and build a Google Ads conversion path.