Scheduled changes

Scheduled changes let you prepare offer updates in advance: pause an offer at midnight, raise a payout on the 1st, or set new caps for a promotion weekend. The worker applies each change within a minute of the chosen time, writes the audit log and notifies your team — and, if you want, the partners running the offers.

Schedule a change#

1. Open Reporting → Automation → Scheduled changes (/app/automation/scheduled).

2. Click Schedule a change.

3. Fill in Schedule an offer change:

   Field	Notes
   Offers	1–200 offers of the workspace.
   Change	Offer status, Payout / revenue or Caps.
   When	Date and time, local time in your time zone (shown under the field).
   Note	Optional, shown in notifications and the list.
   Tell approved partners	"Partners running these offers get a notification when the change is applied."

4. Then the fields of the chosen change (below), and click Schedule change.

Offer status#

New status: Active, Paused or Archived.

Payout / revenue#

All optional — fill in only what should change:

The offer-level default payout and revenue change. Payout overrides per partner and custom payout rules are not touched.

Caps#

Cap changes (merged into the offer's caps) takes JSON with only the caps to change — the metrics clicks, conversions and payout and the periods daily, weekly, monthly and total:

{"clicks":{"daily":5000},"conversions":{"daily":100,"monthly":2000},"payout":{"daily":"750.00"}}

• A listed period sets that limit (counts are whole numbers ≥ 0, payout an amount such as "750.00").
• null removes a limit — {"clicks":{"daily":null}} — or a whole metric — {"payout":null}.
• Everything the JSON does not mention stays as it is: the offer's other metrics and periods, and the revenue caps, hourly caps and soft setting of the offer's Caps tab. Partner-level caps are not affected.

An empty change ({}), an unknown metric or period, or an invalid value is refused when you schedule ("List at least one cap to change, …", "Unknown cap metric …"). The change is merged into each offer's own caps, so one scheduled change can raise a daily cap on offers whose other caps differ.

What happens at the scheduled time#

1. The worker (every minute) claims the change (pending → running) so it is applied exactly once.
2. All offers are updated in one transaction, with one audit-log entry per offer under the name of the person who scheduled it.
3. The edge picks up offer changes immediately (status, caps and money take effect for the next click or conversion).
4. Staff are notified; with Tell approved partners, partners with approved access to the offers are notified too.
5. The change ends done with a result text, or failed with the error.

Changes are applied to offers that still exist in the workspace. Archiving an offer this way stops its affiliate links (they fall back); transparent url= links keep redirecting to their url= address.

The list#

Columns: Runs at (with time zone), Change (a summary such as "Status → paused"), Offers, Tell partners, Status and hidden By and Result. Pending changes come first.

Only pending changes can be cancelled ("Only pending actions can be cancelled."). To change a pending change, cancel it and schedule a new one.

Permissions#

Scheduling and cancelling need a manager role or higher; analysts can view the list.

Examples#

• Black Friday payout bump: Change Payout / revenue, offers "Shop US" and "Shop CA", When Friday 00:00, Payout 12.00, Tell approved partners on — and a second change on Monday 00:00 back to 10.00.
• Advertiser budget ends: Change Offer status, New status Paused, When the last day 23:59.
• Promotion weekend: Change Caps, When Saturday 00:00, {"conversions":{"daily":500}} — and a second change on Monday 00:00 with {"conversions":{"daily":100}} (or {"conversions":{"daily":null}} to remove the daily cap).

Related#

• Automation overview
• Cap alerts and caps pacing