Platform How it works Torii pixel Gates Call tracking Explore Integrations
Company For agencies Trust & data
Book a demo Sign in
Conversion gates

Choose which conversions your ads learn from.

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.

Pass

Counts as a conversion and is sent to Meta.

Hold for review

Waits for someone on your team to approve or reject it. Only approved ones are sent to Meta.

Reject

Stays in your reports with the reason it didn't count, and is never sent to Meta.

How a gate decides

Rules are checked in order, like a checklist.

The first rule a conversion fits decides what happens to it, and the rules below don't get a say.

  1. Each rule is an action and a condition.

    Choose Pass, Hold for review or Reject, then say when it applies: Event is lead, Value is £50 or more, or Campaign contains Brand.

  2. A rule can need every condition or any one.

    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.

  3. Put blocks above passes.

    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.

  4. Your default covers the rest.

    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.

  5. Preview before you save.

    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.

The first rule that fits decides A lead worth £120 from a Facebook ad is checked against a gate. Rule 1, reject when the page contains /careers, does not fit. Rule 2, pass when the event is a lead worth £50 or more, fits, so the lead passes and is sent to Meta. Rule 3, hold other leads for review, is not needed, and neither is the default. Lead £120 · Facebook ad · quote form 1 Rule 1 → Reject ✕ no match Page contains /careers 2 Rule 2 → Pass ✓ first match Event is lead and Value is £50 or more 3 Rule 3 → Hold for review not needed Event is lead When no rule matches → Reject Anything the rules above miss Decision Pass · sent to Meta

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.

A gate for each business

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.

Nothing is sent until you say so

Until a gate is set up, nothing goes to Meta, from your website or from calls, though it's all still recorded.

Try a gate on twelve sample leads, calls and orders.

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.

Checked12
Passed0
Held0
Rejected0
Sent to Meta 0 of 12
Examples

Four gates to start from.

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.

Lead generation

Applies to Web events only · When no rule matches Reject

  1. Rule 1 → RejectPage contains /careers
  2. Rule 2 → RejectPage contains /support
  3. Rule 3 → PassEvent is lead and Value is £500 or more
  4. When no rule matches → Reject

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).

Phone calls

Applies to Calls only · When no rule matches Reject

  1. Rule 1 → RejectAI rating is spam or wrong number
  2. Rule 2 → RejectAI rating is existing customer
  3. Rule 3 → PassAI rating is qualified lead
  4. Rule 4 → Hold for reviewAnswered, and 60 seconds or more
  5. When no rule matches → Reject

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.

  1. The call endsAnswered, 1m 35s, no rating yetRule 4 fits Held
  2. The AI rates it a qualified leadThe gate checks the call againRule 3 fits Passed

Online shop

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.

Applies to Web events only · When no rule matches Reject

  1. Rule 1 → PassEvent is purchase and Value is £25 or more
  2. When no rule matches → Reject

Affiliate or referral site

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.

Applies to Web events only · When no rule matches Reject

  1. Rule 1 → PassEvent is outbound click
  2. When no rule matches → Reject
Review and records

Check borderline leads by hand, and see why each one counted.

Hold for review

Send uncertain leads to a person.

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.

  • Each held lead shows its value, source, page and the rule that held it
  • Approve & Sync sends it to Meta with the time it originally happened
  • Every review records who decided and when, with an optional note
  • Recently decided shows what the team has already been through
  • If you use Microsoft Clarity, watch the visit behind a held lead before you decide
  • A person's decision stands, even if the gate runs again
Decision records

Look up the rule behind any lead.

Every lead, call and order keeps a record of which rule decided it and what that rule checked.

  • Each condition is shown beside the value the lead had, so you can see why a rule fitted or missed
  • Edit a gate and earlier decisions keep the rules that made them, so last month's numbers stay put
  • In Explore, Why weren't events counted? lists what stopped them, with a link to edit the gate

Rules check the facts you'd use to judge a lead or an order.

Website

Every page view and outbound click the Torii pixel records, plus the leads and orders your site sends it.

  • EventLead, purchase, outbound click or any name your site sends, such as first order
  • ValueWhat the lead or order was worth, such as £25 or more
  • Source, medium and campaignFrom your UTM tags, such as Campaign contains Brand
  • PageWhere it happened, such as Page contains /thanks

Calls

Every call to a tracked UK number, tied to the visit and ad behind it where Torii can tell.

  • Call lengthSuch as 60 seconds or more
  • AnsweredYes or no
  • Repeat callerThe same caller within the last 30 days
  • Business hoursInside or outside your opening hours, in London time

AI call rating

AI reads the transcript of an answered call and rates it.

  • RatingQualified lead, existing customer, spam, wrong number, not relevant or other
  • OutcomeBooked, enquiry, callback requested, no action, complaint or other
  • Intent scoreA score from 0 to 100%, such as 70% or more
  • Service asked aboutWhat the caller wanted, such as a boiler repair

Built from drop-downs in Torii.

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.

Questions

Before you switch a gate on.

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.

Turn one business's idea of a good lead or order into a gate.

Tell us which leads, calls or orders that business wants more of, and we'll write the rules with you on the call.