Upload Offline Conversions: Google Ads action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Customer ID customer_id	string	Required	Google Ads customer ID (no dashes)
Conversion Action Resource Name conversion_action	string	Required	Full resource name of the conversion action
Google Click ID (GCLID) gclid	string	Required	The GCLID captured from the original ad click
Conversion Date Time conversion_date_time	string	Required	Conversion timestamp with timezone offset
Conversion Value conversion_value	number	Optional	Numeric value of the conversion
Currency Code currency_code	string	Optional	ISO 4217 currency code (e.g. USD, EUR)
Manager Account ID login_customer_id	string	Optional	MCC manager account ID (optional)

Sample request

{
  "customer_id": "{{trigger.customer_id}}",
  "conversion_action": "customers/1234567890/conversionActions/333",
  "gclid": "{{trigger.gclid}}",
  "conversion_date_time": "2025-01-15 10:30:00+00:00",
  "conversion_value": "{{trigger.conversion_value}}"
}

Returns

{
  "results": [
    {
      "gclid": "Cj0KCQ...",
      "conversionAction": "customers/1234567890/conversionActions/333",
      "conversionDateTime": "2025-01-15 10:30:00+00:00"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Upload Offline Conversions.

What does the Upload Offline Conversions action do in Google Ads?

Pushes offline conversions (sales that closed via phone, sales-rep follow-up after ad click) back to Google Ads using gclid attribution. Improves Smart Bidding accuracy by feeding the full conversion picture, not just on-site conversions.

What inputs does Upload Offline Conversions require?

Required: Customer ID, Conversion Action Resource Name, Google Click ID (GCLID), Conversion Date Time. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Google Ads returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Upload Offline Conversions support batch operations?

Yes. Run Upload Offline Conversions inside a Loop node to process arrays. Tiny Command handles Google Ads's rate limits automatically so you don't have to throttle manually.

More actions