> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Ads Voice AI Integration Guide

> Connect DialNexa voice AI with Google Ads to report qualified offline call conversions and improve campaign measurement with consent controls.

The **Google Ads voice AI integration** closes the measurement gap between an ad click and a valuable phone outcome. Use it to report confirmed offline conversions such as a qualified lead, booked visit, or completed sale, not to let the voice agent modify campaigns.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Google Ads connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Google Ads is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Google Ads voice AI integration

Use Google Ads when:

* Paid search or Performance Max campaigns generate phone leads.
* Click or lead identifiers are captured before the call and retained with consent.
* Conversion actions have precise business definitions and counting rules.
* Uploads can be deduplicated, monitored, and reconciled with CRM outcomes.

<Tip>
  **Best first workflow:** Upload one offline conversion only when a call meets the documented qualified-lead rule, using the stored ad-click identifier and call ID for traceability.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Google Ads account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Google Ads

| Connection method                                   | Use it when                                                  | Important limit                                                             |
| --------------------------------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------- |
| Workspace connector                                 | Google Ads appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Google Ads data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Google Ads should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Google Ads and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Google Ads voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Google Ads

* DialNexa call ID, call direction, status, and final outcome
* Caller name, phone number, email, and matched customer or account ID
* Structured fields collected during the call, including consent where required
* Short operational summary, requested next step, owner, and due date
* Transcript or recording link only when your privacy policy allows it
* Google Ads record ID, record URL, update timestamp, and integration result

## High-value Google Ads voice AI measurements

| Confirmed call outcome              | Google Ads result                            | Human control                                              |
| ----------------------------------- | -------------------------------------------- | ---------------------------------------------------------- |
| Lead meets qualification rules      | Upload the qualified offline conversion      | Define the rule with sales and marketing                   |
| Appointment or sale completes later | Upload the appropriate downstream conversion | Use the correct conversion time and value policy           |
| Lead is duplicate or unqualified    | Do not upload a positive conversion          | Keep rejection reasons in the CRM                          |
| Campaign changes are suggested      | Send insight to a marketing owner            | Keep bids, budgets, audiences, and campaigns human-managed |

## Verify the Google Ads integration

Run a test call and confirm that:

1. The customer account, conversion action, click or lead identifier, and conversion time are correct.
2. The outcome satisfies the documented qualified-lead, appointment, or sale rule.
3. The DialNexa call ID prevents duplicate uploads.
4. Value, currency, consent, and customer-data handling follow the approved policy.
5. Upload errors and conversion diagnostics are reviewed before using the data for optimization.

## Troubleshoot Google Ads integration issues

| Problem                                  | What to check                                                                                                                                     |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Google Ads is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                     | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| Conversion is not attributed             | Check account, conversion action, click or lead ID, conversion time, consent, and upload diagnostics                                              |
| Duplicate conversions appear             | Use the DialNexa call ID as the upload key and audit every offline-conversion sender                                                              |
| The live call becomes slow               | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)