Every feature, every problem it kills.

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.

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.

A lead from a datacenter IP with a disposable email scores 92, so your rule for UK traffic to Northgate Media skips it.

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.

Because networks rarely say why a lead was rejected, filtering before delivery is the only reliable way to keep your acceptance rate under control.

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.

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.

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.

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.

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.

Because disputes are won with evidence, and without the chain you are left guessing which copy came first.

Brightline Leads disputes a DE lead. The chain shows the original from March, the two copies that followed, and that the email address matched.

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.

Without it, every lead would wait on a provider that is not answering, and live traffic would pile up behind the retries.

IPQS is down for ten minutes during a Taboola campaign. Leads keep delivering, and their scores fill in afterwards.

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.

Without the click ID, a postback cannot tell your tracker or ad platform which click became an FTD, so your campaigns optimise blind.

A Meta click comes in through Keitaro. When Halcyon Traffic reports the FTD two days later, the postback carries the original Keitaro click ID.

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.

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.

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.

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.

Because the routing rule names the offer, where a lead goes and what bills it can never drift apart.

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.

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.

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.

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.

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.

Without versions, a price change would silently reprice past leads, and your numbers would no longer match what the network agreed to pay.

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.

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.

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.

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.

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.

Because a forgotten closed deal keeps receiving traffic that earns nothing, Alion keeps it visible and reminds you until you change the routes.

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.

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.

Without an explicit choice, a broad offer could quietly absorb traffic meant for better paying country deals.

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.

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.

Because each offer has exactly one CRM, two identical offers are how one deal reaches two CRMs without breaking that rule.

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

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

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.

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.

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.

Because a rule that can only see the country will send leads the network does not accept or pay for.

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.

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.

Without it, one rejection means one lost lead. Ordered tries and backups give every lead several chances before it is given up.

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.

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.

Without the delay setting, a network that confirms FTDs after a week would look worthless on day two and lose its traffic.

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.

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.

Because the highest lead price is not always the best deal once FTD prices are counted.

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.

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.

Without it, one small rule edit can quietly send unpaid leads to a network for days.

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.

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.

Because a routing mistake costs money every minute it is live, you need a safe place to prepare changes and a fast way back.

On Monday you publish a new FR rule for Halcyon Traffic, see rejections climb, and roll back to Friday's version.

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.

Without it, internal copies would look like deliveries to a network and distort your revenue reports.

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.

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.

Because waiting for paperwork should not stop traffic, and guessing a price now would put wrong numbers in your revenue.

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.

A network that pays for 50 leads on weekdays, 20 on Saturday and none on Christmas Day is a normal deal, not an edge case. A payable cap sits on the offer and follows what the network pays for: per day, week or month, with weekday rules and date overrides. It is optional, so an offer without a limit simply has none.

Without it, leads beyond what the network pays for still go out, and you find the unpaid ones at invoice time.

Velora Partners' Offer A pays for 50 leads a day Monday to Friday, 20 on Saturday, 0 on Sunday, and 0 on December 25.

What a network pays for and what you want to send are often different: you may want to test a new route slowly, or spread volume across the day. Sending limits (also called routing caps) sit on rules, folders and leaves, and count per minute, hour, day, week or in total, in the timezone you choose. They shape your traffic without changing the deal.

Because one cap cannot do two jobs: the payable cap protects revenue, the sending limit controls pace.

A new Taboola route to Halcyon Traffic's Offer A gets a sending limit of 10 per hour and 100 in total, counted in Paris time.

Limits set in different places easily contradict each other, and nobody notices until leads go unpaid. Alion checks them together: a sending limit can never exceed a payable cap of the same or a longer period (it is blocked and the maximum is shown), and sending limits to the same offer cannot add up to more than its payable cap. You get a notice when part of a payable cap is left unused, a warning when a payable cap can never fill, and when you change a payable cap, Alion shows which route limits will be adjusted.

Without it, caps on different screens drift apart, and you either send leads nobody pays for or leave paid volume unused.

Kestrel Ads' Offer A pays for 100 leads a day. A daily sending limit of 120 on one rule is blocked with 100 shown as the maximum, and two rules at 60 each are refused because together they pass 100.

Leads sent over a cap are leads nobody pays for. When an offer's payable cap is full, Alion never sends to it, and never sends untracked instead: the lead reroutes to its siblings, then to later matching rules. Per route you can choose Reroute (the default) or Reject, which puts the lead in the Rejected leads table.

Because over cap delivery is unpaid work, and quietly sending it untracked would hide the problem instead of solving it.

Northgate Media's Offer A is full at 200 for the day. Lead 201 goes to Brightline Leads' Offer B, the next sibling in the folder.

Batch cap checks let leads slip through in the gap between checks. Alion checks payable caps and sending limits on every routing attempt, with no queue and no pending state. Each cap resets by its period in its own timezone.

Without it, a burst of traffic between two checks can push dozens of leads past a full cap.

At 23:59 Berlin time, Kestrel Ads' DE offer has one lead left. Two leads arrive in the same second: one is delivered, the other reroutes. At midnight Berlin time the daily cap resets.

When you assign an offer to untracked deliveries afterwards, those leads belong to the day they were sent, not to today. Alion asks whether the assignment should count against the offer's payable cap, and if it should, it always counts in the period the lead was delivered in, never today's.

Without it, assigning last week's leads would fill today's payable cap and block live traffic for no reason.

On Friday you assign Offer A to 40 untracked leads Halcyon Traffic received on Tuesday. You choose to count them, and they go against Tuesday's payable cap, not Friday's.

Renegotiating volume in the middle of a contract is routine. Finding out the financial result afterwards is not something you want. Change a cap on a live CRG deal and every past FTD is re-evaluated against it, with a dry run preview showing exactly what would change before anything is saved.

Because a cap change on a live CRG deal can move money you already counted, and you should see that before you commit.

Velora Partners lowers a CRG deal from 500 to 400 leads. Before you confirm, the dry run shows the CRG total moving from 9,000 to 7,200 and which FTDs cause the change.

A message for every rerouted lead buries the one alert that matters. Alion notifies once per state change, for example "Offer A capped at 12:04, traffic now going to Offer B" and later "available again". Planned overflow arrives as a digest, an unplanned reroute arrives as an alert, and you can mute, snooze, or choose instant, hourly or daily digests.

Without it, your team learns to ignore cap messages and misses the one that needed action.

Brightline Leads' Offer A fills at 14:10 and reopens at midnight. You get two messages, one for each change, instead of 300.

Finding out at 2pm that a cap filled means hours of traffic went to weaker routes. Set remaining capacity thresholds per offer and get a Telegram alert, for example at 80 percent, so you can rebalance in time. Alerts are deduplicated, so the same threshold never pings the team twice.

Because a cap is far easier to manage before it fills than after.

Halcyon Traffic's FR offer reaches 80 of its 100 daily leads at 11:30, and your team's Telegram chat gets a message in time to add a second offer to the rule.

When every offer has its own copy of the same postbacks and alerts, one change means editing ten places and missing one. In Alion each network has one flow: postbacks, Telegram, email, webhooks, filters and continue on CRM failure. It runs around every delivery to that network, and template variables like {{offer_id}} and {{offer_identifier_name}} are always filled from the offer the lead was routed to.

Because the rule already picks the offer and the offer knows its CRM, the flow only has to handle what happens around the delivery. Without one shared flow, settings drift apart between offers of the same network.

Northgate Media has a CPA offer and a CRG offer in DE. Both use Northgate's one flow, so a lead on the CRG offer fires the tracker postback with {{offer_identifier_code}} set to the CRG offer's code.

Running several trackers or ad sources means each needs its own conversion endpoint, and some alerts only matter for one country. Every flow step can have a condition built with the same condition builder as routing rules: country, language, source, funnel, tracker, landing page, offer, email domain, time, fraud scores, device or any click param.

Without conditions you either send every postback to every tracker or build a separate flow for each case. One flow with conditional steps keeps it in one place.

In the Kestrel Ads flow, the Meta postback runs only when source is Meta, the Taboola postback only when source is Taboola, and a Telegram alert only for leads from CA.

Waiting for a platform to add a network to its integration list can cost you weeks of a deal. In Alion, requests are built from a JSON template with variable substitution and header based authentication, so any CRM that accepts leads over HTTP can be connected right away.

Because new networks appear every week, and a fixed integration list always lags behind. A template you control means you never wait on anyone.

Velora Partners sends you API docs on Monday morning. You map name, email, phone and country into a JSON template, add their API key as a header, and the first UK lead goes out before lunch.

A lead needs to reach the network's CRM, your tracker, and often your own team. Alion handles all five destination types in one place: CRM, postback, Telegram, email and generic webhook.

Without it, alerts live in one tool, postbacks in another and CRM sends in a third, and nobody sees the whole picture for a lead.

One FR lead to Brightline Leads goes to their CRM, fires a postback to your tracker, posts to your team's Telegram chat and sends a webhook to your internal sheet.

Many CRMs return HTTP 200 with an error buried inside the JSON. Alion reads the response body, not just the status code, and a lead is delivered only when the CRM answers with a lead ID. After a business rejection Alion never retries the same CRM, it moves on to the next option.

Without it, you record failures as successes and expect revenue for leads that never landed. Retrying a CRM that already said no only wastes time the lead could spend with another network.

Halcyon Traffic's CRM answers HTTP 200 with {"success": false, "error": "duplicate"}. Alion marks the attempt as failed and tries the next leaf, Kestrel Ads, which returns lead ID 88412.

A slow CRM can hold a fresh lead for a minute while it cools down. In Alion every destination has its own timeout, 9 seconds by default and adjustable. Destinations are tried one at a time, and if a CRM does not answer in time the attempt counts as failed and the next network is tried.

Because a lead's value drops by the second. One global timeout is either too short for a slow but good network or too long for the rest.

You give Northgate Media's CRM 15 seconds because it is slow but converts well, and keep Velora Partners at the default 9. When Velora does not answer in 9 seconds, the lead moves straight to the next leaf.

Sometimes a CRM accepts the lead after Alion has stopped waiting, and the lead has already gone to the next network. If the answer arrives late, the delivery becomes semi successful: statuses sync, revenue is recorded and flagged as a possible double sale, it counts against the payable cap and you get an alert. If the CRM never answered but status sync finds the lead there by email or phone, it is treated the same way.

Without it, a lead the network actually holds stays invisible: no revenue, no status, no cap count. Then you only find out when the network's invoice does not match yours.

Brightline Leads answers with a lead ID after 14 seconds, but the lead already went to Halcyon Traffic. Alion records the Brightline delivery at $40, flags it as a possible double sale and alerts you on Telegram.

Sending the same person twice to one network can break a deal, while other networks happily take a second look. Alion has a double delivery setting per network with three levels: Allow, Not the same destination, or Not this network. It checks the same lead or the same person by email or phone, the window is forever by default, and only real send attempts count.

Because each network has its own rule about duplicates. One global setting is either too strict and wastes leads, or too loose and gets you in trouble.

Kestrel Ads is set to Not this network, so a person already sent there in March is skipped in June. Velora Partners is set to Allow, so the same person can go to Velora again through recycling.

The network's own lead ID is what makes later status sync and reconciliation possible. Alion pulls it, along with an auto login URL or a status, straight out of the response with an interactive picker, no manual step required.

Without the network's lead ID, status sync has nothing to match on, and FTDs cannot be tied back to your leads.

Halcyon Traffic replies with {"data": {"lead_id": "HT-5521", "autologin": "https://..."}}. You click lead_id and autologin in the picker once, and every future lead stores both.

When your tracker shows less revenue than Alion, you need to know which postback fired and with what value. Every postback is recorded per lead: which postback, its status, success or failure, and the revenue value sent. Untracked deliveries send revenue 0, and re-firing with a corrected value is a manual action.

Without it, a failed or wrong postback silently skews your ad platform's optimisation, and you cannot prove what was sent.

A UK lead for Offer A shows two postbacks: the Google lead postback succeeded with $25, and the FTD postback failed with HTTP 500. You fix the endpoint and re-fire the FTD postback with $400.

"We never received that lead" is the most common dispute in this business. Alion records every attempt permanently: the exact request, the exact response, and a rebuilt curl command you can replay, so the argument ends with evidence instead of memory.

Without a record of each attempt, every dispute with a network becomes your word against theirs, and you usually lose the money.

Northgate Media says 12 DE leads from last Tuesday never arrived. You open each one, show the request and their own response with lead IDs, and they credit all 12.

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.

Without one vocabulary, "Interested" at one network and "Hot" at another look different in reports, and you cannot tell which network really performs.

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

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.

Without mapping, a new status from a network falls through the cracks, and an FTD can sit unnoticed under a label nobody recognised.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

Without it, a downgraded FTD hides in thousands of status updates until the invoice comes in short.

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.

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.

Without native support, a hybrid or CRG deal ends up as a side calculation that nobody can audit later.

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.

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.

Without one record per delivery, the same money gets counted twice or not at all, and disputes with a network turn into guesswork.

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.

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.

Without a frozen snapshot, every offer update would quietly reprice your history and break every invoice already sent.

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.

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.

Because untracked deliveries are easy to miss, and every one you miss is money the network never pays you.

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.

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.

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.

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.

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.

Without the lock, the next FTD or chargeback would silently replace an amount you agreed with the network.

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

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.

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.

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.

Without deductions in the system, your expected revenue is always higher than the payment, and every month starts with a gap to explain.

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.

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.

Without automatic settlement, you never know which leads are paid and which are still open, so unpaid revenue hides in plain sight.

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.

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.

Without revisions, you either lose late revenue or quietly rewrite an invoice the network already paid.

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.

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.

Without segments, recycling means exporting spreadsheets and guessing which leads are safe to send again.

You select all UK leads from Meta that Northgate Media marked No Answer in the last 14 days and send them to Halcyon Traffic.

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.

Because a promised volume is a promise. If one network gets fewer leads than agreed, that relationship suffers.

You split 1,000 recycled DE leads 60/40 between Velora Partners and Kestrel Ads. Velora gets exactly 600 and Kestrel exactly 400.

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.

Without it, recycling turns into spam for your own networks and damages the deals you depend on.

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.

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.

Because one resold depositor can cost you a whole network relationship and a clawback on the original sale.

Your CA No Answer segment holds 400 leads, but 6 of them deposited with Kestrel Ads yesterday. Those 6 are left out automatically.

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.

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.

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.

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.

Without a schedule, recycling waits for someone to remember it, and leads go cold in the meantime.

Every Monday at 09:00, all DE leads still in No Answer after 7 days are shuffled to Halcyon Traffic.

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.

Without an offer at shuffle time, recycled revenue is either guessed or forgotten, and it never matches the network's invoice.

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.

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.

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.

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.

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.

Without it, you answer network disputes from memory and spreadsheets, and routing mistakes stay hidden until the invoice.

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.

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.

Without it, the first test of a new rule is a real lead and real money.

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.

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.

Because a gap is invisible in a list of rules, and you usually find it only after leads from that country have already arrived.

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.

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.

Without it, you test conditions one by one, or change a rule that was never the problem.

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.

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.

Without it, a new offer can sit unused because nobody remembered to add it to the rules.

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.

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

Without it, you export to spreadsheets and pivot by hand to find which mix is profitable.

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.

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.

Because one fixed dashboard either hides what you need today or buries it under what you needed last week.

Your morning template shows today's leads, FTDs and capped offers. Your month end template shows revenue per network and deliveries still untracked.

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.

Without it, settling a dispute means rebuilding the invoice from raw exports.

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.

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.

Without it, each network's revenue sits in its own report, and comparing them takes manual work.

In one list you see that, for CA traffic from Google, Brightline Leads paid 31 per lead last week and Velora Partners paid 22.

You route commercially sensitive lead data, so isolation has to be structural, not a matter of careful coding. Separation between workspaces is enforced by the database itself on every table, not only in the application.

Without it, one missing filter in one query could show your networks, prices and leads to another customer.

Even if a report screen had a bug in its filter, your Kestrel Ads leads still could not appear in another customer's workspace, because the database filters every row by workspace.

A media buyer needs to see lead flow, but not what each network pays. Alion has 25 independent permissions, all denied by default, so access matches the job, not a role template.

Because fixed roles always give someone more than they need, and prices are the first thing to leak.

You give your media buyer access to leads, rules and lead journeys but not to offer prices, so the lead and FTD prices of Offer A stay hidden.

Team members and contractors need to do their jobs without seeing customer personal data (PII). Phone, email, IP and network contact details are masked separately for each user, and owners always see the real data.

Without it, every person with access to leads can copy a full customer list.

A contractor checking failed deliveries to Velora Partners sees each lead's email and phone masked, while the owner of the workspace sees them in full.

Agencies and consultants work across several operations and do not want to juggle logins. One account can belong to several workspaces, with its own role in each.

Without it, people share logins or create duplicate accounts, and you lose track of who did what.

A consultant is admin in one client's workspace and has read only reporting access in another, all with one login.

A traffic burst or a misconfigured lander should never slow the platform down for anyone else. Rate limits follow each workspace's plan and are counted per workspace, not per IP.

Because limits counted per IP either block real traffic behind shared IPs or let one noisy account slow down everyone.

Another customer's broken lander floods Alion with requests. Their workspace hits its limit, and your leads from Meta keep arriving at normal speed.

Only your landers should be able to submit leads to your workspace. The public intake endpoint is locked to a landing page identifier, with an optional allowlist of server IPs.

Without it, anyone who finds your endpoint can push fake leads into your rules and onto your networks.

A copied form posts to your endpoint without your landing page identifier and is refused. With the IP allowlist on, only your two servers can submit leads at all.

Another platform with another password is how credentials get reused and, sooner or later, leaked. Sign in with the Google account you already trust, or use email with hashing strong enough that a database breach does not hand out working passwords.

Because weak password storage turns any breach into stolen accounts.

Your team lead signs in with the company Google account. A contractor signs in with email, and Alion stores the password only as a strong hash.

You should not have to pay to find out whether a system fits how your leads really move. The Free plan has the whole platform with 100 leads a month and 2 users, and paid plans only add lead volume and seats.

Because features locked behind a paywall hide whether the tool works for you, and asking for a card first scares people off.

You sign up, connect Kestrel Ads and Velora Partners, and route your first 100 leads of the month with every feature on. When volume grows, you move to Team.

A large part of this industry does not or cannot pay by card. Stripe handles cards, with instant prorated upgrades, and Coinbase Commerce handles crypto.

Without it, teams that work in crypto simply cannot subscribe.

You upgrade mid month by card and pay only the prorated difference. A partner team pays its plan in crypto through Coinbase Commerce.

Nobody wants to discover a usage bill after a traffic spike. Reaching a plan limit blocks further use and prompts an upgrade, and nothing is ever billed as overage.

Because with usage billing, one bad day of traffic can cost more than the whole month's plan.

A Taboola spike takes you to your plan limit on the 20th. Alion stops at the limit and asks you to upgrade, and your bill stays exactly the plan price.