Meta
Show Meta which calls turned into customers.
Saylia sends qualified and booked calls to Meta through the Conversions API, marked as phone calls and matched by the caller’s hashed number and the Meta click ID, so your campaigns can optimize for the calls that paid off.
Schedule
- Action source
- phone_call
- Event time
- 2026-09-29 15:49:40 UTC
- Phone (hashed)
- a3f1c07e9b5d24…
- Click ID (fbc)
- fb.1.1790696551000.IwAR2x…
- Value
- 389.00 USD
The caller’s number is hashed with SHA-256 before it’s sent to Meta.
How it works
From the scroll to the phone call.
Most calls a Meta ad causes happen off Meta, where the pixel can’t see them. The Conversions API closes that gap.
- 01
The visit
When someone arrives from a Meta link, the Saylia tag saves the fbclid to the visit, alongside the UTM tags you already use.
- 02
The call
They call the tracking number shown to them. The call keeps the visit — and the caller’s number, which Meta can match on its own.
- 03
The event
When the call qualifies or books, Saylia sends a Conversions API event marked as a phone call, with its value.
Events
Each outcome, its own event.
Calls, qualified calls and bookings each become their own event, so Meta can tell them apart.
| Meta event | Sent when | Type |
|---|---|---|
| Lead | Any call you choose to count as a lead | Standard |
| QualifiedLead | The call qualified | Custom |
| Schedule | An appointment was booked | Standard |
The details
Meta’s rules, followed for you.
- fbclid saved from the landing page and sent in Meta’s fbc format
- Caller numbers normalized to digits with country code and hashed with SHA-256
- Every call event marked with action_source phone_call
- A value and currency on every event
- Duplicate events caught before they’re sent
Questions, answered
Can Meta match a call without a click ID?
Does an fbclid mean the visitor clicked a paid ad?
Why are qualified calls a custom event instead of Lead?
Which event should my campaigns optimize for?
Let Meta learn from your phone, too.
See which of your Meta-driven calls booked, and what the Conversions API would have sent for each.