> ## 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.

# Meta Ads Voice AI Integration Guide

> Connect DialNexa voice AI with Meta Ads to report qualified phone outcomes and improve lead-ad measurement with consent and deduplication.

The **Meta Ads voice AI integration** helps marketing teams measure which Facebook or Instagram leads become valuable phone outcomes. Send confirmed conversion events through an approved server-side process, and keep campaign edits outside the voice workflow.

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

## When to use the Meta Ads voice AI integration

Use Meta Ads when:

* Meta lead ads or click-to-message campaigns generate phone follow-up.
* Lead and campaign identifiers are stored with the CRM record.
* Conversion events have documented definitions, consent, and data-use rules.
* Event IDs prevent browser, CRM, and server events from being counted twice.

<Tip>
  **Best first workflow:** Send one server-side qualified-lead event only after the voice call meets the agreed rule, using a stable event ID and the permitted attribution fields captured with the lead.
</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 Meta 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 Meta Ads

| Connection method                                   | Use it when                                                | Important limit                                                             |
| --------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Meta 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 Meta 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)         | Meta Ads should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Meta Ads and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Meta 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 Meta 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
* Meta Ads record ID, record URL, update timestamp, and integration result

## High-value Meta Ads voice AI measurements

| Confirmed call outcome                     | Meta result                              | Human control                                       |
| ------------------------------------------ | ---------------------------------------- | --------------------------------------------------- |
| Lead meets qualification rules             | Send the documented qualified-lead event | Agree on the rule with sales and marketing          |
| Appointment or purchase completes          | Send the correct downstream event        | Apply your approved value and attribution policy    |
| Lead is duplicate, invalid, or unqualified | Do not send a positive conversion        | Keep the reason in the source system                |
| Campaign change is proposed                | Notify the marketing owner with evidence | Keep budgets, targeting, and creative human-managed |

## Verify the Meta Ads integration

Run a test call and confirm that:

1. The data source, event name, event time, attribution fields, and action source are correct.
2. The outcome satisfies the documented qualified-lead, appointment, or purchase rule.
3. A stable event ID prevents duplicate browser, CRM, and server events.
4. Consent, permitted matching data, value, and currency follow the approved policy.
5. Event diagnostics are reviewed before the data is used for campaign optimization.

## Troubleshoot Meta Ads integration issues

| Problem                                | What to check                                                                                                                                     |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Meta 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                                                                    |
| Event is not matched or attributed     | Check data source, event name, time, action source, permitted matching fields, and diagnostics                                                    |
| Duplicate events appear                | Use one stable event ID across browser, CRM, and server send paths                                                                                |
| 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)