Separate rules for calls
A good phone call looks different from a good form fill, so calls can have a gate of their own that checks how long the caller stayed on and how the AI rated the call.
Record every lead and order, and let only the real ones through.
Ad platforms find more of whatever you count. A gate is a short list of rules that decides which leads, calls and orders count, and only those are sent on.
Every enquiry and order keeps the rule that decided it, so when a client or your sales team asks why one was left out, you can show them.
Counts as a conversion and is sent to Meta.
Waits for someone on your team to approve or reject it. Only approved ones are sent to Meta.
Stays in your reports with the reason it didn't count, and is never sent to Meta.
The first rule a conversion fits decides what happens to it, and the rules below don't get a say.
Choose Pass, Hold for review or Reject, then say when it applies: Event is lead, Value is £50 or more, or Campaign contains Brand.
With ALL match, a lead has to be worth £50 or more and come from a paid campaign. With ANY match, one is enough, so a quote request or a booking would both fit.
A rule rejecting job applications from your careers page belongs above the rule that passes leads. Put it below, and the pass rule lets the applications through first.
If no rule fits, the gate's default decides. It's Reject unless you change it, so nothing reaches Meta that you didn't ask for.
Run a change against the last 7 days to see what it would have counted. Torii also warns you when a rule names an event that hasn't arrived.
A good phone call looks different from a good form fill, so calls can have a gate of their own that checks how long the caller stayed on and how the AI rated the call.
A clinic can count consultation requests while an online shop counts orders over £40. An agency sets up each client's gates in the same account.
Until a gate is set up, nothing goes to Meta, from your website or from calls, though it's all still recorded.
Each switch is one rule. Turn rules off and on, or change the default, and watch which of the twelve would be sent to Meta and which would stay in your reports.
Torii has starter gates like these built in. Pick the one closest to how the business sells, then change the pages, values and ratings to fit.
Job applicants and existing customers often use the same forms as new customers, so the first two rules drop anything sent from your careers and support pages, and the third counts enquiries worth £500 or more.
The value comes from the form. A heating firm might give a new boiler enquiry £2,000 and a repair £150, sent with one line of code when the form is submitted. Booked jobs can also be sent from your CRM and run through a gate of their own (available on request).
Spam, wrong numbers and existing customers are dropped, so Meta stops looking for people who already use you. Calls the AI rates as qualified leads count, and other answered calls over a minute wait for a person.
The gate checks each call when it ends and again once the AI has rated it, so a call can be held at first and passed once the rating is in.
Meta only hears about orders of £25 or more, so Advantage+ learns from customers who fill a basket rather than those who buy a single sample. Set the threshold from your own AOV.
On most stores, each order is sent with one line of code on the order confirmation page. Send first orders under a name of their own and a gate can count only new customers. On Shopify, checkout tracking sends each order and the same value rule applies.
Meta learns from visitors who click through to a partner or booking site, which is the click you're paid for. Switch on outbound clicks in Torii and they're recorded with no extra code.
Any rule can hold a lead or call instead of deciding. It waits in the Review queue until someone approves it, and only then goes to Meta. Meta accepts conversions up to 7 days old, so the queue shows how long each one has left. If you'd rather not wait on a person, a gate can approve or reject held leads automatically after a time you choose.
Every lead, call and order keeps a record of which rule decided it and what that rule checked.
Every page view and outbound click the Torii pixel records, plus the leads and orders your site sends it.
Every call to a tracked UK number, tied to the visit and ad behind it where Torii can tell.
AI reads the transcript of an answered call and rates it.
Pick a field, a comparison and a value, then what happens when a lead fits. Anyone who runs the ad account can read a gate and see what it counts, without a developer.
It can if the gate is too strict. Meta's guidance is around 50 conversions per ad set in a week to leave the learning phase, so a gate has to leave enough volume for Meta to learn from.
Switch the gate on first and watch in Explore how many conversions pass in a week. Passed conversions reach Meta under their own event name, so live campaigns carry on as they are until you point one at them.
For a lead campaign, set the event up as a custom conversion and point a duplicate ad set at it while the original keeps running. Advantage+ sales campaigns run as one campaign, so duplicate the whole campaign and choose the gated event as its conversion event. Move budget across once the new one is out of learning, then tighten the rules from there.
Ads Manager counts what Meta is sent. Optimise for the gated conversion and it reports only the ones that passed, so its cost per result rises and its ROAS falls even in a week when nothing changed in your sales.
Judge the switch on numbers from outside Ads Manager, such as cost per qualified lead, CAC or MER, and on what the sales team says about the leads. If you run ads for a client, tell them before you switch so the change in Ads Manager isn't a surprise.
Yes. Preview a change against the last 7 days of events and see what it would have counted before you save. The preview changes nothing and sends nothing on.
It stays as it was. A saved change applies to new leads, calls and orders straight away, and earlier ones keep the decision and rules they already had. Explore marks the change on its charts, so you can compare what was sent before and after.
To Meta, through its Conversions API. If you run ads for more than one business, connect a Meta pixel for each and it receives only that business's conversions. GA4 can receive them too, and Google Ads is used for spend only. More ad platforms are on the way, using the same rules.
Keep Meta's own pixel on the site. Meta matches each conversion to a person using the browser IDs that pixel sets, and Torii needs those IDs to send a conversion.
The value it was recorded with. A gate decides whether a conversion counts and never changes its value. Calls have no value of their own, so you set one call value for each business and every passed call is sent with it.
Yes, and where two gates both apply, a pass from either one counts. To keep it simple, give each business one gate for the website and one for calls. That's how we set them up with you.
Only on calls. Gates are plain rules you write and can read. AI rates each answered call from its transcript, and your call gate can use that rating like any other condition, or leave it out.
Tell us which leads, calls or orders that business wants more of, and we'll write the rules with you on the call.