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

Your rules sit between your site and your ads.

Ad platforms find more of whatever you count as a conversion. Torii saves every lead and order on your site along with where it came from, then sends the ones that pass your rules to Meta and GA4, with more platforms on the way.

Each lead's record names the deciding rule and keeps the platform's reply, for when someone asks why it counted or whether it arrived.

Step by step

Every lead and order takes the same route, from the ad click to your ad platform.

Each website needs the tag, one line of code where a lead or sale happens, a Meta connection and your rules. After that, every lead and order follows this route on its own.

How a lead or order travels from the ad click to Meta Four sources feed Torii: the Torii pixel on your website, Shopify and tracked calls, plus your CRM, available on request. Everything is saved before any rule runs, with the ad click and campaign that brought it in. It stays in your reports whether it counted or not, so changing a rule loses nothing. Your gates then decide: pass, hold for review or reject. Held conversions wait for a person to approve or reject them. Passed conversions go to Meta's Conversions API and to Google Analytics 4, and Google Ads brings in spend only. Reporting shows where leads came from, why any didn't count, and whether Meta received each one. 01 · WHERE IT STARTS 02 · SAVED FIRST 03 · YOUR RULES 04 · WHERE IT GOES Torii pixel ad clicks, leads and orders Tracked calls UK numbers, AI-rated Shopify checkout and every order Your CRM qualified leads, booked jobs ON REQUEST Everything is saved first before any rule runs Where from the ad click and campaign that brought it in Kept counted or not, it stays in your reports Safe to edit change a rule and nothing already recorded is lost Gates your rules decide pass → sent on hold for review reject → not sent Review queue a person approves or rejects Meta Conversions API automatically, every few minutes Google Analytics 4 the same conversions, in GA4 Google Ads spend only, for cost per lead what came in why it counted what Meta got 05 · REPORTING The proof behind each number Where leads came from which ads and campaigns click a count to see the leads Why a lead didn't count the rule that stopped it and what it checked Did Meta get it? Meta's reply for each one resend a failed one in a click
  1. 01Where it starts

    • Torii pixel Ad clicks, leads and orders from your website
    • Tracked calls UK numbers, every call rated by AI
    • Shopify Checkout and every order, with its real value
    • Your CRM Qualified leads, booked jobs and sales On request
  2. 02Saved first

    Everything is saved before any rule runs
    Where from
    The ad click and campaign that brought it in.
    Kept
    Counted or not, it stays in your reports.
    Safe to edit
    Change a rule and nothing already recorded is lost.
  3. 03Your rules

    Gates: your rules decide what counts
    • passSent on to Meta
    • hold for reviewWaits for a person to decide
    • rejectStays in your reports and isn't sent
    Review queue A person approves or rejects each held lead.
  4. 04Where it goes

    • Meta Conversions API Sent automatically, every few minutes
    • Google Analytics 4 The same conversions, in GA4
    • Google Ads Spend only, for cost per lead
  5. 05Reporting

    The proof behind each number
    Source
    Which ads and campaigns your leads came from. Click a count to see the leads.
    Decision
    Why a lead didn't count: the rule that stopped it and what it checked.
    Delivery
    Whether Meta got each one, with Meta's reply and a one-click resend.

One tag on your site remembers which ad each visitor came from and records your leads and orders with their value.

The Torii pixel

You decide what a real lead or a good order looks like, such as an order above your average order value, and agencies can set a different definition for each client.

How gates work

Passed leads and orders go to Meta through its Conversions API, with the details Meta uses to match them.

Where conversions go

Reports are titled as the questions you'd ask, and any lead count opens the leads behind it.

Explore
Numbers you can defend

Open any lead or order and see why it counted.

Each record shows the ad behind it, the rule that decided and what that rule checked.

  1. Rejected leads stay in your reports.

    The leads and orders your rules turned away sit next to the ones that counted, so you can see what was filtered out and check your rules are doing what you meant.

  2. Change your rules as often as you like.

    Everything is saved before any rule runs, so tightening or loosening a rule loses nothing already recorded, and earlier decisions keep the rule that made them.

  3. Nothing goes to Meta unless a rule says so.

    If none of your rules covers something from your website, Torii keeps it and sends nothing. Anything that passes is sent to Meta once, and its record shows when Meta received it.

Where conversions go

Meta and GA4 get the conversions you count.

They go server-side, through Meta's Conversions API and to GA4.

How leads and orders reach Meta.

Once a lead or order passes your rules, Torii sends it to Meta automatically, every few minutes, and records whether it arrived.

What Meta receives
Alongside your setup
Conversions arrive in Meta as their own events, under names you choose, next to whatever Meta's pixel or Shopify's Facebook & Instagram app already sends. Nothing you have now is switched off, so you can move campaigns over one at a time.
What Meta matches on
Each conversion carries Meta's own browser ID, its click ID when the visitor came from a Meta ad, and the visitor's IP address and browser. Email and phone can go too, scrambled (hashed) in the visitor's browser so the raw details never leave the page. That part is rolling out.
Keep Meta's pixel
Meta's browser and click IDs come from Meta's own pixel, so keep it on your site. A conversion with none of those IDs and no hashed email or phone isn't sent, and the log tells you why.
Cookie consent
When a visitor declines ad cookies through Google Consent Mode, their conversions aren't sent to Meta, and the log records the reason. If your site sends no consent signal, conversions are sent as normal.
One per client
Agencies can give each client its own Meta connection, and it receives only that client's conversions.
Test first
Send to Meta's Test Events view, check everything looks right, then switch to live.
In Ads Manager
A campaign optimising for a Torii conversion is credited only with the ones that passed, so expect fewer conversions than it showed on your old lead or purchase event, at a higher cost for each. The Conversion log shows which leads and orders your rules left out.

Follow a conversion after it leaves Torii.

The Conversion log lists every lead and order with the rule's decision and Meta's reply. Sync health shows each connection's deliveries with every attempt, explains any problem in plain English, retries temporary failures automatically, and has a Retry button for the rest. It also flags quiet problems, such as a tag that has stopped sending, a gate that never passes anything or spend that has stopped coming in.

Integrations

What Torii connects to.

Torii records traffic from any ad platform. Conversions go to Meta and GA4, and Torii brings in spend from Google Ads and Meta, so you can see what each lead cost.

What Torii connects to and what each connection does
ConnectionWhat it does for you
Torii pixel One tag on your website. It remembers which ad and campaign each visitor came from, picks up Meta's and GA4's browser IDs when their tags are on the site, and records your leads and orders with one line of code where they happen.
Meta Conversions API The leads and orders that pass your rules, sent server-side with the details Meta matches on.
Google Analytics 4 Passed leads and orders go to GA4 too, matched to the visitor by GA4's own browser ID. GA4's traffic by source and campaign comes back into Torii to sit beside them.
Google Ads and Meta spend Daily campaign spend from both, so you can see what each lead or order that counted cost on each platform.
UK call tracking UK tracking numbers that ring your existing line. Answered calls are recorded and transcribed, and AI rates each one as a qualified lead, existing customer, spam or wrong number. The calls you count go to Meta, and each call's result can be sent to your own systems.
Your CRM On request Send leads your sales team has qualified, booked jobs and sales through the same rules, so Meta learns from real customers instead of enquiries.
Shopify Checkout tracking from add to cart to purchase, with each order's real value, set up with you in your Shopify admin.
Google Tag Manager Import Torii's template, paste the pixel ID and choose what to record, with no change to the site's code.
Microsoft Clarity Link gate decisions and held leads to the session recording in your own Clarity project, so a reviewer can watch what happened. Recordings stay in Clarity.
More ad platforms Coming soon Google Ads conversion uploads, TikTok, LinkedIn and Microsoft Ads are next, with the same rules and records as Meta.
CRM connections Coming soon Direct connections to HubSpot and Salesforce, so booked jobs and sales reach Torii without custom work.
One-click Shopify app Coming soon Install Torii from Shopify with no code to paste.
Your data

Torii is built by a UK agency, and your data is stored in London.

What Torii keeps, and who handles it, is set out on Trust & data.

Pick the first campaign to train on the conversions you count.

We'll look at one of your live campaigns: what it optimises for now, which leads or orders it should learn from instead, and how to switch it over.