Every partner speaks a different status. Alion translates all of them.

27 canonical statuses mapped from every partner's own vocabulary, with an append-only history and automation triggered the moment status changes.

068 features

Status Tracking

Four networks speaking four different languages about the same lead, turned into one set of statuses you can actually compare.

27 Status Canonical Taxonomy

Every network's wording becomes one shared set of statuses.

What it does: Four networks means four different status vocabularies and no way to compare them. In Alion every lead outcome resolves to one shared vocabulary: FTD, Callback, No Answer, Unqualified and 23 more, so network quality becomes directly comparable.
Why it exists: Without one vocabulary, "Interested" at one network and "Hot" at another look different in reports, and you cannot tell which network really performs.
Example: Northgate Media sends "Deposited" and Kestrel Ads sends "ftd_ok". Both show as FTD, so your DE report compares their FTD rates side by side: 4.1% against 2.7%.

Per Destination Status Mapping

Networks keep their own labels. You still get one clean view.

What it does: You should not have to ask a network to change its CRM just to work with you. In Alion each destination's own status strings map into the canonical taxonomy, and anything unmapped shows up in a triage panel instead of silently disappearing.
Why it exists: Without mapping, a new status from a network falls through the cracks, and an FTD can sit unnoticed under a label nobody recognised.
Example: Velora Partners starts sending "Reassigned". It appears in the triage panel, you map it to Callback once, and every past and future lead with that status lines up.

Append Only Status History

Nothing is overwritten, so the full story stays provable.

What it does: When a network insists a lead was always Unqualified and you remember it as a Callback last week, someone has to be provably right. Alion records every status change as a permanent row, never overwritten, so the full sequence stays available.
Why it exists: Because a system that only keeps the latest status hides how a lead got there, and that is exactly what disputes and CRG reconciliations are about.
Example: A FR lead at Brightline Leads shows New on 3 May, Callback on 5 May and Unqualified on 12 May, each with its time, so the Callback claim is settled in one screen.

Inbound Status Webhooks

Networks tell you the moment something changes.

What it does: Finding out about an FTD the next morning is a day too late. Networks can push status changes to Alion in real time instead of waiting for the next scheduled sync.
Why it exists: Because ad platforms optimise on fresh signals. An FTD reported hours late reaches your tracker and Meta or Google too late to help the campaign.
Example: Halcyon Traffic calls your Alion webhook at 14:32 when a CA lead deposits. By 14:32 the lead shows FTD and the Meta conversion postback has fired.

Status Triggered Automation

Fire a postback the second a lead converts.

What it does: Your ad platform can only optimise on conversions it actually knows about. In Alion you set up steps that run automatically whenever a lead reaches a chosen status, most often a conversion postback the moment it reaches FTD.
Why it exists: Without it, someone has to export FTDs and upload them to each ad platform by hand, and the campaign optimises on stale or missing data.
Example: When any Taboola lead reaches FTD, Alion fires the Taboola conversion postback with the click ID and posts "FTD, UK, Offer A" to your Telegram chat.

Four Status Filter Modes

Ask the question you actually mean, not the closest one available.

What it does: "Show me leads no network converted" and "show me leads someone marked Callback at some point" are different questions, and most tools only answer one of them. In Alion you filter by last recorded status, status at every network, status at any network, or ever had status.
Why it exists: Because recycling and reporting depend on asking the right question. The wrong filter sends converted leads back out or hides leads worth a second try.
Example: To recycle DE leads, you pick "ever had status Callback" and exclude "status at any network FTD". You get 640 leads that showed interest but never deposited anywhere.

Status Source Labels

Every status change shows where it came from.

What it does: When a lead suddenly shows FTD, the first question is who said so. Alion records the source of every status change: sync, webhook, manual, import, flow or shuffle.
Why it exists: Without it, you cannot tell a network's own update from a manual fix or an import, and you cannot trust the number in a dispute.
Example: A UK lead at Velora Partners shows FTD from webhook on 9 June, then Rejected from manual on 11 June by a teammate. You see both, with who and when.

FTD Regression Flags

A lead that moves away from FTD is flagged for your review.

What it does: A network can report an FTD and later change the lead to Rejected, and that quietly changes what you are owed. Alion flags every lead that moves away from FTD as a regression for review. It is a flag only: nothing is reversed automatically, you decide what to do.
Why it exists: Without it, a downgraded FTD hides in thousands of status updates until the invoice comes in short.
Example: Kestrel Ads marks a DE lead FTD on 2 July and Rejected on 20 July. Alion flags it, you open the lead, check the $450 FTD payout and raise it with Kestrel before invoicing.

099 features

Visibility & Reporting

See every decision Alion made for a lead, and test a change before it goes live.

Lead Journey with Reasons

See every step a lead took, in order, and the reason for each decision.

What it does: When a network says a lead never arrived, or a lead ends up on the wrong offer, you need facts, not guesses. Every lead in Alion shows its full path in order: the rule that matched, the offer chosen, a full cap and where the lead rerouted, a CRM timeout, the CRM that accepted it and the postbacks that fired. Each step comes with its reason.
Why it exists: Without it, you answer network disputes from memory and spreadsheets, and routing mistakes stay hidden until the invoice.
Example: Velora Partners says lead 48213 from Meta UK never reached them. Its lead journey shows that rule "UK Meta" matched, Offer A at Velora was capped at 12:04, the lead rerouted to Offer B at Kestrel Ads, and Kestrel's CRM accepted it with a lead ID.

Lead Simulator

Enter any lead and see exactly where it would go, before real traffic does.

What it does: Changing rules while traffic runs is risky, because you usually see a mistake only when real leads go to the wrong place. In the lead simulator you enter any lead data, and Alion shows the exact path against your draft or published rules: the rule, the leaf, the offer, the price, the caps, the CRM and the flow steps. It doubles as a check before you publish.
Why it exists: Without it, the first test of a new rule is a real lead and real money.
Example: Before publishing, you simulate a DE lead from Taboola at 23:00. The simulator shows it matches rule "DE night", lands on Offer C at Brightline Leads at a lead price of 25, and its flow sends a Telegram message and a postback.

Offer Coverage View

A grid of countries and networks showing which offer each lead lands on.

What it does: With many rules and offers, it is hard to tell whether every country is covered and which offer a lead really ends up on. The offer coverage view is a grid of countries and networks: each cell shows the offer a lead lands on and the rule that sends it there. Gaps are highlighted, and before you publish you see what changes between the draft and the live rules.
Why it exists: Because a gap is invisible in a list of rules, and you usually find it only after leads from that country have already arrived.
Example: The grid shows FR covered by Offer A at Northgate Media through rule "EU core", but CA has no offer at Halcyon Traffic. You add a rule, and the diff shows CA now lands on Offer D before you publish.

Why Didn't This Lead Match?

Pick a lead and a rule, and see exactly which condition failed.

What it does: A rule looks right, yet a lead skipped it, and checking a dozen conditions by hand takes time. Pick the lead and the rule, and Alion shows exactly which condition did not match.
Why it exists: Without it, you test conditions one by one, or change a rule that was never the problem.
Example: A UK lead from Google skipped rule "UK mobile". The diagnostic shows that country and source matched, but the device type was desktop, so the rule did not apply.

Add Network Helper

Add all of a network's offers to a rule in one click.

What it does: A network often has several offers, and adding them to a rule one by one is slow and easy to get wrong. The Add network helper adds all of that network's offers to a rule in one click. When you create a new offer, Alion asks whether to add it to the rules that already use that network.
Why it exists: Without it, a new offer can sit unused because nobody remembered to add it to the rules.
Example: Kestrel Ads has three offers for UK, DE and CA. You click Add network on rule "Tier 1 Meta" and all three are added. A week later you create a fourth offer for FR, and Alion asks whether to add it to "Tier 1 Meta" too.

Multi-Level Drill-Down Reporting

Group by up to four things at once, like country plus source plus network.

What it does: "Which country and source combination actually makes money at which network" is a question with several dimensions, and most reporting answers only one at a time. Group by up to four levels across networks, countries, offer versions, traffic sources and statuses.
Why it exists: Without it, you export to spreadsheets and pivot by hand to find which mix is profitable.
Example: You group by country, then source, then network, and see that UK Taboola leads earn 42 per lead at Northgate Media but only 18 at Kestrel Ads.

Customisable Dashboards

Build the view you check every morning and save it.

What it does: The numbers you check every morning are not the ones you check at month end. Build a board of widgets you can drag and resize, and save it as a named template per view.
Why it exists: Because one fixed dashboard either hides what you need today or buries it under what you needed last week.
Example: Your morning template shows today's leads, FTDs and capped offers. Your month end template shows revenue per network and deliveries still untracked.

Billing Drill-Down

From an invoice line to the individual lead in three clicks.

What it does: When a network disputes an invoice, you need to reach the individual lead in three clicks, not thirty. Drill from country, to offer version, to the individual leads.
Why it exists: Without it, settling a dispute means rebuilding the invoice from raw exports.
Example: Halcyon Traffic questions 40 FTDs on their DE invoice. You click DE, then Offer B version 2, and see the 40 leads with their delivery dates and statuses.

Cross-Network Revenue Feed

Compare every network side by side in one list.

What it does: Deciding which network gets your next lead depends on comparing them side by side. One flat feed covers every network, country, offer version and traffic source at once.
Why it exists: Without it, each network's revenue sits in its own report, and comparing them takes manual work.
Example: In one list you see that, for CA traffic from Google, Brightline Leads paid 31 per lead last week and Velora Partners paid 22.

Features

More of what Alion does

Alion Lead Distribution: Routing, Splits & RecyclingHow Alion routes every lead automatically by weighted splits and cap-aware fallback, then recycles unconverted leads by rule instead of losing them.Alion Fraud Detection: Block Bots, Duplicates & ProxiesAlion screens every lead on four signals, blocks VPNs, proxies and disposable emails at intake, and stops duplicates and redeliveries across every partner.Alion Cap Management: Real-Time Limits, No OverdeliveryEnforce daily, weekly and contract caps on every lead in real time, preview cap changes with a dry run, and get a Telegram alert before a cap is breached.Alion Revenue Tracking: Payouts, Terms & Live ReportingTrack CPL, CPA, hybrid and CRG payouts per country with versioned terms, automatic FIFO settlement, and reporting that drills down to a single lead.Alion Delivery & Integration: Any API, Full Audit TrailConnect any CRM, postback, Telegram or email destination, detect real business success from the response, and keep a full delivery audit trail.Alion Security: Row-Level Isolation & PII MaskingEvery tenant's data stays isolated at the row level, PII is masked by default, and granular permissions decide exactly what each teammate can see or do.

See all features