Connect Google Ads Enhanced Conversions
Upload conversion signals using Google authorization.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
customer_id | Google Ads customer ID; hyphens are removed. |
conversion_action | Numeric action ID or full conversion-action resource name. |
login_customer_id | Optional manager-account ID. |
offline_feed_crm | Optional CRM won-stage feed. |
conversion_action_offline | Optional separate conversion action for CRM wins. |
Connect
Open Integrations, find Google Ads Enhanced Conversions, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Create a secondary conversion action in Google Ads for initial verification.
- Save the customer and action IDs in AXO, then use Connect Google account in the saved connector. Authorize an account with access to that customer.
- For CRM wins, select a separate secondary action before enabling the offline feed. Uploads are not retracted if a deal reopens.
Verify the result
The test sends a validation-only conversion. Online delivery requires gclid; organic/direct conversions without it are logged as skipped. Verify actual uploads in Google’s diagnostics.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Reconnect after token-refresh errors. google_ads_developer_token_env_missing is an AXO deployment setting, not a field you can fix in the drawer. Google has retired developer-token requirements, but this AXO check still requires the configured value.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Provider reference: Google Ads developer-token migration. Reviewed October 2026.
Next: create an event-triggered action, or implement a webhook receiver.