Skip to content
Use cases

Optimise for qualified leads

Report calls and deals from sales to Meta and Google through the conversion API, so the algorithms look for leads who buy instead of people who fill in forms.

The problem

The campaign optimises for the form. It reliably finds people who fill in forms, but many of them never pick up the phone. As long as Meta and Google only see the opt-in, they learn nothing about quality.

How to do it

  1. Create the sales steps as eventsNext to system events such as "deal won", add your own, for example "sales call" or "qualified".
  2. Send events from salesYour CRM or your team reports each step by webhook, API or CSV import, with the lead's email or phone.
  3. Set up destinationsA Meta destination sends deal created, won and lost as CRM stages. For Google Ads, choose a conversion action of the type "Import from clicks" per event.
  4. Define send rulesPer destination, decide which events go out, under which name and on which condition, for example only after an ad click.
  5. Test and optimiseCheck in test mode, then see in the delivery log what arrives. In the campaign, choose the new event as the optimisation goal.
Destinations
  • Meta dataset
    Conversions API · Lead, deal won, purchase
    active
  • Google Ads
    Import from clicks · enhanced conversions
    active
  • LinkedIn
    Conversions API · own token
    active
  • Microsoft Ads
    UET Conversions API
    Test mode
DeliveryDeal won · €4,800
  1. Ad click · Meta
    Oct 12 · Sales call · Lookalike
  2. Lead · form detected
    Oct 12 · email and phone
  3. Deal won · webhook from the CRM
    Nov 3 · €4,800
  4. Sent to platforms
    Meta ✓Google Ads ✓LinkedIn ✓

Why the form is the wrong goal

Meta, Google and others optimise for what they get back. If they only hear about the form, they look for more form fillers, including those who never buy. If they hear about the call or the deal, they look for more people like your customers.

What TSO brings to it

  • One place for every step: lead, call, deal and payment land on the same person, whichever tool they come from.
  • The right identifiers: click IDs, platform cookies, hashed contact data and lead IDs from lead forms go along, so the platform finds the user.
  • The right format: Meta gets deal stages as CRM events, Google the conversion action you created for them.
  • Delivery with proof: a queue with retries and a delivery log per destination show what arrived and why something wasn't sent.

The result

Meta and Google receive calls and deals as conversions, with the identifiers they need to match them. You can let campaigns optimise for these events instead of the form.

Common mistakes

Works with

  • Meta
  • Google Ads
  • LinkedIn
  • Webhook

Frequently asked questions

Does this work with Meta Instant Forms?

Yes. The form's lead ID goes along with every later conversion of the person, and deal stages go to Meta in CRM format.

What if the deal closes weeks later?

TSO keeps the person's click IDs and identifiers and sends them when the event arrives. How long a platform accepts late conversions is up to the platform.

Which platforms receive the sales steps?

Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Snapchat and ChatGPT Ads, each through its conversion API.

More use cases

Set it up in your project.

Hosted in Germany · Built in Austria