Payable Caps with Weekday Rules
Set exactly what the network pays for, per day, week or month.
- What it does
- 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.
- Why it exists
- Without it, leads beyond what the network pays for still go out, and you find the unpaid ones at invoice time.
- Example
- Velora Partners' Offer A pays for 50 leads a day Monday to Friday, 20 on Saturday, 0 on Sunday, and 0 on December 25.
Sending Limits on Rules and Leaves
Control your pace per minute, hour, day, week or in total.
- What it does
- 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.
- Why it exists
- Because one cap cannot do two jobs: the payable cap protects revenue, the sending limit controls pace.
- Example
- 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.
Caps and Limits Checked Together
Alion stops sending limits that conflict with the offer's payable cap.
- What it does
- 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.
- Why it exists
- Without it, caps on different screens drift apart, and you either send leads nobody pays for or leave paid volume unused.
- Example
- 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.
Full Offers Are Never Sent To
When an offer's payable cap is full, the lead goes somewhere else.
- What it does
- 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.
- Why it exists
- Because over cap delivery is unpaid work, and quietly sending it untracked would hide the problem instead of solving it.
- Example
- 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.
Real Time Enforcement
Caps are checked on every lead, so overdelivery cannot happen.
- What it does
- 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.
- Why it exists
- Without it, a burst of traffic between two checks can push dozens of leads past a full cap.
- Example
- 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.
Later Revenue Counted in the Right Period
Revenue assigned later can count against the cap of the day it was delivered.
- What it does
- 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.
- Why it exists
- Without it, assigning last week's leads would fill today's payable cap and block live traffic for no reason.
- Example
- 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.
Cap Recalibration with Dry Run
See the money impact before you change a cap on a live deal.
- What it does
- 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.
- Why it exists
- Because a cap change on a live CRG deal can move money you already counted, and you should see that before you commit.
- Example
- 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.
Cap Notifications Without the Noise
One message when a cap changes state, not one per lead.
- What it does
- 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.
- Why it exists
- Without it, your team learns to ignore cap messages and misses the one that needed action.
- Example
- Brightline Leads' Offer A fills at 14:10 and reopens at midnight. You get two messages, one for each change, instead of 300.
Telegram Cap Alerts
A Telegram message at 80 percent full, before you waste traffic.
- What it does
- 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.
- Why it exists
- Because a cap is far easier to manage before it fills than after.
- Example
- 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.
