Catch the bot before the invoice does.

Alion screens every lead on four signals, blocks VPNs, proxies and disposable emails at intake, and stops duplicates and redeliveries across every partner.

017 features

Capture & Lead Quality

Every lead is checked, scored and recognised before any rule sees it.

Four-Signal Fraud Enrichment

Every lead is scored on IP, email, phone and device before any rule sees it.

What it does: Sending junk to a network costs you the lead fee and the relationship. Every lead is scored on IP, email, phone and device fingerprint through IPQS, and your rules can use those fraud scores as conditions. If the fraud provider goes down, leads keep flowing and get scored afterwards instead of stalling.
Why it exists: Without it, you only find out about bad traffic when the network rejects it or claws back the payout, long after you paid for the click.
Example: A lead from a datacenter IP with a disposable email scores 92, so your rule for UK traffic to Northgate Media skips it.

Traffic Protection Filters

22 checks you switch on or off one by one, run before delivery.

What it does: Networks reject leads for reasons they rarely explain, so your rejection rate stays a mystery. Alion runs 22 checks you configure one by one: IP reputation, email quality, phone quality, device and behaviour signals, and geo consistency. Together they catch most of the problems before a lead is delivered.
Why it exists: Because networks rarely say why a lead was rejected, filtering before delivery is the only reliable way to keep your acceptance rate under control.
Example: Turn on VPN blocking and phone validation, leave email quality off. A Meta lead with an invalid phone number is stopped before it reaches Kestrel Ads.

Duplicate Detection with Network Rules

Spots repeat leads and follows each network's rule on sending the same person twice.

What it does: Selling the same lead twice to the same network is the fastest way to lose an account. Alion matches leads on email, phone or IP and flags the duplicates. Each network has its own double delivery setting, Allow, Not the same destination or Not this network, and by default it never expires.
Why it exists: Without it, a person who fills in two forms a week apart gets sold twice, and the network deducts it or stops trusting your traffic.
Example: Velora Partners is set to Not this network. The same phone number arrives again three days later, so Alion skips Velora Partners and tries the next option in your rules.

Duplicate Chain Visualisation

See where a duplicate came from and everywhere it went.

What it does: When a network disputes a duplicate, you need the full picture in seconds, not a database query. Alion shows a lead's whole duplicate history, back to the original and out to every later copy. You see which field matched and where each copy was delivered.
Why it exists: Because disputes are won with evidence, and without the chain you are left guessing which copy came first.
Example: Brightline Leads disputes a DE lead. The chain shows the original from March, the two copies that followed, and that the email address matched.

Circuit Breaker on Enrichment

If the fraud checker goes down, your leads keep moving.

What it does: An outage at a third party should not stop your lead intake. After five failures in a row from the fraud provider, Alion pauses the calls for a short time. This protects live traffic from waves of retries while the provider recovers.
Why it exists: Without it, every lead would wait on a provider that is not answering, and live traffic would pile up behind the retries.
Example: IPQS is down for ten minutes during a Taboola campaign. Leads keep delivering, and their scores fill in afterwards.

Tracker and Traffic Source Recognition

Click IDs from your tracker and ad platform carry all the way through.

What it does: Attribution has to survive the whole journey from click to FTD. Click IDs from Binom, Keitaro, Voluum, RedTrack and ad platforms like Taboola, Google, Meta and MGID are recognised and carried through to your postbacks automatically. Your rules can also use the tracker and source as conditions.
Why it exists: Without the click ID, a postback cannot tell your tracker or ad platform which click became an FTD, so your campaigns optimise blind.
Example: A Meta click comes in through Keitaro. When Halcyon Traffic reports the FTD two days later, the postback carries the original Keitaro click ID.

Leads with an Offer ID

A lead that asks for a specific offer is only ever sent to that offer.

What it does: Some traffic is bought for one specific deal, and sending it anywhere else breaks that deal. Pass OfferId on the request or AlionOfferId on the landing page URL (the request wins), and Alion treats it as a normal rule condition: the other conditions must still match, and the lead only goes to leaves with that offer, never a substitute. If it cannot be delivered (cap full, no matching rule, CRM rejected), it goes to the Rejected leads table with one grouped notification, unless you set TryOtherNetworks, which routes it as if it had no offer ID.
Why it exists: Without it, a lead meant for one deal could be swapped into another offer and billed at a price, or by a network, that never agreed to it.
Example: Leads for Offer A at Northgate Media arrive with AlionOfferId on the landing page. On Sunday its payable cap is full, so 14 leads wait in Rejected leads and you get one notification, not 14.

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