Worked Examples
Three campaigns, from simplest to advanced, each built node-by-node with an explanation of how a click flows through it.
Example 1 — A simple direct link
The minimum viable campaign: send every visitor straight to one offer.
Add a Domain (or use the default)
Drag a Domain node, pick your tracking domain, and connect it into the Campaign node. (Skip this to use the shared platform domain.)
Add an Offer
Drag an Offer node. Set its URL to https://offer.com/?cid={clickid} so the
click ID is carried to the destination.
Connect & save
Wire Campaign → Offer, then Save. Your /t/<id> link is live.
How a click flows: every visitor matches no special rule, so the engine uses the
default offer and redirects to https://offer.com/?cid=<thatClickId>.
Example 2 — Geo split, A/B test, and an AI rotator
A realistic campaign: French visitors get an A/B test between two landers; everyone else gets an AI-optimized offer rotation.
Geo rule
From Campaign, draw an edge to a Rule node. Add the condition
country in FR.
A/B split
From the Rule, connect a % Split node with two slots at 50% each.
Two landers → one offer
From the split’s two handles, connect Landing A and Landing B (enable Forward query params on each). Point both to the same Offer FR.
Default rotator for everyone else
From Campaign, also draw an edge to a Smart Rotator (goal = EPC). Connect it to three offers (X, Y, Z).
Notify on conversion
Hang a Discord node off Offer FR to ping your channel on every sale.
Save
The graph compiles to a flow and pushes to the edge.
How clicks flow:
| Visitor | Path |
|---|---|
| 🇫🇷 French | The FR rule matches → the % Split sends them 50/50 to Lander A or B → that lander forwards clickid to Offer FR. |
| 🇩🇪 German (or anyone else) | No rule matches → the default Smart Rotator runs Thompson Sampling and routes to whichever of X/Y/Z is earning the most (still probing the others). |
Example 3 — A fraud-shielded, capped funnel
Protect a sensitive offer: drop bots, cap conversions so you never overspend a network’s daily limit, and fail over if a lander dies.
Filter bots first
Campaign → Bot Filter. Route the bot handle to a junk/blank Offer so bots never
touch your real offer; route human onward.
Cap conversions
From the human handle, connect an Offer Cap (100/day). The under handle
carries normal traffic; the over handle routes overflow to a Backup Offer once
the cap is hit.
Lander with failover
From under, connect a Landing with a Monitor failover to a fallback
Landing. Point the lander at your Main Offer.
Save
Done — your offer is shielded from bots, protected from over-delivery, and resilient to a dead lander.
How clicks flow:
- Bots are forked off to a blank page (recorded, but not sent to the real offer).
- Humans hit the cap check: under 100 conversions today → main funnel; at/over → backup offer.
- If the main lander’s monitored site is down, traffic automatically diverts to the fallback lander.
Tips for building good flows
- Put broad fallbacks last. Wire your catch-all routes off the Campaign node as defaults; the engine uses them only when no specific rule matches.
- Always forward the
clickid. Every landing→offer hop must carry it, or attribution breaks. - Test with the real link. Open
/t/<id>from different devices/VPNs and watch Live Logs to confirm routing. - Use a Smart Rotator when you’re unsure which offer wins — let the data decide.