Ordered rules
Match on geo, device, OS, browser, ISP or ASN, language, connection, bot flag, referrer, IP or CIDR, weekday, hour and sub IDs.
Routing
Match traffic to the casino offers and landers you choose for each geo and device. Split traffic by weight, then compare registrations, FTDs and reported revenue for each variant.
Match on geo, device, OS, browser, ISP or ASN, language, connection, bot flag, referrer, IP or CIDR, weekday, hour and sub IDs.
Weighted, sticky (a returning visitor sees the same path), pinned, or top to bottom.
One path holds several landers and offers with their own weights. The chosen pair is stored on the click.
Add ?next={lp_click_url} to the lander URL and link the lander's CTA to that next value. Capve marks the LP click and sends the visitor to the click's offer.
Each campaign has ordered rules. Conditions inside a rule are AND-ed, each an in or not in list. The first rule that matches uses its own paths, and everything else falls through to the default pool. Hour and weekday conditions use the rule's own timezone.
A path is a direct URL, an offer, or a lander followed by an offer. Mix them in one campaign to compare a pre-lander against direct linking.
Because each click stores its path, lander and offer, the grouped report compares them directly: clicks, LP CTR, conversions, EPC and ROI per variant.
FAQ
Edge redirects with geo, device, ISP, 10 sub IDs and cost
Learn moreBinom-style postbacks, events, status updates, outgoing postbacks
Learn moreBlocklists, datacenter ASNs and safe pages
Learn moreROI by any dimension, 4-level drilldown, CSV
Learn more14-day free trial with every feature. No card, no server, no sales call.