Custom Traffic Source Integration

Not every traffic source comes with an API and a logo. A lot of affiliate operations run meaningful spend through smaller ad networks, push and pop platforms, in-app inventory, email and SMS sends, private placement deals, and things they've built or bought outside the named-platform world. None of those have the kind of integration Meta or Google does, and historically that's meant they either live outside the main reporting view entirely or get tracked in spreadsheets that someone has to maintain by hand.

The Routy Custom Traffic Source integration is the catch-all for everything outside the named platforms. You define the source, configure the parameters you want to track against, and Routy treats it as a first-class channel in your reporting. The traffic gets tracked the same way as any other channel through Routy's tracking links and postbacks, and the data ends up in the same dashboards as your Google Ads, Meta, and the rest of your major channels.

Once configured, a Custom Traffic Source gives you:

• Click and conversion tracking through Routy's tracking links and postbacks, regardless of where the traffic originated
• Spend data you bring in yourself — either entered manually for the period, imported from a CSV, or posted in through Routy's API if your source can output it programmatically
• Sub-source, campaign, and creative-level attribution using whatever parameter taxonomy makes sense for your setup
• Side-by-side reporting with your major channels, so a custom source shows up next to Google and Meta in the same dashboards with the same metric definitions

Plus, because the conversion attribution rules are the same across all your sources, a comparison between a custom email send and a paid search campaign is genuinely a like-for-like comparison rather than two different things measured differently.

You create a Custom Traffic Source by defining its parameters: the source name, the campaign and sub-campaign structure, whatever creative or placement dimensions you want to break the data down by, and the conversion postback configuration if the source supports server-to-server reporting. Routy gives you tracking links for the source, you tag your traffic with those links, and clicks start flowing into your reports.

A few things worth knowing before you set one up:

• The richness of the data depends on how much you tag. If you only tag at the source level, you'll see that source's performance as a single aggregate. If you tag down to campaign and sub-source, you'll see the breakdown that level of tagging supports. Routy doesn't impose a taxonomy; you define one that fits the source.
• Spend data for custom sources doesn't get pulled automatically the way it does for named-platform integrations. You either enter it manually, import via CSV on a schedule, or push it through Routy's API. Many operations build a small script that posts spend daily from whatever the source's reporting endpoint is.
• Conversion attribution works through Routy's standard tracking, which means the conversions are matched to clicks using the same logic as your other channels. The custom source doesn't need to do anything special on its side beyond passing the tracking parameters through.

The reason custom sources tend to be under-tracked is that the work of setting up tracking for each one is real, and the perceived payoff is usually smaller per source than for the major platforms. The result, over time, is that a lot of operations end up with 80% of their reporting covering 60% of their traffic, with the long tail of smaller sources living in spreadsheets that get out of date and decisions getting made on incomplete data.

Setting custom sources up properly through Routy collapses that asymmetry. The smaller sources stop being second-class citizens in the reporting; they get measured on the same terms as everything else, and the comparisons across the full traffic mix become honest. For operations that run a meaningful share of traffic outside the named platforms — affiliate-heavy buys, push and pop networks, off-the-shelf inventory deals — getting custom sources into the same reporting view is usually what makes the full media mix manageable rather than a constant exercise in mental gymnastics.