Table of Contents
A typical day for an affiliate manager looks about like this.
Send every affiliate a new set of links, because the GEO routing changed. Create a fifth identical payout rule, because the offer runs five landing pages. Grant landing page access to two thousand partners in order to hide it from two. Export statistics to Excel, because the metric you need doesn’t exist in the formula builder.
None of these looks like a problem. Each takes a couple of minutes and runs on autopilot, which is exactly why nobody counts it as work. The trouble is that those couple of minutes add up to half a day, and the more partners, GEOs and landing pages you run, the longer tomorrow’s list gets.
The six updates below are about that list.
Smart Link: one link for every GEO instead of one per country
Multi-GEO campaigns are still assembled by hand: a separate offer per country, a separate link per offer. The affiliate keeps them in a note and pastes the right one into each creative. With three countries that’s tolerable. With fifteen, sooner or later somebody drops a German link into a Spanish campaign.
And every change to the routing gets paid for with someone else’s time. You launch a new offer for Spain, pause Germany, and then start messaging every affiliate asking them to swap their link. A hundred partners stretches that over a week, and for that whole week part of your traffic keeps landing where nobody pays for it anymore.
Smart Link removes that dependency. The admin creates one in a dedicated section of the platform: name and description with localisation support, a domain for generating tracking links, public or private access. Then come the routing rules, mapping countries to offers:
- Germany → Offer A;
- France → Offer B;
- Spain → Offer C.
Every partner gets their own unique tracking link and never has to think about it again. On click, the system reads the user’s country, checks whether that partner actually has access to the matching offer, and sends the traffic there. In statistics the click is recorded against the offer the user was redirected to, so your usual offer-level reporting keeps working exactly as before.
You can rewrite the routing tomorrow: add Portugal, switch France off, point Spain at a different offer. The link on the affiliate’s side stays the same, and you won’t have to send a single message about it.
The whole setup lives in the Smart Link section: create it, add a name and description, pick a domain and access type, write the country-to-offer rules. Affiliates pull their own links from there.
Smart Link is a separate module and is enabled as part of your plan or as an add-on on request.
One special payout across several landing pages
Special payouts per landing page have been in Alanbase for a while, with one limitation: one condition, one landing page.
Now several landing pages go into a single payout. The setup works the same way it always did; only the selector changed — instead of picking one landing page, you tick the ones you need. This works for Goal, Formula and Qualification condition types, in both general and individual offer terms, and on mobile. The selector is built for real volume: accounts with several thousand landing pages are not unusual, so you won’t be scrolling the entire list to find three of them.
The setup order:
- Choose the condition type.
- Choose what the condition applies to.
- Set the parameters: countries, cities, OS, device types and the other available conditions.
- Create the special payout.
- In the Landing page field, switch on landing page selection.
- Tick one or several of the landing pages available to the offer.
- Enter the payout amounts and save the condition.
We also fixed how conditions are displayed. When a payout covers several landing pages, both the admin and the affiliate see the full list of pages it applies to. One rate across a group of landing pages is now set once, and edited once.
A landing page open to everyone except the few who shouldn’t see it
Three thousand affiliates in the network, and a new landing page that two of them must not see. The reason can be anything: an exclusive for one team, or a test page that’s too early to show around.
Before this release the task was solved inside out. You made the landing page private, then manually granted access to everyone who did need it. Thousands of operations for the sake of a couple of restrictions — and after that, every new partner needs a separate action, otherwise the page simply won’t show up for them.
Now offers and products have an exclusion mode. The landing page stays available to everyone, and the partners who shouldn’t see it go into an exclusion list when you create or edit the page. It works on mobile devices too.
Setup takes minutes instead of hours, and you describe an exception as an exception, rather than assembling it out of thousands of permissions.
Qualifications in the formula builder
In Statistics → General you build your own columns for your own reporting model: any metrics, any formulas. One thing was missing — the number of qualifications. Because of that, reports were built the long way round, or data was exported and finished off elsewhere, in Excel or your own BI. The familiar situation where the platform calculates almost everything, and one missing metric drags a whole separate process behind it.
The formula builder now has a Qualification count variable, and you choose which qualifications to include:
- approved;
- on hold;
- pending;
- rejected.
Statuses can be counted separately and compared against each other right in the table. You can, for example, output the share of rejected qualifications per partner and see immediately whose quality is slipping, without exporting anything. The variable is added when you create a new column or edit an existing one, and the status is picked in the same place.
Qualification analytics stay inside the platform, and the numbers in your report match the numbers in the system, because they are the same numbers.
API: product goals, active products and partner referrals
Three additions to the public API, each closing a manual step in an integration.
Product goals used to be created through the interface: the client’s service created the product, then a manager went into the platform and added the goals by hand. There’s now a Create goal method — an admin with access rights to products and advertisers creates them directly, passing the goal name and key.
The Create product method got an optional is_active parameter. Pass it and the product is created active. Leave it out and the API behaves exactly as before: the product is created inactive, and nothing breaks in your current integration.
Partner list and Partner by ID now return an array of referrals: ID, email and creation date for each, an empty array when a partner has none. Referral structures no longer need separate calls — they arrive together with the rest of the partner’s data.
All the methods are live, and they’re described in the current version of the API documentation.
Advertiser postbacks through the external API
The list of postbacks configured for an advertiser used to live only in the interface. Before launch you need to confirm that events and goals point where you agreed they would, so you open the card and check by eye. With dozens of advertisers, that check gets postponed until the moment something has already failed to fire — and by then the day’s conversions are too late to recover.
The new external API method returns an advertiser’s postbacks, both event routes and goal routes. Access rights are preserved: an admin only sees their own advertisers.
Checking the setup is now a request, with no cards to open. Postbacks can be synced with your own systems and verified automatically, before the configuration lets you down on live traffic.
What ties these updates together
All six work against the same pattern: the bigger an affiliate program gets, the more expensive every routine action inside it becomes. One link across ten GEOs, one condition across ten landing pages, one exclusion instead of a thousand permissions, one API request instead of a walk through the cards.
Individually, none of them is a headline release. Together they remove the kind of work that eats affiliate managers’ hours and never shows up in any report.
Want to see how this works on your own setup? Book a demo call: we’ll collect your requirements, walk through the platform for your offers and vertical, and set up a dashboard preset. After the demo — 14 days free, no card required.
