Table of Contents
Hybrid payout models stopped being the exception a long time ago. A serious program almost always runs partners on CPA and RevShare at the same time, adding Fix Fee somewhere in the mix. While volume is low, you can split accruals across models by hand. At scale, that same manual reconciliation produces money errors and loads up the team. The latest Alanbase updates hit exactly this point: they remove manual steps in payouts, analytics, tasks, and integrations.
Invoice generation by payout model
A hybrid offer combines CPA and RevShare. Before, when you created a payout, the system pulled in every matching conversion at once, even when you only needed to close one type of reward. Splitting them meant doing it by hand: export and recalculate. At every one of those steps, the wrong amount lands in the partner’s payout.
Now the payout creation window has a “Payout model” filter: All, CPA, RevShare, plus Fix Fee and CPM if they’re connected and enabled in the account.
In practice: a partner works on CPA + RevShare. You first close the invoice for CPA over the current period, then create a separate payout for the RevShare accruals. No duplicate offers, no manual filtering of exports.
Where the owner’s money is here. Manual reconciliation costs more than a finance manager’s time, and you pay for it in two places. First, an error in a payout to a strong partner. Top affiliates fear unpredictability: manual recalculations and cuts after they’ve pushed volume. One disputed payout on a hybrid deal damages trust more than a week’s delay in a manager’s reply. Second, speed. While the team sorts payouts by model by hand, the cycle stretches out, and for a media buyer a delayed payout means a stop on traffic buying. Separate invoices by model remove both risks: the partner sees the correct amount on clear logic and gets it faster. For a program that retains large buyers, this works for retention.
Drag-and-drop in the task tracker
Now on the Kanban board you can drag a card both to another column and up or down within its own, without opening it for editing. The new order persists after a page refresh.
On a large task list, this gives the team back control over priorities: you move what matters to the top in a single gesture, with no menus and no extra clicks.
Copying dashboard widgets
When you build a dashboard, you often need several near-identical widgets with a single difference: the same metrics, but by a different geo, offer, or period. Before, you had to set up each one from scratch.
Now you copy a widget in one click with all its settings: statistics indicators, line chart, pie chart. Before saving the copy, you can change any parameter.
What this means for an analyst: you build a comparison view (geo vs geo, offer vs offer) in a minute instead of ten. The cheaper a comparison is to build, the more often the team looks at breakdowns instead of the blended average.
API method for the partner tag list
This update is for teams building automation on their own side. Tags in Alanbase help segment partners, but pulling their full list through the external API wasn’t possible before.
The new method returns the tag ID and name. That makes it easier to sync data with external systems and set up tag-based scenarios. The public API documentation already covers this endpoint.
Straight talk on reach: it’s a narrow feature, one a tech team will pick up, not managers. But for programs that automate work with segments, it closes a specific gap in integration.
What ties these four updates together
Separately, these are different parts of the platform. The shared logic is one: at scale, manual operations turn into costs, and taking them out of the process pays off.
Estimate the cost of this routine on your own numbers. Count the risk, not the minutes saved. Take one typical source of loss, say disputed payouts on hybrid deals. Multiply the frequency (how many times a month a payout goes out with manual reconciliation) by the probability of an error and by the cost of one unhappy large partner. The cost here isn’t the size of the correction, but the probability that they move volume to an advertiser with a more predictable process. What makes manual reconciliation expensive is usually that term, not the finance manager’s salary. Apply the same reasoning to analytics (the cost of a decision made on the average instead of the breakdown) and to tasks (the cost of a lost priority inside the team).
Takeaway
These updates don’t add “features for the sake of features.” They remove manual steps where money and risk hide at scale: in payouts on hybrid models, in comparative analytics, in task prioritization, and in integrations.
Want to see how this maps onto your program and your payout models? Book a demo call: we’ll assemble a preset of dashboards and payouts to your requirements and open access to Alanbase for 14 days with no card required.
👉 Book a demo: https://alanbase.com/
