Meta Ads call tracking for Facebook and Instagram

Send the calls your Meta ads bring in back to Meta as events, so your campaigns learn which clicks turn into callers worth having.

Meta call tracking integration

What is Meta call tracking with Nimbata?

Nimbata's Meta call tracking integration sends the calls your Meta ads bring in to your pixel through the Conversions API, as phone call events under the names you choose, so Events Manager and your campaigns count the calls that matter.

Alongside dynamic number insertion, Nimbata's tracking script saves the fbclid from the visitor's landing page, or the _fbp cookie Meta's pixel set. When a call meets your workflow's conditions, Nimbata sends it to Meta with that click, the caller's phone number hashed and the visitor's IP address and user agent, so Meta can match the call to the ad. Nimbata AI can decide which event each call becomes, a booked appointment or a qualified lead. The call's value isn't sent. See call attribution for how Nimbata ties each call to its source, and our Facebook call tracking guide for the basics.

From Nimbata

Into Meta

  • Call activity

    Event time, the call's start, Caller's phone, hashed

  • Marketing attribution

    fbc or fbp, Landing page URL, Visitor's IP and user agent

  • Call intelligence

    Event name, picked by outcome, Action source, phone call

Events Manager

Qualified callNimbata · Conversions API

Server

Event

Event time
9:41 AM, the call's start
Phone number
Hashed (SHA-256)

Customer information

Click ID (fbc)
From the fbclid
Event source URL
acme.com/pricing
IP address, user agent
The visitor's

Event details

Event name
Qualified call
Action source
Phone call

In Meta

See every call in Meta

Your pixel's events, the way you see them in Events Manager. Everything numbered came from Nimbata.

Acme Co. Pixel

EventsIntegrationLast receivedTotal events
Qualified call1Conversions API9:41 AM42
Booked call1Conversions APIYesterday18
PageViewMeta Pixel9:38 AM2,406

Qualified call

Action source1
Phone call
Integration
Conversions API
Click ID (fbc)2
Received
Phone number3
Received, hashed
IP address, user agent3
Received
Value
Not sent
  1. 1Conversions API

    Every qualifying call becomes a server event

    Calls reach your pixel through the Conversions API as phone call events, under the event name you chose for each outcome.

  2. 2Ad click

    Matched to the click on your ad

    Each event carries fbc, built from the fbclid on the visitor's landing page, or fbp from the _fbp cookie. A call with neither isn't sent.

  3. 3Customer information

    More for Meta to match on

    The caller's phone number, hashed, and the visitor's IP address and user agent go with each event. Calls from hidden numbers go without the phone.

Automation

An event for every outcome

Test it. AI checks the call first, and its outcome picks the event. A booked appointment goes to Meta as its own event, a qualified lead as another, and a call that isn't a lead is never sent.

A workflow, top to bottom: when a call ends, AI analyzes it and the outcome decides the conversion. A booked appointment goes to Meta as Booked call event, a qualified lead as Qualified call event, and a call that is not a lead is tagged and never sent. Then the sales channel in Slack hears of a lead, and it is logged on the caller’s HubSpot contact. Test it with the choices beside it.

Test this workflowSandbox

Caller
Call outcome

Run log

  1. Call ended, 4m 12s9:41:02
  2. AI: appointment booked, value $4809:41:05
  3. Meta: Booked call event sent9:41:06
  4. Slack: #sales alerted, caller and source9:41:07
  5. HubSpot: call logged on the contact9:41:07

What you can do with call events

More than a call count. Nimbata decides which calls Meta sees and what each one is called.

  1. 01An event for each outcome

    Send booked appointments and qualified calls as their own events, each under the name you give it, and optimize your campaigns for the one that matters.

  2. 02Matched to the ad click

    Nimbata saves the fbclid from the landing page, or the _fbp cookie, and sends it with the call so Meta can tie it to the ad. Calls with neither aren't sent.

  3. 03AI decides what counts

    Ask Nimbata AI a question about the call, and only the calls it says yes to become events.

  4. 04Any pixel you manage

    Pick a pixel from the businesses you connected for each event, or enter a dataset ID by hand.

  5. 05Test before you go live

    Send a test event from Nimbata and see whether Meta received it before a real call goes through.

How it works

Connect Nimbata to Meta in three steps

No code. Sign in with Facebook, name your events, and pick which calls count.

  1. Sign in with Facebook Login for Business

    Choose Meta under Integrations and sign in. Nimbata gets a business integration token, so there's no pixel to share by hand.

    1Connect

  2. Name your events

    For each event, pick a pixel or enter a dataset ID, and type the event name Meta should show.

    2Name

  3. Pick which calls count

    Add Meta to a workflow step and give it conditions, such as first-time callers, calls over a minute, a source or campaign, a tag, or an answer AI found on the call.

    3Choose

Customers

Trusted by marketers who need better attribution

Teams use Nimbata to see which calls make money and to settle questions about lead quality.

  1. 50%More conversionsnovi.digital

    Portrait of Aaron CreweAaron CreweFounder & Managing Director, Novi.Digital

    “With Nimbata, we can see which phone calls make money and reinvest away from the ones that don’t.”

    Discover their strategy

  2. 4.5xGrowthService24

    Portrait of Stefan MitrovicStefan MitrovicPerformance Marketer, Service24

    “Before Nimbata, everything was manual CPC. Every day was a new battle. Now, the algorithm knows exactly which jobs bring more money.”

    Discover their strategy

  3. 200+Phone conversions a monthSkyleads

    Portrait of Vasileios SpanoudakisVasileios SpanoudakisFounder, Skyleads

    “When clients question lead quality, I just play the call recording. No more debate.”

    Discover their strategy

Rated 4.7 on G2

Read G2 reviews

Everything you need to know about Nimbata + Meta

What does the Nimbata + Meta integration do?

It sends the inbound calls your Meta ads bring in to your pixel through Meta's Conversions API, as phone call events under the names you choose, so Events Manager and your campaigns count them.

How do I connect Nimbata to Meta?

Open Integrations in Nimbata, choose Meta and sign in with Facebook Login for Business. Nimbata gets a business integration token, so you don't share your pixel by hand. Pick a pixel, or enter a dataset ID, type an event name, then add Meta as a step in a workflow. There's no code to write.

What does Nimbata send to Meta?

Each call goes as a server event with the action source phone call, your event name, the call's start as the event time and the landing page as the event source URL. For matching it carries the caller's phone number, hashed, the visitor's IP address and user agent, and fbc, built from the fbclid, or fbp, from the _fbp cookie.

Does Nimbata send the call's value to Meta?

No. Value, currency and email aren't sent to Meta. To tell outcomes apart, send each one as its own event, such as a booked call and a qualified call.

Which calls can be sent to Meta?

Calls whose visit had an fbclid on the landing page or Meta's _fbp cookie, which Nimbata's tracking script reads. A call with neither isn't sent. Calls from hidden numbers are sent without the caller's phone.

Can I send different calls as different events?

Yes. Add a row for each pixel and event name, and each workflow step picks the rows it sends to, so separate workflows can send booked appointments and qualified calls as their own events.

Can I choose which calls count?

Yes. Meta is a step in a Nimbata workflow, so you set its conditions, such as call outcome, duration, first-time callers, source or campaign, tags, value, rating, or an answer Nimbata AI found on the call.

Does it work for forms, outbound calls and texts?

No. Meta runs as a workflow step on inbound calls only, when a call starts, when it ends or when you run it by hand. Form submissions, outbound calls and texts aren't sent.

How quickly do events show up in Meta?

Nimbata sends a call when its workflow runs, with no waiting period, and Meta then processes it on its side. A call more than 7 days old is sent with the time it's sent, since Meta won't take an older event time.

Will a call be counted twice?

No. Nimbata sends each call once per event, even if the workflow runs on it again.

Does Nimbata import campaigns or ad spend from Meta?

No. Nimbata sends events to Meta and lists your pixels, but doesn't read your campaigns, ads or spend. Each call's source and campaign come from your tracking numbers and the visitor's landing page.

What happens if a send fails?

Nimbata doesn't retry it on its own. If Meta revokes Nimbata's access, the integration disconnects and Nimbata emails you. On the Agency plan and the trial, the Integration Events log shows every attempt, with what was sent and Meta's reply.

Which Nimbata plans include the Meta integration?

The Marketing and Agency plans, and the 14-day free trial. See pricing for everything else each plan includes.

Still unsure? Talk to a human

Your next call belongs in Meta.

Connect your pixel and send Meta the calls that turn into customers.

  • 14-day free trial, no credit card
  • Billed per answered call
  • 24/7 expert support
  • No long-term contracts

Nimbata + Meta

Part of Integrations