One Flow per Network
Set up postbacks, alerts and webhooks once per network, and they run on every delivery.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Conditional Flow Steps
Any step in a flow can run only for the leads you choose.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Deliver to Any API or Webhook
If a network takes leads over HTTP, you can connect it today.
- What it does
- 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.
- Why it exists
- Because new networks appear every week, and a fixed integration list always lags behind. A template you control means you never wait on anyone.
- Example
- 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.
Five Destination Types
CRM, postback, Telegram, email and webhook in one system.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Business Success Detection
A lead counts as delivered only when the CRM returns a lead ID.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Per Destination Timeouts
Each CRM gets its own wait time, and a slow one never blocks the lead.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Late and Silent Delivery Detection
Leads a CRM accepted after the timeout are caught, recorded and flagged.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Double Delivery Control
Choose per network whether the same person may be sent there again.
- What it does
- 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.
- Why it exists
- 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.
- Example
- 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.
Response Field Extraction
Pull the network's own lead ID straight out of the CRM's reply.
- What it does
- 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.
- Why it exists
- Without the network's lead ID, status sync has nothing to match on, and FTDs cannot be tied back to your leads.
- Example
- 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.
Postback Record per Lead
See every postback a lead fired, its result and the revenue value sent.
- What it does
- 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.
- Why it exists
- Without it, a failed or wrong postback silently skews your ad platform's optimisation, and you cannot prove what was sent.
- Example
- 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.
Full Delivery Audit Trail
Proof of exactly what you sent and exactly what came back.
- What it does
- "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.
- Why it exists
- Without a record of each attempt, every dispute with a network becomes your word against theirs, and you usually lose the money.
- Example
- 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.
