August 2026

8 new features, 6 new integrations, 30 improvements, 23 fixes and 45 connector fixes.

New8

NewAccount integrations
Customer-level data collection.
Integrations that expose per-customer activity (such as Casino Controller) can now collect it day by day. This data powers upcoming per-customer reporting; there is nothing to configure today.
NewAccount integrations
Cellxpert now collects player-level data.
Your Cellxpert accounts can pull a customer report — one row per player — alongside the existing day, tracker, brand and click reports. Where your network grants access to its player activity report, you get true day-by-day activity per player, including deposit, withdrawal and commission counts. Otherwise you get each player's running totals, refreshed whenever their record changes. Ask your network about enabling the activity report if you want the richer, day-by-day version.
NewAccount integrations
Stake can now also collect player-level data.
A new Report shape setting on Stake accounts chooses what the export becomes: the existing day-over-day change report (click), a player-level report of each player's running totals (customer) — the same way Cellxpert and Centrivo work — or both, which is the default. Two other improvements come with it: every column your Stake export contains is now kept (previously anything outside a fixed list, such as first-deposit date or monthly wager, was dropped), and a share link that has expired or been revoked is reported as something for you to fix rather than a generic failure. You can also now use Test connection on a Stake account to check the share link straight away. Expect one empty day on the first run after the upgrade — the day-over-day report needs a fresh copy of the export to compare against.
NewAccounts
Fill in your tracking profiles from their names.
If your profile names already carry the brand, traffic source and country (FB_BTM_DE), you can now write a rule that says so — as when/then dropdowns, not a pattern — and we'll work out what each part means, learning your shorthand (BTM = BetMGM) from the profiles you already mapped by hand. Ask us to suggest a rule and we read your existing names and draft one for you. The first release was preview-only — you saw exactly what would change and how much your reporting coverage would improve (brand: 41% → 88%) — and the next entry adds writing it. See the guide.
NewAccounts
You can now apply what the preview showed — and undo it.
Press Apply and we fill your tracking profiles in, across one account, one program, one platform, or everything. Anything you set by hand is left alone: a rule fills an empty detail and can correct a detail a rule set before, but it never overwrites yours unless you explicitly ask it to — and profiles you mapped before this feature existed count as set by hand. (One exception for now: if a rule filled a detail in and you then correct that detail by hand, a later apply may fill it in from the rule again — correcting the rule is the more durable fix, and the run is undoable either way.) Every apply is kept as a run you can put back: undo restores what it replaced, except on anything you've changed since, which it leaves alone and tells you about. One thing to know: a run can only be undone once, and if you applied several times, undo them newest-first. Profiles sitting at New that end up with a brand, a traffic source and a country all filled in move to Enabled, so "new" stays a list of profiles that still need you. New profiles are still not mapped automatically — that's next. See the guide.
NewAccounts
You can archive tracking profiles you're done with.
Integrations keep discovering profiles, and old ones pile up in a list you have to scroll past every time. Archiving takes one out of the list without deleting anything — its history, reports and any links pointing at it are untouched, stats keep arriving, and you can bring it back whenever you want. It's separate from a profile's status, so archiving doesn't disable or close anything.
NewChannels
Import your links from a connected channel.
If your destination links already live somewhere else — a tracker like Voluum, or a network you have an account with — you can bring them into Routy instead of retyping them. Open the connection, choose the links you want, say which account each belongs to, and Routy creates them. Setting an account on one link offers to apply it to every link in the same group, so a whole network is a couple of clicks rather than fifty. Links you have already imported are marked and never duplicated. Note that importing a link copies the destination into Routy — it does not change anything at your tracker, so your new Routy links show no clicks until you point traffic at them.
Read the full page
NewChannels
Voluum connections can now report by the hour.
A connection can be switched from daily to hourly figures, which is what makes day-parting — seeing which hours actually perform — possible. Daily stays the default. Ask support to switch a connection over; note that hourly and daily figures for the same day cannot be mixed, so the days already collected are re-imported when you switch.
Read the full page

New integrations6

IntegrationAccount integrations
AffiliationSpace.
Connect with your AffiliationSpace portal email and password to collect daily totals, site, advertiser, and postback-level performance. A report-timezone setting keeps postbacks on the correct local calendar day.
IntegrationAccount integrations
Number1Affiliates.
Connect your Number1Affiliates account with your portal username and password to collect brand performance (Daily Financials), tracker performance (Tag Traffic) and sub-id performance, plus your balance and your campaign list. A Tracker report setting chooses whether trackers are broken down by banner (the default), by campaign, or both, and a Balance currency setting says which currency the portal's earnings figure is in — the portal doesn't state one, so it defaults to USD.
IntegrationAccount integrations
Casino Controller.
Connect your Casino Controller affiliate account with your portal username and password to automatically pull daily and tracker-level performance reports.
IntegrationAccount integrations
Everygame.
Connect your Everygame affiliate account with your portal username and password to automatically pull daily, brand and campaign performance reports. Enter your Everygame affiliate ID in the integration settings — it appears in the Everygame portal and most accounts need it.
IntegrationAccount integrations
Digitain Centrivo.
Connect your Centrivo affiliate account with the API key and secret from its back office to automatically pull daily totals, per-media performance and per-player activity. You can narrow what is collected to a single brand or media type, and history reaches back 12 months — the furthest the Centrivo API allows.
IntegrationAccount integrations
JIM Partners.
Connect your JIM Partners account with the API token from your partner account to automatically pull your campaign stats — traffic, registrations, first-time deposits, deposits and commission, per day, promo code and brand. History reaches back to the 1st of last month, which is as far as the JIM Partners API goes; older figures stay in their portal. Note a token only works on the environment it was issued for, so a live token won't work against their staging site.

Improved30

ImprovedAccount integrations
Cellxpert reports are now configurable.
You can choose which breakdowns each Cellxpert report is grouped by (day, tracking code, brand, language, creative type, size and name) and narrow any of them to a single brand, tracking code or creative. Backfills are also much faster: a date range is now fetched in one request per report instead of one per day.
Read the full page
ImprovedAccount integrations
Clearer messages in run history.
When a run fails for a reason on our side, the run's message is now a plain sentence saying we've been notified and no action is needed from you. Failures you can act on (wrong credentials, an IP allow-list, an action needed in the partner's portal) still show their real message, unchanged. The same applies to Test connection.
Read the full page
ImprovedAccount integrations
Casino Controller and Income Access accounts can now use the proxy setting.
These two integrations now support the connection's proxy option. It is worth enabling if an account keeps reporting that the network refused our connection.
Read the full page
ImprovedAccount integrations
IREV accounts now collect daily and per-offer performance.
Previously an iREV connection only pulled the raw conversion feed. It now also collects your performance report — visitors, registrations, FTDs and commission — as daily totals and broken down by offer, using whichever figures your iREV account is entitled to. Two settings come with it: the currency the money figures are converted to, and the timezone days are counted in — set the timezone to match your reporting timezone in iREV, or daily totals will straddle midnight. You can also change the breakdown from offer to country, brand, goal or a sub-ID.
Read the full page
ImprovedAccount integrations
MAP brands on the new portal are picked up automatically, and now bring player data.
MAP has been rolling out a rebuilt affiliate portal, brand by brand. Routy now recognises which version a brand is on each time it collects, and switches to the new portal's data feed on its own — nothing to reconfigure, and a brand that gets upgraded later just starts working the new way. On brands already moved across you also get a player report: a row per player with their registration and first-deposit dates, deposits, revenue and your commission. Four optional settings come with it — which tracking variable (CID, PID or VAR1–VAR5) your click report is grouped by, whether to pull every available column or the portal's standard set, an optional filter to specific brands, and the row cap for the player report.
Read the full page
ImprovedAccount integrations
Test connection now works on MAP accounts.
MAP accounts answered "this integration does not support test connection", so the only way to check credentials was to wait for the next collection. Test connection now signs in the same way a real collection does — on the new portal or the old one, whichever your brand is on — and answers in seconds without pulling any reports.
Read the full page
ImprovedAccounts
Account status is now just Active, Inactive or Closed.
There were eight statuses, most of them leftovers meaning the same thing. Active works as before. Inactive means "not using it right now" — stats stop, links stop, everything is kept, and it still uses one of the account slots in your plan. Closed means done with it, and it frees the slot so you can connect something else; your history stays and you can re-open it later if you have room. Your accounts moved to their equivalent automatically — Enabled/New/Approved are now Active, Suspended is Inactive, and Disabled/Obsolete/Duplicated are Closed. See the guide.
Read the full page
ImprovedChannels
Voluum connections now report on the workspace they name.
If your access key covers several workspaces, each connection's figures now cover only its own. If you only have one workspace, nothing changes.
Read the full page
ImprovedChannels
Voluum syncs are quicker, and no longer store empty rows.
We were asking Voluum for every campaign every day, including ones with no activity at all — about three quarters of what came back was empty. We now ask only for campaigns that saw traffic. Campaigns with no activity are still listed on your connection; they simply no longer create a row of zeroes for each day.
Read the full page
ImprovedChannels
See the values behind a breakdown, not just how many there are.
You could tell that your Search Console query breakdown had brought back 18,740 rows across 5,502 distinct queries — and then not see a single query. You can now open a breakdown and get its values ranked over a period (your top queries this month, biggest first), and pick one to see day by day. One thing worth knowing: the ranked view shows fewer columns than the daily one. Clicks and impressions add up over a month; a click-through rate does not, and neither does an average position — so the ranked view shows what can honestly be totalled, plus a genuine average position weighted by each day's impressions, and leaves out what cannot. The daily view shows everything the vendor sent.
Read the full page
ImprovedChannels
Google Ads can report by ad group, keyword or ad — not only by campaign.
A connection reported one row per campaign per day and nothing finer, so there was no way to see which ad groups or search terms the spend actually went to. You can now choose the level: campaign, ad group, keyword, or ad. Keyword level also brings each keyword's quality score and its first-page and top-of-page bid estimates. These are different Google Ads reports rather than a filter on the same one, so a deeper level means more rows and a longer sync — and switching does not rewrite the days already collected, so ask support to re-pull a range if you need the history at the new level.
Read the full page
ImprovedChannels
Connection settings now tell you what a vendor accepts.
Where a channel has choices to make — which Search Console product to report on, which breakdowns to pull — the options come from the vendor rather than from you knowing them. A choice we cannot honour is refused when you save it, with the valid ones named, instead of being accepted and quietly ignored until the next sync. Capped choices say so: Search Console's breakdowns are limited to four, because each one is a separate request to Google.
Read the full page
ImprovedChannels
See what a connection actually pulled, per breakdown.
Asking a vendor for a breakdown and getting one are different things — a vendor can decline it, withhold rows for privacy, or have no data for those days. You can now see, per breakdown, how many rows and distinct values it holds, the days it covers, and which measures those rows carry. It also answers the confusing case: some vendors send different measures for different breakdowns — on Search Console's Discover product there is no average position at all — so a column that is empty for one breakdown and full for another is the vendor, not a fault.
Read the full page
ImprovedNotifications
Live alerts are back in the new app.
Notifications now appear as they happen while you have Routy open — a link stops resolving, an integration fails, an import finishes — instead of only showing up after a refresh. Alerts follow the affiliate you have selected, and respect the notification types you have switched on. They are an announcement, not the record: anything you miss is still waiting in your notifications list. (What live alerts are)
Read the full page
ImprovedNotifications
Your notifications now show when a problem keeps happening.
A recurring issue — a connector that keeps failing, an integration that keeps timing out — still appears as a single entry rather than filling your list with copies, but that entry now tells you how many times it has happened and when it last did. An entry that fired once looks exactly as it did before.
Read the full page
ImprovedNotifications
Failures and critical alerts now email you by default.
Informational notices — a link's destination changed, a summary of what we tidied up for you automatically — don't email by default, and can be switched on per type in your notification settings.
Read the full page
ImprovedNotifications
Every notification email and Slack message now links straight to your notification settings, so you can change what sent it, or switch it off, without going looking for the screen.
Read the full page
ImprovedNotifications
Slack now works from a single webhook.
Add your Slack webhook once in your notification settings and the alerts meant for Slack start posting — you no longer have to set one up notification type by notification type. Subscription and billing alerts, which could never reach Slack at all before, are included.
Read the full page
ImprovedPlans & limits
New limit: affiliate trackers.
Your plan can now carry a cap on how many affiliate trackers your account holds. Nobody is capped today — every existing plan is unlimited until a limit is set on it. When one is set and reached, links carrying a tracker name we have not seen before keep working and keep being tracked; they are simply recorded without a tracker rather than creating a new one. Clicks are never refused because of this limit.
ImprovedReporting
More detail in the same reports.
Deposits, chargebacks, withdrawals, downloads and earnings are now filled in, alongside a breakdown of estimated commission by CPA, RevShare, CPL and CPC shown separately from the commission the network reported.
Read the full page
ImprovedReporting
Summary reports follow your account scope.
The account summary reports are limited to the affiliates you can see.
Read the full page
ImprovedReporting
A tidier report list.
Reports that exist only to power a dashboard can now be kept out of the reports list, and the list comes back in a deliberate order instead of an arbitrary one. Nothing is taken away: a report kept off the list still runs, and the dashboards and links that use it are unaffected.
Read the full page
ImprovedTracking & redirects
Pixel setting changes now take effect immediately.
A change could previously take up to an hour to reach your site, with nothing to indicate it was still pending. Changes are now served on the next request. Your snippet is unchanged, so you never need to re-paste it — if you are verifying a change, hard-reload the page, since your own browser may still hold the previous copy for up to an hour.
Read the full page
ImprovedTracking & redirects
Your traffic source's website is now shown as a full web address.
Whatever you typed when you added the source — domain.com, http://domain.com, or a link to a particular page — is now stored and displayed the same way: https://domain.com/. Nothing about your tracking changes, your pixel snippet is unchanged, and you do not need to re-enter anything. Where a website had gone missing from a traffic source but was still recorded against its tracking pixel, it has been restored.
ImprovedTracking & redirects
Duplicate websites are now caught when you add a traffic source.
A website that is already registered can no longer be added again. Traffic sources you already have are untouched and nothing has been merged or removed, but if you have been adding a duplicate website deliberately, that will now be refused. See traffic sources.
ImprovedTracking & redirects
Affiliate trackers on a generated link are now checked before you get the link.
A tracker id has to exist on your account, otherwise the link request is refused straight away with the reason, so you find out before a visitor clicks. If a link generator or integration of yours sends a tracker id that fails this check, it will now get an error instead of a link.
Read the full page
ImprovedTracking & redirects
You can now name an affiliate tracker when you generate a link, not just pick one by id.
Type a name of 4–50 characters and it becomes a tracker on the first click that arrives. This already worked on links you built by hand; it just was not available when asking us to build one. Names shorter than 4 characters used to be dropped without a word, and names longer than 50 failed the click outright — both are now refused when you ask for the link, so you find out while you are still looking at it. Note that generated links are lower-cased, so a name you have used before is matched regardless of how you capitalise it.
Read the full page
ImprovedTracking & redirects
Impression trackers now match your own account.
The tracker on an impression pixel is resolved against your own trackers, and anything that does not match is recorded with no tracker.
Read the full page
ImprovedTracking & redirects
Your tracking pixel now records visitor device details.
Screen size, operating system, graphics hardware, language, timezone and connection speed are stored with each page view, and a device ID is worked out from the parts that belong to the machine rather than the browser — so the same visitor returning in a different browser is recognisable, even after clearing cookies. None of this is new information leaving your visitors' browsers: your pixel was already sending it with every page view and we were discarding it on arrival. It is on by default and can be switched off per site; Do Not Track visitors have their graphics details excluded automatically. See visitor device details.
Read the full page
ImprovedTracking & redirects
Page views are sent more reliably.
Everything used to travel in the page-view web address, which was close enough to the length limit some networks enforce that a long page title or a link with campaign tags could push it over — and past that limit, page views are silently lost. They now travel in the body of the request, which removes the limit. Older browsers fall back to the previous method automatically; your snippet is unchanged.
Read the full page

Fixed23

FixedAccounts
Going over your account limit now closes accounts instead of parking them.
When enforcement trimmed you back to your plan limit it used to move accounts to Suspended, which still used a slot — so you stayed over the limit and had to fix it by hand. It now closes them, which actually frees the slots, and it takes your inactive accounts before touching any active one.
FixedNotifications
Several notifications were never being sent at all.
A group of notifications had never worked — nothing arrived by email, in the app, or on Slack, and nothing in your settings looked wrong. Affected: CSV import updates (ready for review, completed, failed, expiring, expired, cancelled), monitored-domain down and recovered alerts, partner join requests, partner offer requests, new partner postbacks, account extract and transform progress, and two data-quality warnings about click tracking on an integration. The underlying events all happened and nothing was lost — only the notification was missing. You may now see notifications for activity that has been going on quietly for some time; if any type is noisier than you want, you can switch it off per type in your notification settings.
Read the full page
FixedNotifications
Network owners were not being told about partner join requests.
When someone requested to join your network, the notification was never delivered — not by email, not in the app, not to Slack. Nothing in your settings looked wrong; the notification simply never arrived. Join requests themselves were unaffected and are all still there, so nothing was lost. You will now be notified as intended.
Read the full page
FixedNotifications
Slack notifications were silently not being sent.
If you had Slack switched on for your account, notifications that were tied to a specific user — which is most of them — were never delivered to it. There was no error and nothing in your notification settings looked wrong; they simply did not arrive. They do now. If you switched Slack on and concluded it was not working, it is worth checking your notification preferences, because you may now receive more than you expect. Slack messages also fill in their detail — the account, connector or link a message is about — where previously those places were blank.
Read the full page
FixedNotifications
Notification emails were never actually being sent.
Switching Email on for a notification type did nothing — no email was ever delivered for any of them, with no error and nothing in your settings to suggest a problem. Email works now, so you may start receiving notifications by email for the first time; anything you don't want can be switched off per type in your notification settings.
Read the full page
FixedNotifications
Alerts about an account integration didn't say which account.
The email and Slack alert for a failed sign-in — and for a failed run, a missing password or missing credentials — arrived with the account name blank and a "view account" button that led nowhere. They now name the program, the account, the username we tried to sign in with and the account id, and the button opens that account directly.
Read the full page
FixedNotifications
Our emails were showing a broken logo.
The header image at the top of every email we send — password resets, invoices, alerts — pointed at an address that had never existed, so most mail clients showed a broken-image placeholder where the Routy logo should be. The logo now loads. Nothing about what the emails said, or who received them, has changed.
FixedPlans & limits
You could be blocked by a plan limit we had failed to renew.
If your quota period was never issued, or was cancelled or expired without a replacement, features you pay for were refused as "not in your plan", and clicks, conversions and postbacks were rejected and could not be recovered. Your service now continues while we re-establish your plan's limits, and your account manager is alerted automatically. A current plan that does not include a feature still blocks it. See what happens if we lose track of your plan limits.
FixedPlans & limits
Your shared event allowance is now counted properly.
Most plans include one monthly budget you can spend across clicks, conversions, postbacks, webhooks, page views and custom events, in whatever mix your traffic arrives — but that shared figure was never actually applied, and a limit set on a single activity type was being discarded when we checked it. Both now apply, and whichever you reach first is the one that stops you. Nobody is over their shared allowance today, so this changes nothing you will notice right now. Plans that set limits per activity type instead of a shared budget are unaffected. Where a plan sets a shared allowance of zero, that is now applied as the limit it is — on free accounts this means postback and impression tracking stops, while clicks and page views continue. See your event allowance.
FixedPlans & limits
A plan change could leave you with no limits at all.
If your subscription's billing date had fallen behind, editing your plan cancelled every limit you had and the replacement was discarded — so features stopped working until someone noticed. Your limits are now always replaced with a current period, and a replacement that would not be valid is refused rather than applied on top of nothing.
FixedPlans & limits
Usage figures that had stopped moving.
Where a billing period had lapsed, your usage was being measured against a window that had already closed, so the figures read near zero however much traffic arrived. Usage is now measured over the month you are actually in. Expect your usage numbers to go up — that is the correct figure appearing, not new consumption.
FixedPlans & limits
Usage warnings that only ever arrived once.
We tell you when you pass 70% of a limit. A comparison error meant that after the first warning you were never told again, however close to the cap you got. Warnings now follow your usage as it climbs.
FixedPlans & limits
A usage figure showing as `-1`.
Limits with no usage counter were displayed as "-1 / 1" instead of leaving the figure blank.
FixedPlans & limits
Accounts and domains could be disabled using last month's numbers.
Over-limit enforcement — which closes accounts, disables domains, deactivates partners and pauses link monitors — could run against a billing period that had already ended, where your usage figures stopped updating the day it closed. It now refuses to act unless the period is current.
FixedReporting
Corrected totals on the summary reports.
The day, account and account-by-day summary reports (/reports/days, /reports/accounts, /reports/accounts/days) were adding your network-reported figures to our own tracked figures for the same day, so accounts with both sources showed inflated clicks, signups and commissions. They now report one figure per day, preferring what the network reported. Expect these numbers to go down where both sources were present — the new figures are the correct ones.
Read the full page
FixedReporting
Custom reports showed `NaN` in every figure column.
Reports served from our analytics warehouse sent their numbers — visits, signups, deposits, revenue, commission, earnings — in a form the app couldn't read, so each of those cells displayed NaN and the value could not be recovered on your side. They are now sent as plain numbers, and a CSV or Excel export that had the same text in it comes out with the figures.
Read the full page
FixedTeam
You can now edit a teammate who is an admin.
Saving a teammate, including your account owner, now changes only the permissions you can grant and keeps everything else, so admins stay admins and a traffic-source restriction stays in place unless you change it. You still cannot grant admin rights to someone who doesn't already have them: see the team guide.
Read the full page
FixedTracking & redirects
Links failing with "Unknown place holder".
Incoming links carrying a parameter named clickid, tracker, dynamic, campaign or value could fail with an "Unknown place holder" error or redirect with a broken click id, so conversions could not be attributed back. These links now redirect with the real click id. Note that to pass your own click id through to the destination you should use cid, not clickid.
FixedTracking & redirects
Conversions sent to you from another Routy account were being rejected.
If another Routy account forwards its conversion events to yours — the sub-account setup, where they post to your hooks/catch address — every one of those posts was being refused with a "forbidden" error before it was read, so the conversions never reached your account. They are accepted again. Note that the events that were refused were not stored anywhere, so anything missed has to be re-sent by the account that was posting to you; talk to your account manager if you need a hand identifying the gap.
Read the full page
FixedTracking & redirects
Four tracking-pixel settings could never be changed after setup.
"Track every page", "auto-intercept clicks", "remember visitors with cookies" and "append traffic source id" could be chosen when a traffic source was created, but any later change to them was accepted and quietly discarded — the saved value never took effect. They now save. If you asked support to change one of these and it appeared not to work, it is worth asking again. See what you can configure.
Read the full page
FixedTracking & redirects
Closing a traffic source didn't stop its tracking pixel.
Closing a traffic source stopped it appearing as active, but the pixel on your site carried on sending page views, and they carried on counting. Collection now stops when you close the source, as it always should have. If you closed a traffic source and left its pixel installed, expect your page-view numbers to drop — that is the traffic that should never have been collected, not traffic you are losing. Removing the snippet from your site is still worth doing.
Read the full page
FixedTracking & redirects
A link carrying a deleted affiliate tracker stopped working entirely.
If a link named a tracker that had since been deleted, the visitor got a broken response instead of your destination — the click was lost, and so was the visit. Those links now redirect normally; the click is tracked, just without a tracker against it. Regenerate the link when you spot it, so the traffic is attributed again.
FixedTracking & redirects
Removed: the `[%Tracker%]` placeholder.
It could be pasted into a destination URL, but there was never anything to fill it with, so any link using it would have been refused on every click. We checked, and no link on the platform was using it — nothing changes for anyone. It is gone from the interface and the docs; [%Campaign%] is the placeholder that carries the tracker from your link.

Maintenance

Connector reliability: 45 fixes across account integrations and connected channels.