Facebook call tracking connects each phone call to the Meta ad, ad set and campaign that produced it. Calls from a call ad are tracked with a tracking number in the ad. Calls from people who click through to your website are tracked with dynamic number insertion and Meta’s click ID (fbclid). Qualified calls can then be sent back to Meta as conversions.
Meta’s ads on Facebook and Instagram are good at getting people to call, and poor at telling you what those calls were worth. Ads Manager can count taps on a call button. It cannot tell you that the caller booked a job, asked for a quote or dialed the wrong number.
This guide covers what Meta reports on its own, the two kinds of calls a Meta campaign produces and how each is tracked, how to set it up in Nimbata, and how to send the calls that matter back to Meta so your campaigns are measured on leads, not taps.
What Facebook call tracking is
Facebook call tracking is the practice of tying every inbound call to the Meta campaign, ad set and ad behind it, then judging the ad by what happened on the call. “Facebook” is the name most people still search for. In practice it covers every placement you buy through Meta Ads Manager, Instagram included.
It rests on two pieces:
- A tracking number. A phone number that forwards to your business line and records each call with its source. See our guide to call tracking numbers.
- A link back to the ad. For calls made from the ad itself, the link is the number: one number, one campaign. For calls made from your website, the link is the click ID that Meta adds to the landing page address.
What Meta reports about calls, and what it misses
Meta has its own call ads. According to Meta’s call ads page, you create one with the Leads objective and Calls as the conversion location, then enter the phone number people should call. A call button can also be added to an ad that sends people to your website (Meta calls this a call add-on). Call ads run on mobile placements only, and Meta says they can use any phone number, toll-free numbers included.
For these ads, Ads Manager reports a small set of call metrics:
- Estimated call confirmation clicks: roughly how many times people tapped the call button in the confirmation dialog.
- Calls placed to your business after a tap on the ad.
- 20-second calls and 60-second calls: connected calls that lasted at least that long.
- Callback requests, if you turned on the option that lets people ask for a call back.
That is useful, and it is as far as Meta goes. Four things are missing:
- The caller. You get counts, not a list of calls with a number, a time and a recording.
- The outcome. A 60-second call is a proxy. It may be a booked appointment or a long wrong number.
- Calls from your website. Someone who taps your ad, reads your landing page and then calls the number on it is invisible to Meta, unless you send that call to Meta yourself.
- A comparison with other channels. Meta’s numbers live in Ads Manager, apart from your Google Ads and organic calls.
Call tracking fills those gaps. The same idea applies to every paid channel, as our PPC call tracking guide explains.
The two kinds of calls from Facebook ads
A Meta campaign makes the phone ring in two ways, and each needs its own tracking.
| Calls from a call ad or call button | Calls after a visit to your website | |
|---|---|---|
| What the person does | Taps the call button in the ad | Clicks the ad, reads the page, then calls |
| How it is tracked | A tracking number used in the ad | Dynamic number insertion on the site |
| What ties it to the ad | The number itself | The click ID (fbclid) and UTM parameters |
| Detail you get | The campaign or ad set that owns the number | Campaign, ad set and ad, per visitor |
| Can be sent to Meta from Nimbata | No, there is no click to match | Yes, through the Conversions API |
Calls from a call ad or call button
The caller never reaches your website, so there is no page and no script. The tracking happens in the number. Put a tracking number in the call ad instead of your main line, and every call to it is logged with the caller’s number, the time, the duration and a recording, under the source you named.
One number per campaign tells you which campaign made the phone ring. If you need to compare ad sets or audiences, give each its own number. Meta’s developer documentation notes that the number in a call ad has to be from the same country as the audience you target, so pick your tracking numbers to match.
Meta still shows its own counts for these ads. Your call tracking tool adds what was said and what it led to.
Calls after a visit to your website
Most Meta ads send people to a landing page, and many of those visitors call the number they find there. This is where dynamic number insertion (DNI) comes in. A script on your site reads how each visitor arrived and swaps the phone number on the page for a tracking number.
When someone clicks an ad on Facebook or Instagram, Meta adds a click ID, the fbclid parameter, to the landing page address. Meta’s pixel also sets a browser cookie called _fbp. Nimbata’s tracking script saves the fbclid from the landing page, or the _fbp cookie, along with the UTM parameters on the link. When the visitor calls the number they were shown, the call is matched to that visit.
UTM parameters are what give you the names. Add them to the website URL of each ad so the campaign, ad set and ad arrive with the click, and every call shows them in your reports.
How to set up Facebook call tracking in Nimbata
The steps below use Nimbata’s Meta Ads call tracking integration. It is included in the Marketing and Agency plans and in the 14-day free trial.
Step 1: Get your tracking numbers
Create a tracking number for each call ad campaign, and a set of numbers for your website. How many you need for the website depends on your traffic. Our dynamic number insertion guide explains the difference between one number per source and a pool of numbers shared across visitors.
Step 2: Use a tracking number in your call ads
Enter the tracking number as the phone number of the call ad or call button. Calls are forwarded to your business line as before.
Step 3: Add the tracking script to your website
Install Nimbata’s tracking script on every page, the landing pages your ads point to above all. It swaps the number for each visitor and saves the fbclid or the _fbp cookie. Then check that your ads’ website URLs carry UTM parameters for the campaign, ad set and ad.
Step 4: Connect Meta
In Nimbata, choose Meta under Integrations and sign in with Facebook Login for Business. Nimbata receives a business integration token, so you do not have to share your pixel by hand. For each event you want to send, pick a pixel from the businesses you connected (or enter a dataset ID) and type the event name Meta should show, for example “Qualified call”.
Step 5: Choose which calls count
Meta is a step in a Nimbata workflow. Add it to a workflow and set the conditions a call has to meet: first-time callers, calls longer than a minute, a source or campaign, a tag, a rating, or an answer that Nimbata AI found on the call.
Step 6: Send a test event
Send a test event from Nimbata and confirm that Meta received it before real calls go through.
Send qualified calls back to Meta as conversions
Counting calls in your own reports is half the job. The other half is telling Meta which clicks turned into callers worth having.
Meta’s delivery system looks for more people like those who completed the event you report. If the only signal it gets is link clicks or button taps, that is who it finds. Sending real call outcomes gives it a better target. It is the same principle as offline conversion tracking on any ad platform.
The route is Meta’s Conversions API, which accepts events from a server instead of the browser. Each event carries an action source, and Meta’s documentation lists “phone_call” among them, for conversions made over the phone. Nimbata sends each qualifying call this way.
| Sent with each call | Detail |
|---|---|
| Event name | The name you chose |
| Action source | Phone call |
| Event time | The start of the call |
| Click identifier | fbc or fbp |
| Event source URL | The landing page |
| Caller’s phone number | Hashed |
| IP address, user agent | The visitor’s |
| Value and currency | Not sent |
A few rules are worth knowing before you rely on it:
What the integration does and does not do
- Only matched calls are sent. A call needs an fbclid from the landing page or Meta’s _fbp cookie. A call with neither, such as a call straight from a call ad, is not sent.
- Inbound calls only. Form submissions, outbound calls and texts are not sent to Meta.
- No call value. Value, currency and email are not sent. Use a separate event for each outcome.
- Each call is sent once per event, even if the workflow runs on it again.
- Calls from hidden numbers are sent without the caller’s phone number.
- Older calls: Meta accepts an event time up to 7 days old, so a call older than that is sent with the time of sending.
- Failed sends are not retried automatically. On the Agency plan and the trial, a log shows every attempt and Meta’s reply.
Because value is not sent, the way to separate outcomes is by event name. Let Nimbata AI answer a question about each call, such as “Was this a qualified lead?” or “Did the caller book an appointment?”, and send a “Booked call” event for one answer and a “Qualified call” event for the other. A call that is not a lead is never sent.
In Meta, the events arrive under your pixel in Events Manager. Meta decides which events a campaign can count or optimize for, so check in Ads Manager that your call event is offered for the campaigns you want to use it in.
Nimbata does not read your campaigns, ads or spend from Meta. Source and campaign on each call come from your tracking numbers and the visitor’s landing page, so cost figures stay in Ads Manager.
What to measure
Once calls carry their campaign and their outcome, a handful of numbers tell you where the budget should go.
- Calls by campaign, ad set and ad. The basic count, split by call ads and website calls.
- Qualified call rate. The share of calls that were real leads. Two campaigns with the same call volume can differ widely here.
- Cost per qualified call. Spend from Ads Manager divided by qualified calls. This is the number to compare with Google Ads and your other channels.
- First-time callers. Repeat callers and existing customers inflate call counts without adding leads.
- Call length and time of day. Missed and very short calls often point to ads running outside business hours. Meta lets you schedule call ads, which is the fix.
- Calls by placement and creative. If one video brings long conversations and another brings hang-ups, the call data shows it before the sales figures do.
Start tracking your Facebook calls
Meta will tell you how many people tapped the call button. Call tracking tells you who they were, which ad brought them and whether they were worth the spend, and it passes the good ones back to Meta. To try it on your own campaigns, start a 14-day free trial of Nimbata and connect Meta under Integrations.
Frequently asked questions about Facebook call tracking
What is Facebook call tracking?
Facebook call tracking connects each phone call to the Meta ad, ad set and campaign that produced it. Calls made from a call ad are tracked with a tracking number placed in the ad. Calls made after a visit to your website are tracked with dynamic number insertion, which shows each visitor a tracking number and saves the click ID (fbclid) from the ad click.
Can Meta track phone calls on its own?
Partly. For call ads, Ads Manager reports estimated taps on the call button, calls placed, and connected calls of at least 20 and 60 seconds. It does not report who called, what was said or whether the call became a customer, and it does not see calls made from the phone number on your website unless you send them to Meta.
Does Facebook call tracking work for Instagram ads?
Yes. Facebook and Instagram ads are run from the same Meta ad account, and Meta adds the same click ID to the landing page address on both. A tracking number in a call ad, or dynamic number insertion on your website, works the same way for either placement.
How do I send phone calls to Meta as conversions?
Use a call tracking tool that connects to Meta’s Conversions API. With Nimbata, you sign in with Facebook, pick a pixel, name the event, and add Meta as a step in a workflow with the conditions a call must meet. Each matching call is sent to your pixel as a phone call event.
Does Nimbata send the value of a call to Meta?
No. Nimbata sends the event name, the time of the call, the click identifier, the landing page, the caller’s hashed phone number and the visitor’s IP address and user agent. Value and currency are not sent. To tell outcomes apart, send each one as its own event, such as a booked call and a qualified call.





