See what every lead is worth the moment it converts.

Track CPL, CPA, hybrid and CRG payouts per country with versioned terms, automatic FIFO settlement, and reporting that drills down to a single lead.

0710 features

Revenue

Every delivery gets one revenue record, tracked or untracked, with a full history.

Four Payout Models

CPL, CPA, Hybrid and CRG offers, all running at the same time.

What it does: Real network deals run CPL, CPA, Hybrid and CRG at the same time, and tracking that in a spreadsheet is where reconciliation errors start. In Alion each offer carries its own payout model, lead price and FTD price, so every model is supported natively, side by side.
Why it exists: Without native support, a hybrid or CRG deal ends up as a side calculation that nobody can audit later.
Example: With Velora Partners in DE you run a CPL offer at 30 per lead and a Hybrid offer at 10 per lead plus 400 per FTD, and both bill correctly in the same report.

One Revenue Record per Delivery

Each delivery shows what it earned, where the number came from, and every change since.

What it does: When revenue lives in several places, nobody can say for sure what a single lead earned. Alion keeps exactly one revenue record per delivery, split into lead part, FTD part, CRG part and total, with its source (Offer, Manual or Untracked) and status (Untracked, Pending FTD, Earned or Void). Every change is kept with the before and after values, the reason, who made it and when.
Why it exists: Without one record per delivery, the same money gets counted twice or not at all, and disputes with a network turn into guesswork.
Example: A UK lead sent to Kestrel Ads shows 15 lead part, 0 FTD part, status Pending FTD. When the FTD arrives a week later, the record moves to Earned with 415 total and the change is logged.

Pricing Frozen at Delivery

Old leads keep the price they were sent at, even when the FTD comes later.

What it does: A price change today should never rewrite what you were owed for last month's leads. At delivery, Alion records a snapshot of the offer, offer version, CRM, flow, rule, leaf and rule set version. That lead keeps the price of that version for good, including an FTD that arrives weeks later, and the snapshot proves the lead went to the right CRM.
Why it exists: Without a frozen snapshot, every offer update would quietly reprice your history and break every invoice already sent.
Example: Offer A with Northgate Media paid 350 per FTD until 1 March, then 400. A CA lead delivered on 25 February that deposits on 10 March still earns 350.

Untracked Revenue Queue

One list of every delivery that has no offer revenue yet.

What it does: Some leads go out before the deal is final, and those are the leads that get forgotten at invoice time. Alion puts every delivery without offer revenue in one queue: leads sent through a No Offer leaf, to a closed offer, with no active version, or after the terms changed. From there you assign the right offer and the revenue is filled in.
Why it exists: Because untracked deliveries are easy to miss, and every one you miss is money the network never pays you.
Example: You test Brightline Leads in FR through a No Offer leaf for three days. The 120 deliveries wait in the queue until you sign the CPL deal and assign Offer A to all of them.

Revenue Edits with Preview and Undo

Change revenue on many leads at once, see the result first, undo it if needed.

What it does: Fixing revenue after a renegotiation usually means editing leads one by one and hoping the totals add up. In Alion you select deliveries with any filter and choose one action: assign an offer or version, set a manual amount, clear to untracked, or recalculate with new terms. You see every lead before and after, with totals and the impact on caps, CRG and invoices, then apply, and you can undo the whole operation in one step.
Why it exists: Because bulk revenue changes without a preview are how invoices go wrong. When you assign revenue later, Alion asks whether it counts against the payable cap, and always uses the period the lead was delivered in, never today.
Example: Halcyon Traffic agrees to pay 25 instead of 20 for all June DE leads from Taboola. You filter those 300 deliveries, choose recalculate with the new version, check the preview shows plus 1,500, and apply.

Manual Revenue Lock

An amount you set by hand stays exactly as you set it.

What it does: Sometimes a network pays an agreed amount that no formula produces, and an automatic update must not overwrite it. Manual revenue in Alion stays editable but is locked against automatic changes such as an FTD or a chargeback, until you assign an offer again. Those events are still recorded, and the lead is flagged for your review.
Why it exists: Without the lock, the next FTD or chargeback would silently replace an amount you agreed with the network.
Example: You settle a UK lead with Kestrel Ads at 250 by hand. When a chargeback arrives later, the 250 stays, the chargeback is logged, and the lead appears in your review list.

CRG Deals with Three Risk Scenarios

Agree up front who carries the risk when a CRG deal misses its conversion rate.

What it does: CRG (conversion rate guarantee) deals hold the most money and cause the most arguments. In Alion a CRG deal is a defined batch of contracted leads or an unlimited deal you close by hand, and the pool covers the whole life of the deal, not one billing period. While the deal is open you see provisional CRG revenue, and the final amount is calculated once at close, under Seller Protected, Buyer Protected or Seller Capped.
Why it exists: Because booking a fixed CRG amount per lead or per month gives numbers that change at close. Seller Protected always pays at least every actual FTD, and at close you reconcile as contracted or as delivered.
Example: Northgate Media buys 500 DE leads at a 10% CRG for 600 per FTD. The batch ends with 38 FTDs. Under Seller Protected you are never paid less than those 38 actual FTDs, the final amount is set at close, and CRG leads can still be moved to another CRG offer with the whole deal recalculated in the preview.

Quality Deductions

Your expected revenue matches what the network actually pays out.

What it does: Networks deduct for bad leads whether or not your own numbers show it. Alion applies deductions at billing time as an overlay: a flat haircut, actual performance, a capped allowance, or a deduction that only starts below an agreed conversion rate.
Why it exists: Without deductions in the system, your expected revenue is always higher than the payment, and every month starts with a gap to explain.
Example: Velora Partners takes 10% off any month where CR falls below 5%. In April the CR is 4.2%, so the April invoice for Offer A shows the deduction before you send it.

Automatic FIFO Settlement

Payments match themselves to deliveries, oldest first.

What it does: Matching payments to leads by hand is the biggest time cost in lead operations, and it is where money quietly goes missing. Alion allocates each payment against revenue records oldest first, automatically, supports partial settlement, and runs a fresh pass on every delivery, payment or FTD confirmation.
Why it exists: Without automatic settlement, you never know which leads are paid and which are still open, so unpaid revenue hides in plain sight.
Example: Brightline Leads sends 8,000 against 9,500 owed for May. Alion settles the oldest May deliveries first and shows exactly which 1,500 worth of leads are still open.

Paid Invoice Revisions

A late change to a paid period reopens the invoice with only the difference.

What it does: FTDs, chargebacks and renegotiations keep arriving after an invoice is paid, and editing a closed invoice by hand breaks your records. When revenue changes on a paid period, Alion reopens that invoice with the outstanding difference and keeps a revision history. If the amount goes down, a credit is created for the network instead.
Why it exists: Without revisions, you either lose late revenue or quietly rewrite an invoice the network already paid.
Example: Kestrel Ads paid the March invoice of 12,000. Two late FTDs worth 800 arrive in April, so March reopens as revision 2 with 800 outstanding.

027 features

Offers

An offer is one deal with a network, with its terms, prices, caps and one CRM.

Offers as Deals

Each deal with a network lives in one offer, with its own terms and prices.

What it does: Deals with networks change often, and when they live in spreadsheets nobody knows which price applies to which lead. In Alion an offer is one deal: which leads it takes (countries, traffic source, other fields), the payout model (CPL, CPA, Hybrid or CRG), lead and FTD prices, deductions, payable caps, one CRM, an optional end date and labels. You can hold several offers with the same network in the same country, for example a CPA deal and a CRG deal with one broker.
Why it exists: Because the routing rule names the offer, where a lead goes and what bills it can never drift apart.
Example: Velora Partners has two offers for DE: Offer A on CPA at $900 per FTD, and Offer B on CRG with a 10% conversion guarantee.

One CRM per Offer

Each offer sends to exactly one CRM, and one CRM can serve many offers.

What it does: When a network has several CRMs, it is easy to send a lead to the wrong one and lose the sale. Each Alion offer points to exactly one CRM of that network, while one CRM can serve many offers. A CRM used by an open offer cannot be deleted, and every change of an offer's CRM is recorded in the audit log.
Why it exists: Without this, a lead could be billed under one deal but land in a CRM that belongs to another, and you would have no proof of where it should have gone.
Example: Kestrel Ads gives you one CRM for UK and CA. Offer A (UK) and Offer B (CA) both point to it, and Alion blocks deleting that CRM while either offer is open.

Offer Versions

Change a price with Update offer, and the new version starts at once.

What it does: Prices change mid month, and editing a number in place rewrites the history of every lead already sent. In Alion, a price change goes through an explicit Update offer: the current version closes and the new one is active immediately. Leads already delivered keep the price of their version, including FTDs that arrive later.
Why it exists: Without versions, a price change would silently reprice past leads, and your numbers would no longer match what the network agreed to pay.
Example: On 14 March Brightline Leads raises the FTD price on Offer A from $800 to $850. A lead delivered on 10 March that deposits on 2 April is still paid at $800.

Scheduled Offer Updates

Plan a price change now and let it apply at the time you choose.

What it does: Networks often agree a new price that starts on the 1st at midnight, when nobody wants to be at a keyboard. Schedule the Update offer ahead of time: you make all the choices when you schedule it, and Alion applies them at the chosen moment. If the offer is closed before then, the scheduled update is cancelled.
Why it exists: Without it, someone has to change the price by hand at the exact minute, and every lead sent before they do is billed at the wrong price.
Example: Halcyon Traffic agrees $950 per FTD on Offer A from 1 November at 00:00. You schedule it on 28 October, and the new version starts on time.

Offer Lifecycle

Each offer shows its state, and routing reacts to that state on its own.

What it does: A deal does not just switch on and off: it fills up, ends or gets cancelled. An offer can be active, payable cap full (never sent to, the lead reroutes), closed (still routed but untracked, with a recurring reminder), past its end date (closed automatically, and you are notified) or removed. Removing an offer removes its routes after a clear warning, and offers that already earned revenue are archived, not deleted.
Why it exists: Because a forgotten closed deal keeps receiving traffic that earns nothing, Alion keeps it visible and reminds you until you change the routes.
Example: Offer A at Northgate Media has an end date of 30 June. On 1 July it closes by itself, you get a notification, and its leads count as untracked until you change the rule.

Global Offers and Catch All

One offer can cover every country, but it is used only where you choose it.

What it does: Some networks take traffic from anywhere, while most deals are per country. A global offer covers all countries, but Alion never picks it automatically: you choose it in a rule like any other offer. For leftovers, a catch all is simply the last rule with no condition, so you decide where unmatched leads go.
Why it exists: Without an explicit choice, a broad offer could quietly absorb traffic meant for better paying country deals.
Example: Kestrel Ads has a global Offer G at $15 CPL. Your last rule, with no condition, sends everything the UK, DE and CA rules did not take to Offer G.

Split Deals and Labels

Split one deal across two CRMs, and group related offers with labels.

What it does: Sometimes a network wants one deal delivered to two CRMs, for example one per sales desk. Create two identical offers, one per CRM, and route to both. Labels group related offers so you can find them together, and they never affect routing or billing.
Why it exists: Because each offer has exactly one CRM, two identical offers are how one deal reaches two CRMs without breaking that rule.
Example: Velora Partners wants DE leads split between its Berlin and Munich desks. You create Offer A1 and Offer A2 with the same terms and give both the label "Velora DE Q4".

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