Conversion sync

Send ad platforms the calls that made you money.

Choose which outcomes count, give each one a value, and Saylia sends them to Google Ads, Microsoft Advertising and Meta — matched to the click that started the call.

Conversion rules

Example
  • Booked· AC repair

    Send as “Booked call” → Google · Microsoft · Meta (Schedule)

    $389

  • Qualified

    Send as “Qualified call” → Google · Microsoft · Meta (QualifiedLead)

    —

  • Every call

    Send as “Call” → Meta (Lead) · Microsoft, with an MSCLKID

    —

  • Not a lead

    Never sent as qualified or booked

    —

  • Send each conversion once, even when an upload is repeated

What counts

Bidding learns from whatever you count. Count customers.

Smart Bidding finds more of what you report as a conversion. Report every 60-second call and it finds more long calls. Report booked jobs with their value and it finds more of those.

  • Primary

    Booked calls

    The outcome you want more of. Sent with a value — the job’s actual value when your field-service system reports it.

  • Secondary

    Qualified calls

    Real prospects who didn’t book yet. Extra signal for bidding when bookings are few.

  • Never counted

    Not a lead

    Robocalls, wrong numbers, solicitors, job seekers. Logged for you, and never sent as a qualified or booked conversion.

Every platform

Matched the way each platform expects.

Each ad platform has its own identifiers, formats and rules. Saylia speaks each one natively, so the conversion lands on the right click.

  • Google Ads

    Details
    Matches on
    The click ID from your site (gclid, or gbraid and wbraid for iOS traffic), with hashed caller details for enhanced conversions. Calls from call ads match on caller ID and call time instead.
    Sends
    Your conversion action, the call’s time, value, currency and an order ID.
  • Microsoft Advertising

    Details
    Matches on
    The MSCLKID captured when the visitor landed on your site. Calls without one aren’t sent.
    Sends
    Your offline conversion goal, the call’s time, value and currency.
  • Matches on
    The click ID built from fbclid, plus the hashed caller phone, sent through the Conversions API as a phone call.
    Sends
    Lead for calls, QualifiedLead for qualified calls, Schedule for booked calls, with the value.
  • Your CRM

    Details
    Matches on
    Saylia’s own call ID, on every event.
    Sends
    Signed webhooks as calls start, complete or are missed, and when the recording is ready.

The details

Every detail, handled.

Offline conversions fail quietly when a detail is off: a missing click ID, a malformed time, a number that wasn’t hashed the way the platform expects. These are the details Saylia takes care of.

  • Click IDs captured on every landing page: gclid, gbraid, wbraid, msclkid and fbclid
  • Hashed caller details alongside the click ID for Google Ads, so a call can match through enhanced conversions
  • Caller phone numbers normalised to E.164 and hashed with SHA-256 for click, enhanced and Meta uploads
  • Each call sent once, even if an upload is retried
  • Every upload logged with the platform’s response, so a rejected conversion never fails silently
  • Nothing from the conversation — no recording, no transcript — ever sent to an ad platform

Delivery

A conversion that didn't land is a conversion bidding never saw.

Offline uploads fail quietly on most platforms. Saylia keeps a record of every one, and the reason when a platform says no.

  • LoggedEvery upload is recorded with what the platform said back.
  • Kept with its reasonA rejected upload stays in the log with the platform’s reason, not buried in an error file.
  • Sent onceThe same conversion is never uploaded twice, even when a send is repeated.
Upload logExample
  1. 10:49:40

    Google Ads

    Booked call · $389

    Accepted

  2. 11:02:15

    Microsoft Advertising

    Qualified call

    Accepted

  3. 11:20:44

    Google Ads

    Booked call · $129

    Rejected: click too old

  4. 11:31:09

    Meta

    Lead

    Accepted

Privacy

Only what the platform needs.

Ad platforms need an identifier to match, an outcome and a value. That’s all they get.

  • Hashed where the platform allows

    Phone numbers are normalised and hashed with SHA-256 for click, enhanced and Meta uploads. Calls from Google call ads match on caller ID and call time, which Google requires unhashed.

  • Never the conversation

    Recordings, transcripts and summaries stay in Saylia. Ad platforms get the outcome, the value and the identifiers they match on — never the conversation.

  • Not a lead, not counted

    Robocalls, wrong numbers and job seekers are never sent as qualified or booked conversions.

Questions, answered

Should I keep Google’s own call conversions?
Keep them, but as secondary. Make your booked-call action the primary conversion so bidding learns from outcomes and nothing is counted twice. The Google Ads guide walks through it.
Which conversion should be primary?
Usually booked calls. If bookings are rare, adding qualified calls gives bidding more to learn from. Calls that weren’t leads should never count.
Where do conversion values come from?
From your business: a value for each outcome, or the job’s actual value when your systems report it. Values go with their currency to Google Ads, Microsoft Advertising and Meta.
What about calls from organic search or direct visits?
They’re in your reports and can go to your own systems by webhook. They’re sent to an ad platform only where it can match the hashed caller phone.
What if a call has no click ID?
Google Ads can still match it through enhanced conversions, using the caller’s hashed details, and Meta can match on the hashed phone. Microsoft Advertising needs the MSCLKID.
Do you send recordings or transcripts to ad platforms?
No. Ad platforms receive the conversion, its value and time, and the identifiers they match on. The conversation stays with you.

See what your calls are really worth.

Get started, and every call is followed from the ad click to the conversion your ad platform receives.