Route it automatically. Recycle what didn't convert.

How Alion routes every lead automatically by weighted splits and cap-aware fallback, then recycles unconverted leads by rule instead of losing them.

039 features

Routing Rules

One ordered list of rules decides where every lead goes and which offer bills it.

Rules That Pick the Offer

One rule decides both where a lead goes and which offer pays for it.

What it does: When routing and billing live in separate places, a lead can reach one CRM and be billed against a different deal. In Alion, every rule ends in a leaf, and an Offer leaf names exactly one offer, so the route and the bill are the same decision. A leaf can also be No Offer (sent untracked on purpose) or an Internal flow (no revenue).
Why it exists: Without it, you need a second matching step to guess which deal a delivery belongs to, and guesses go wrong. One decision means where a lead went always matches what you invoice.
Example: A UK lead from Meta matches the rule "UK Meta", whose leaf is Northgate Media's Offer A at 30 per lead. Alion delivers it to Offer A's CRM and records 30 against Offer A.

Conditions on Any Lead Field

Match leads on country, source, time, fraud score, device or any click parameter.

What it does: Real deals are rarely just "UK traffic": a network may want only mobile leads, during office hours, from one funnel. Alion rules can check country, language, source, landing page, funnel, tracker, requested offer, email domain, local hour, day of week, fraud scores, VPN, IP country, device type and any click parameter. Operators include In, NotIn, Contains, Between, GreaterThan and Exists.
Why it exists: Because a rule that can only see the country will send leads the network does not accept or pay for.
Example: A rule for Kestrel Ads matches DE leads from Taboola, local hour Between 9 and 18, device type mobile, with a fraud score under 40.

Folders with Priority, Split and Mirror

Group routes in folders and choose how leads are shared between them.

What it does: Sending everything to one buyer loses leads when that buyer says no, and splitting by hand does not scale. In Alion, routes sit in folders and each folder has a strategy: Priority tries children in order, Split shares leads by fixed weights, Mirror copies the lead to every child as separate deliveries. Backups are tried only after every sibling fails, and a lead tries the siblings inside its matched rule before it moves to the next matching rule.
Why it exists: Without it, one rejection means one lost lead. Ordered tries and backups give every lead several chances before it is given up.
Example: In the "FR Google" folder, Split sends 70 percent to Velora Partners and 30 percent to Halcyon Traffic. If both reject a lead, the backup, Brightline Leads, gets it.

Smart Routing by EPC

Volume moves on its own toward the routes that earn the most.

What it does: Rebalancing weights by hand every time a buyer's results change is a chore that rarely gets done. A Smart folder sets its weights from each route's EPC (earnings per click), so more volume goes to what actually pays. Each network has a setting "revenue usually arrives after N days", so a slow paying network is not judged before its FTDs come in.
Why it exists: Without the delay setting, a network that confirms FTDs after a week would look worthless on day two and lose its traffic.
Example: Velora Partners earns you 12 per click and Kestrel Ads earns 7, so the Smart folder gives Velora more. Kestrel's revenue usually arrives after 5 days, so its newest leads are not counted against it yet.

Best Payout Routing

Each lead goes first to the offer expected to pay the most for it.

What it does: When one network pays more per lead and another pays more per FTD, it is hard to see which deal is worth more. A BestPayout folder compares its leaves using each leaf's own offer: lead price plus FTD price times a baseline conversion rate (CR). The leaf with the highest expected payout is tried first.
Why it exists: Because the highest lead price is not always the best deal once FTD prices are counted.
Example: Offer A pays 20 per lead plus 800 per FTD, Offer B pays 35 per lead plus 300 per FTD. With a 5 percent baseline CR, Offer A is worth 60 and Offer B 50, so Offer A is tried first.

Rules That Respect Offer Terms

Alion blocks any route that could send an offer leads outside its terms.

What it does: If an offer only accepts DE leads from Google, a route that also lets FR or Meta leads through will produce leads the network will not pay for. In Alion, a rule must guarantee the offer's terms: it may be stricter, never looser. The rule builder blocks a route that breaks this.
Why it exists: Without it, one small rule edit can quietly send unpaid leads to a network for days.
Example: Brightline Leads' Offer A covers CA leads from Google only. A rule matching "CA, any source" cannot point to Offer A until you add the condition source In Google.

Draft, Publish and Rollback

Edit rules in a draft, publish when ready, and roll back if needed.

What it does: Editing live routing while leads flow in means every half finished change hits real traffic. In Alion, you change rules in a draft, publish it when it is ready, and roll back to an earlier version if something goes wrong. Live traffic always follows the published version.
Why it exists: Because a routing mistake costs money every minute it is live, you need a safe place to prepare changes and a fast way back.
Example: On Monday you publish a new FR rule for Halcyon Traffic, see rejections climb, and roll back to Friday's version.

Internal Flows for Notifications and Mirrors

Send leads to your own team or systems, with no network and no revenue.

What it does: Your team and your own tools need to see leads too, but those copies are not sales and should not show up as revenue. An Internal flow has no network and no offer. Use it as a leaf for internal notifications, or inside a Mirror folder to copy a lead to your systems next to the real delivery. It never creates revenue.
Why it exists: Without it, internal copies would look like deliveries to a network and distort your revenue reports.
Example: A Mirror folder sends every UK lead to Northgate Media's Offer A and to an Internal flow that posts it in your team's Telegram chat.

No Offer Leaves

Send leads to a network before the deal is set, and assign it later.

What it does: Sometimes you start sending to a network before the price is agreed, or you want to test a new CRM. A No Offer leaf lets you choose the network and the CRM yourself and send untracked on purpose. Those deliveries wait in the untracked queue until you assign the right offer.
Why it exists: Because waiting for paperwork should not stop traffic, and guessing a price now would put wrong numbers in your revenue.
Example: Kestrel Ads agrees to test UK leads before the contract is signed. You send them through a No Offer leaf for a week, then assign Offer A at 25 per lead to those deliveries.

088 features

Lead Recycling

A lead nobody converted is not a dead lead. Send it out again to a new offer, never to a place it already went.

Rule Based Recycling Segments

Pick which unconverted leads go back out, and which network gets them.

What it does: A No Answer lead is not a dead lead, but most teams leave that money on the table because moving leads by hand is not worth the effort. In Alion you build segments by country, traffic source, campaign, original destination and current status, and send those unconverted leads to new networks.
Why it exists: Without segments, recycling means exporting spreadsheets and guessing which leads are safe to send again.
Example: You select all UK leads from Meta that Northgate Media marked No Answer in the last 14 days and send them to Halcyon Traffic.

Deterministic Distribution

The split you set is the split you get.

What it does: A random split drifts over time instead of holding to what you configured. Alion splits recycled leads across the target networks in exact proportions, not by random assignment.
Why it exists: Because a promised volume is a promise. If one network gets fewer leads than agreed, that relationship suffers.
Example: You split 1,000 recycled DE leads 60/40 between Velora Partners and Kestrel Ads. Velora gets exactly 600 and Kestrel exactly 400.

Redelivery Deduplication

A lead is never sent again to a CRM that already had it.

What it does: Sending a lead to a network that already rejected it hurts the relationship and never gets paid. Alion never resends a recycled lead to a destination it already reached, and the network's double delivery setting still applies on top.
Why it exists: Without it, recycling turns into spam for your own networks and damages the deals you depend on.
Example: A FR lead already went to Brightline Leads and was rejected. When you recycle the FR segment, that lead skips Brightline and only goes to Halcyon Traffic.

FTD Exclusion

A lead that already deposited can never be resold.

What it does: Reselling a lead that already made a first deposit (FTD) is the worst mistake in this business. Alion excludes converted leads from recycling with no exceptions, so it simply cannot happen.
Why it exists: Because one resold depositor can cost you a whole network relationship and a clawback on the original sale.
Example: Your CA No Answer segment holds 400 leads, but 6 of them deposited with Kestrel Ads yesterday. Those 6 are left out automatically.

Geo Eligibility Checks

Recycled leads follow the same country rules as fresh traffic.

What it does: Recycled leads are still leads, and they must follow the same commercial rules as fresh traffic. Alion checks eligibility before a lead is assigned and again right before it is sent.
Why it exists: Because a network only pays for the countries in its deal. A lead from the wrong country is a lead you will never be paid for.
Example: Velora Partners only takes DE and CA. A mixed recycling batch sends them only the DE and CA leads, and the UK leads stay out.

Scheduled Auto Shuffle

Recycling runs on a schedule, so it actually happens.

What it does: Recycling only earns money when it happens regularly, and manual processes never do. In Alion you set a shuffle once and it runs on a schedule, with all the same checks every time.
Why it exists: Without a schedule, recycling waits for someone to remember it, and leads go cold in the meantime.
Example: Every Monday at 09:00, all DE leads still in No Answer after 7 days are shuffled to Halcyon Traffic.

Offer Picked at Shuffle Time

Choose which offer bills each recycled lead, or send it untracked and assign revenue later.

What it does: Recycled leads are often sold under a different deal than fresh ones, so the price must be clear before they go out. When you run a shuffle in Alion, you pick a specific offer of the receiving network, or No Offer to send untracked and assign the revenue later. The network's double delivery setting applies, just like for fresh leads.
Why it exists: Without an offer at shuffle time, recycled revenue is either guessed or forgotten, and it never matches the network's invoice.
Example: You shuffle 200 old UK leads to Kestrel Ads and pick their recycled CPL offer at 8 per lead, so every delivery is billed at 8 from the first second.

Rejected Leads Table and Resend

See every lead Alion could not deliver, with the reason, and send it again.

What it does: Leads that fail quietly are leads you paid for and never sold. Alion collects them in a Rejected leads table: leads with an offer ID that could not be delivered, and leads stopped because their offer was full on a route set to Reject instead of Reroute. Each one shows the reason, and you can resend it through a shuffle.
Why it exists: Because a lead pinned to one offer is never swapped for another. If that offer is full or the CRM refuses it, the lead needs a place where you can see it and act.
Example: Forty CA leads pinned to Offer A with Velora Partners land in the table with the reason payable cap full. Next morning, when the cap resets, you resend them through a shuffle.

Features

More of what Alion does

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 Status Tracking: One Taxonomy, Every Partner27 canonical statuses mapped from every partner's own vocabulary, with an append-only history and automation triggered the moment status changes.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