Operator Platform - How to Update Commissions in Bulk: Status Changes, Amount Adjustments, and CSV Import
This article provides a guide for operators on how to update commissions and import them into the system.
The following topics are covered:
- Bulk Inline Updates for Statuses and Payouts
- Updating commission statuses
- Updating commission amounts
- Working with CSV files for import and updates
When to Use Each Method
| Method | Best for | Example |
|---|---|---|
| Status Changes | Approve/reject conversions | Approve 500 commissions |
| Amount Adjustments | Fix payouts | Adjust payouts after validation |
| CSV Import | Complex bulk updates | Sync data, manual adjustments |
Bulk Inline Updates for Statuses and Payouts
For quick updates of a single commission status, the web interface provides an option to select a new status directly via the UI. The change is applied immediately and updates the commission.

Additionally, it is possible to select up to 100 commissions per page and update their status using a bulk action.

For quick updates of payout, the platform allows selecting the required commissions and updating their amounts.
This applies not only to commissions with fixed payouts but also to commissions where the payout is calculated as a percentage. Payout can be updated for RevShare type without any additional steps.

Any interaction involving commission updates via the UI will prompt the manager to confirm whether affiliate postbacks should be triggered.
By default, postback triggering is enabled.
To prevent sending affiliate postbacks, the manager needs to uncheck the postback option before confirming the update.

β οΈ Important
- Only commissions that are not part of an invoice can be updated
- Changes cannot be reverted β only corrected by performing another update to restore previous values
π Notes Field
When performing bulk updates of statuses or payouts, managers can specify a reason in the Notes field.
- Notes are visible to affiliates (read-only)
- Managers have full access (read and edit)
This helps maintain transparency and track the reason for any changes.
Updating Commission Statuses
The platform provides the ability to bulk update commission statuses for up to 1,000 records using transaction IDs or click IDs.
Path:
Transactions β Adjustments β Change Status
Recommendations
- Usage of transaction IDs is recommended, as this is a unique value and ensures that only specific commissions are updated.
- When using click ID, note that a single click may have multiple commissions (for example, RevShare), and all matching commissions will be updated.
- If no specific conditions are defined (transaction ID, click ID, brand, commission type), the system will update all records within the selected time period.
Common mistakes
- IDs must be listed one per line, without commas or spaces
- No empty line at the end (even a hidden space may create an empty row and cause issues)
- Confusion between Track ID and Transaction ID β these are different parameters. For updates, Transaction ID is recommended.


By default, the Trigger Affiliate Postback option is enabled. This means that if the affiliate postback settings match the new commission status, the postbacks will be triggered automatically.
Updating Commission Amounts
In certain cases, there is a need to recalculate commission amounts for already generated but unpaid commissions β for example, to increase, decrease, or adjust payouts.
Path:
Transactions β Adjustments β Change Commissions
Steps
- Select:
- Brand
- Commission type (goal)
- New values for Revenue and Commission (Values should be equal to avoid affecting profit calculations)
- Define conditions:
- Time period
- Current status
- Recommended: Transaction IDs
Important notes
- The list of transaction IDs must be entered: one value per line, without spaces or commas, up to 1,000 records per task
- Usage of Transaction ID is preferred over click ID, as it ensures that only the exact commission is updated.

When updating commission amounts, affiliate postbacks are not triggered.
β οΈ Please note: adjustments cannot be reverted. Once applied, the changes cannot be undone β you can only submit a new task to modify the data again.
While the task is still in the queue and has not yet been processed, it can be deleted.
Working with CSV Files for Import and Updates
Path
Transactions β Adjustments β Insert Commissions (Conversions) via CSV
| Use Case | Template |
|---|---|
| Import Commissions without clicks | Insert without clicks |
| Import Commissions by Click ID | Insert by Click ID |
| Update Commissions by Click ID | Update by Click ID |
| Update specific Commissions using transaction ID | Update by Transaction ID |
Insert Conversions Without Clicks
This option can be used when there is a need to adjust the affiliate balance manually β for example, to add a commission without a click or player association. Typical use cases include chargebacks or bonus adjustments.
Required columns:
- affiliate_id β affiliate ID in Scaleo
- goal_id β commission type ID (specific per brand; available in the Goal filter on the Commissions page)
Optional fields:
- conv_status β status of the commission (approved, pending, rejected, trash)
- If not specified, the default status will be applied (based on brand settings)
- date β commission date. If not specified, - Default: current date at 12:00 UTC. Format: YYYY-MM-DD HH:MM:SS (e.g., 2021-01-01 12:30:30)
- revenue and payout β must be equal to avoid affecting profit calculations
- public_notes / private_notes β recommended to describe the reason for the import (e.g., bonus, chargeback)

Insert Conversions by Click ID
This option is less common for operator use cases, as most commission calculations are handled automatically on the server side. It is typically used for internal adjustments.
Allows adding additional commissions linked to an existing click (player).
- Adding a CPA for a player who did not qualify
- Adding CPL outside of commission plans
- Manually adding a flat fee
Required columns:
- click_id β click associated with the player
- goal_id β commission type ID
Optional fields:
- conv_status β commission status
- date β commission date. If not specified - Default: current date at 12:00 UTC, Format: YYYY-MM-DD HH:MM:SS (e.g., 2021-01-01 12:30:30)
- revenue / payout β must be equal
- public_notes / private_notes β reason for import
- adv_user_id β player ID to link the commission to the player (otherwise treated as a standalone amount)


This screenshot serves as a quick reference for how to easily find the commission type ID (goal_id) for a specific brand.
The number shown in brackets next to the commission type (e.g., CPA (2)) represents the goal_id, which must be specified in the CSV file.
Update Conversions
(Update by Click ID / Update by Transaction ID)
These options are used to update existing commissions. The difference lies in the filter condition:
- By Click ID β updates all commissions linked to a click
- By Transaction ID β updates a specific commission (recommended)
Key differences:
- If updating by click ID and goal_id is not specified, all commissions for that click will be updated
- If updating by transaction ID, only the exact commission will be updated (transaction ID is unique)
Capabilities:
- Update up to 20,000 commissions per task
- Update: statuses, amounts (revenue/payout), additional parameters: adv_param1β5, aff_param1β5
Recommendation:
Use Update by Transaction ID, as it guarantees precise updates without affecting unintended commissions.
When using Click ID, specifying goal_id is required to avoid updating multiple commission types unintentionally.
Step-by-Step Guide
- Download the required CSV template.
- Fill in the file according to the selected template.
- Ensure all required fields are completed.
- Upload the CSV file in the system.
- Wait for processing to complete.
- Verify results in the Transactions section.
CSV Format Example
affiliate_id,goal_id,conv_status,date,revenue,payout
10,2,approved,2026-01-01 12:00,15.00,15.00
How to fill in the file correctly?
Each of the templates has its own required fields without which your data will not be added.
In the table below you will see information about required fields, as well as some rules for filling in the parameters.
Note:
βοΈ Fields Required in the CSV.
βοΈ Fields are not used.
| Column Title | Insert conversions without clicks | Insert conversions by Click ID | Update conversions by Click ID | Update conversions by Transaction ID |
| transaction_id | βοΈ | βοΈ | βοΈ | βοΈ |
| click_id | βοΈ | βοΈ | βοΈ | βοΈ |
| affiliate_id | βοΈ | βοΈ | βοΈ | βοΈ |
| goal_id | βοΈ | Optional (Default: Default Goal) | Optional (Default: Default Goal) | βοΈ |
| conv_status | Optional (Default: Goal Settings) | Optional (Default: Goal Settings) | Optional | Optional |
| date | Optional (Default: Today 12:00 UTC) | Optional (Default: Today 12:00 UTC) | βοΈ | βοΈ |
| revenue | Optional (Default: Goal Settings + Custom Parameters) | Optional (Default: Goal Settings + Custom Parameters) | Optional | Optional |
| payout | Optional (Default: Goal Settings + Custom Parameters) | Optional (Default: Goal Settings + Custom Parameters) | Optional | Optional |
| adv_track_id | Optional | Optional | Optional | Optional |
| adv_order_id | Optional | Optional | Optional | Optional |
| adv_user_id | Optional | Optional | Optional | Optional |
| amount | Optional (Default: 0) | Optional (Default: 0) | Optional | Optional |
| adv_param1 | Optional | Optional | Optional | Optional |
| adv_param2 | Optional | Optional | Optional | Optional |
| adv_param3 | Optional | Optional | Optional | Optional |
| adv_param4 | Optional | Optional | Optional | Optional |
| adv_param5 | Optional | Optional | Optional | Optional |
| ip | Optional | Optional | Optional | Optional |
| idfa | Optional | Optional | Optional | Optional |
| gaid | Optional | Optional | Optional | Optional |
| public_notes | Optional | Optional | Optional | Optional |
| private_notes | Optional (Default: Imported from CSV) | Optional (Default: Imported from CSV) | Optional (Default: Imported from CSV) | Optional (Default: Imported from CSV) |
Some parameters have possible values and if you enter incorrect values, this parameter will be ignored or the whole data from the file will not be added.
| Column Title | Supported values |
| conv_status | approved | pending | rejected | trash |
| date | Date format should be YYYY-MM-DD HH:MM:SS, e.g. 2021-01-01 12:30:30 |
| revenue, payout, amount |
Integral or fractional number, e.g. 7.50. Note: Notation of a fractional number is allowed only through a dot. Any other symbol (e.g. comma) would not go through. |
Note: We recommend removing unused columns from the CSV file.
β οΈ Important:
- CSV must follow the correct format
- Incorrect data may affect reporting and payouts
What Happens After Upload
- Commissions are created or updated based on the selected template.
- Processing time depends on file size and number of records.
- If the data or format is incorrect, the task will not update any conversions.
β οΈWarningβ οΈ Completed adjustments cannot be reverted.
Limits and Recommendations
- Large files may significantly increase processing time.
- Recommended maximum is up to 20,000 rows per file for import or update.
- Ensure correct formatting before upload to avoid errors.
Common Mistakes
- Incorrect column names
- Missing required fields
- Invalid date format
- Using commas instead of dots in decimal values
- Extra spaces in values
Notes
- Fractional numbers must use a dot (e.g., 10.50).
- Date format: YYYY-MM-DD HH:MM:SS (e.g., 2021-01-01 12:30:30).
- Ensure no trailing spaces in CSV values.
- Use correct template depending on the task.
π‘οΈ Best Practice
β Before making bulk changes:
- Export data as a backup
- Double-check filters
β When using CSV:
- Test with 5β10 rows first
- Use a validated template
β After updates:
- Review reports
- Compare before/after values