Push lead conversion event to Google Ads Conversion API

Overview

Use the Lifecycle Rule action Push Conversion to Ad Account with Ad platform Google Ads to upload lead conversions to Google Ads through Data Manager (events:ingest).

Prerequisites

• A Google Ads conversion action that accepts offline / uploaded conversions
• A Google connection under Admin → Ad Account Connections
• A GCLID available on the lead via marketing source or a lead attribute
• Permission to create and edit Lifecycle Rules

Connect Google Ads in Chakra

1. Go to Admin → Ad Account Connections (/admin/ad-account-connections).
2. Connect Google and grant Data Manager access so Chakra can upload conversions.
3. If the connection later shows needs re-auth, use Reconnect on that Google row so existing Lifecycle Rules keep the same connection id.

Create a conversion action in Google Ads

1. In Google Ads, create a conversion action that accepts uploaded / offline conversions for leads.
2. Copy the numeric Conversion Action ID — you will paste it into the Lifecycle action.

Create the Lifecycle Rule

1. Create a Lifecycle Rule that fires when a lead converts (for example process:state-change:post with a condition on the converted state).
2. Add action Push Conversion to Ad Account.
3. Set Ad platform to Google Ads.
4. Fill in the Google fields below, then save and enable the rule.

Action fields

• Google connection (required) — OAuth connection from Ad Account Connections
• Google Ads Account Id (required) — customer id that owns the conversion action
• Google Ads login account id (optional) — manager / MCC id when the connected user reaches the Ads account through a manager
• Conversion Action ID (required) — numeric id from Google Ads
• Event name (optional) — label only; matching uses Conversion Action ID
• GCLID source — Marketing source (process.marketingSource.gclid) or Lead attribute
• Procedure + GCLID attribute — required when GCLID source is Lead attribute
• Event ID (dedupe) (optional) — maps to Google order_id
• Value / Currency (optional)
• User data mappings (recommended) — email, phone, and other identity fields
• Custom data / Click ID overrides (optional) — advanced overrides

How attribution works

Google matching works best when the event includes a gclid and/or strong identity fields such as email or phone. Events with weak identity may still be sent, but they are less likely to match in Google Ads.

Verify

1. Convert a test lead that has a GCLID (from marketing source or the mapped attribute).
2. Open the Google connection in Ad Account Connections and check conversion logs for a successful upload.
3. Confirm the conversion in Google Ads reporting (it can take time to appear).

Notes

• Reconnect Google if the token expires so Lifecycle Rules can keep using the same connection id.
• Set the login / manager account id only when the connected Google user accesses the Ads account through an MCC.
• See also the Lifecycle Rule overview under Platform → Features for how events and actions work together.