A classic situation: you agreed with a partner to raise the payout starting the 1st. The 1st is a week away. The agreement lives in Telegram, the reminder lives in the manager's head. If the manager forgets, the partner sees the old rate, sends an angry message, and you end up manually recalculating conversions for the missed days.
In this article we'll look at what Affise itself offers for scheduling rate changes, where its limits are, and how to close the loop completely — from the agreement in a chat to notifying the partner.
What Affise can do: Scheduled Changes
Affise has a Scheduled Changes feature (Automation → Scheduled Changes). It lets you schedule a payout, revenue or cap change for a specific offer and goal at a set date and time, with timezone support. The system shows the current value, the scheduled value and when it will apply.
An important nuance: according to Affise documentation, Scheduled Changes is not available on every plan — you need to contact your Affise account manager to enable it. Check whether your plan includes it. The feature is also relatively new — Affise only documented it in autumn 2024. That's why many teams that hit this problem earlier still run their own scripts or manual reminders.
If the feature is available to you, it's a workable tool for the basic scenario: one change, one offer, a known date.
Where the built-in features end
In practice, a rate change isn't a single action in the tracker — it's a multi-step process. And most of those steps are outside what Scheduled Changes covers:
- The agreement lives in a messenger. The manager agreed with the partner in Telegram — but the scheduled change still has to be entered into Affise manually. Between "agreed" and "entered" there's still a human who can forget.
- Nobody notifies the partner. Affise will change the number, but telling the partner "your rate is new starting today" is still the manager's manual task.
- Context isn't preserved. A month later nobody remembers why the rate was raised, who approved it and where that agreement is recorded.
- Bulk changes are clumsy. If you have many agreements, each one has to be entered separately through the UI.
The workaround: changing rates via API — on any plan
An important detail that rarely gets mentioned: even if Scheduled Changes isn't included in your plan, changing payouts via the Admin API works on any Affise plan. The method POST /3.0/admin/offer/{id} with the payments[] array is a standard, documented Admin API capability — Affise even provides ready-made request examples in its help center.
So scheduling can be built yourself: a script or an assistant calls the API on the scheduled date and applies the new rate. That's exactly how many teams solved this problem before Scheduled Changes existed.
But there are two pitfalls that regularly break offers when teams write their own scripts:
- The payments array is overwritten as a whole. The request must repeat every payout of the offer you want to keep. Send only the one you're changing — and the rest (other geos, other goals) simply get deleted. A classic mistake that wipes out rates across half the offer.
- Payment ID. Every payout has a unique identifier (UUIDv4). When updating an existing payout you must pass it in the request — otherwise the system generates a new one every time.
The safe pattern: first fetch the offer via API → take the current payments array with all IDs → change the value you need → send the whole array back. That's exactly the scheme our assistant uses — which is why rate change scheduling works with us regardless of your Affise plan.
What a fully automated process looks like
Capture from chat
The manager tells the assistant: "Set partner X's payout to $28 on offer Y starting July 1." Or the assistant spots the agreement in the conversation itself and offers to lock it in.
Automatic application
On the scheduled date the change is applied in the tracker via API — regardless of whether anyone remembers it, and regardless of which tracker plan you're on.
Notification and audit trail
The partner gets a message about the new rate, the rate registry updates, and the history keeps a record: who agreed, when and where. The next reconciliation is calculated against the correct rates.
Which option is right for you
The honest answer depends on scale. If you have a few changes per month and Scheduled Changes is included in your Affise plan — start with the built-in feature; it may be enough. But if changes are frequent, agreements are scattered across chats, and reconciliations keep catching rate discrepancies, you need a process that connects the messenger, the tracker and the rate registry into one chain. That's exactly what an AI assistant does.
Want to see how this works in your business?
Book a free Automation Mapping session — we'll analyze your processes and show where AI can save the most time.
Book for free →