Publishers rarely have just one page competing for traffic.
You might have several articles covering a similar topic, different versions of an offer page, or multiple destination pages you want to test with the same audience. Add traffic from email, push notifications, quizzes, CTAs, and other channels, and managing all those destinations can become surprisingly complicated.
The bigger question is what happens after the click.
Which page generates more ad revenue? How much traffic should each destination receive? And when the numbers start to separate, how quickly can you shift more traffic toward the stronger performer?
For many publishers, answering those questions means juggling links, reports, and spreadsheets.
| Traditional destination testing | A more centralized approach |
|---|---|
| Multiple links to manage | One shared link |
| Manual traffic allocation | Configurable traffic weights |
| Data pulled from different sources | Destination-level revenue data |
| Manual performance comparisons | Revenue Per Visitor (RPV) |
| Link changes across campaigns | Routing changes in one place |
The underlying challenge is straightforward: publishers need a practical way to compare destinations using the revenue those destinations generate.
The concept behind a split test is simple. Send traffic to two destinations and compare the results.
The execution can be much less simple.
A publisher might create separate links for each destination, use them across different campaigns, and then pull performance data from several places. If one destination needs more traffic, the links may need to be updated again.
Over time, this creates more work and makes comparisons harder to manage.
There is also the question of what you’re actually comparing.
Clicks and sessions tell you how much traffic reached a destination. They don’t tell you whether that traffic generated more ad revenue than the traffic sent elsewhere.
For an ad-monetized publisher, that distinction matters.
Revenue Per Visitor (RPV) gives publishers a revenue-based way to compare destination performance.
If two destinations receive traffic during a test, comparing their RPV can help show which destination is generating more ad revenue per visitor.
That makes RPV useful when deciding how to allocate traffic between destinations.
Instead of stopping at questions like “Which page received more visitors?”, publishers can also ask:
“Which destination generated more revenue from those visitors?”
That gives publishers a revenue-based way to compare how destinations perform with the traffic they receive.
SplitFlow is a traffic-splitting tool inside PubGuru that lets publishers send visitors to multiple destinations through one shared link.
A publisher creates a redirect rule, adds two or more destination URLs, and assigns a traffic weight to each one. A 50/50 split might be used to distribute traffic evenly, while a 70/30 split gives one destination a larger share.
The shared link remains the same while SplitFlow manages where visitors go.
This means publishers can manage the routing from one place instead of maintaining separate links for every destination.
Once a test is running, SplitFlow provides a destination-level view of the results.
Publishers can see:
The rule detail view also automatically highlights the Best Branch, giving publishers a quick view of the leading destination.
If the results support changing the traffic allocation, publishers can edit the weights in SplitFlow. Those changes are applied at the edge and can go live within seconds.
That creates a simple workflow:
Set the split → collect results → compare RPV → adjust traffic.
The workflow can fit into several common publisher use cases.
Compare different content destinations using their revenue performance.
Split traffic from an email or push broadcast across candidate pages and compare the results.
Manage routing between destinations from one place when working across multiple websites or campaigns.
Give different destinations defined shares of traffic and adjust those shares as performance data develops.
Because the shared URL can continue to be used while routing is adjusted in SplitFlow, publishers can make routing changes without replacing the link everywhere it has already been used.
SplitFlow’s main distinction is the metric used to evaluate the destinations.
A typical link-rotation tool can help determine where visitors were sent or how many clicks a link received. SplitFlow connects destination routing with ad revenue data in PubGuru, allowing publishers to see RPV alongside visitors, revenue, and traffic share.
That gives publishers a revenue-based way to compare how destinations perform with the traffic they receive.
SplitFlow requires a one-time redirect-domain setup for each domain.
The publisher provisions a redirect subdomain through the DNS wizard in SplitFlow and adds the required CNAME record at their registrar. SplitFlow then validates and activates the domain automatically.
Once the redirect domain is active, a publisher can create a rule, add the destination URLs, assign traffic weights that total 100%, and generate the shared link.
DNS propagation can take from a few minutes to up to 72 hours depending on the registrar. After the domain is active, creating a redirect rule typically takes around 3–5 minutes.
SplitFlow is designed for publishers within the MonetizeMore MCM network, with destination domains active in the network.
Testing destinations doesn’t have to mean constantly switching links and piecing together reports.
With a shared link, configurable traffic allocation, and destination-level Revenue Per Visitor data, publishers have a clearer way to run the test and compare destination performance.
If you’re managing multiple destinations and want to see whether SplitFlow fits your workflow, get in touch with the MonetizeMore team.
SplitFlow is a traffic-splitting tool inside PubGuru. It lets publishers send visitors to multiple destination URLs through one shared link and compare destination performance using metrics including revenue and Revenue Per Visitor.
Revenue Per Visitor (RPV) is the revenue-based metric SplitFlow uses to compare destination performance. SplitFlow surfaces RPV alongside visitors, revenue, and traffic share for each destination.
Yes. Publishers can edit the traffic weights assigned to each destination. Changes are applied at the edge and can go live within seconds.
SplitFlow can be used with publisher workflows such as website CTAs, buttons, quiz pages, push notifications, SMS, and email broadcasts.
SplitFlow currently attributes GAM/AdX ad revenue. It does not track affiliate payouts, CPA/CPC performance, or app monetization. Destination domains also need to be active within the MonetizeMore MCM network.
Product Marketing @ MonetizeMore
10X your ad revenue with our award-winning solutions.
