The limits are the contract between the engine and your operation. Every limit is yours, every proposal outside the routine goes through you and every decision is kept in Decisions with the previous value, the new value and the reason.
Every workspace starts with these values. You change each one in Rules › Limits; the floor, the cap, the target CPA and the guard rail of each group are set in the calibration and adjustable in Rules › What the engine operates.
| Limit | Default | What it holds |
|---|---|---|
| Actions per day, per ad set | 30 | How many writes the engine makes on the same ad set per day, increases and cuts counted together. |
| Cumulative change per ad set | 50% per day | How much an ad set's budget can go up in the day, adding up the increases. Cuts have their own separate cap; without a value of their own, they inherit this one. |
| Time between actions on the same ad set | 15 min | The minimum time between two writes on the same ad set. |
| Minimum budget | R$10 per day | The absolute floor: no cut takes an ad set below this, nor below 5% of the current value. |
| Floor and cap per group | set in the calibration | The bottom and the top each group can reach, in reais. |
| Target CPA and guard rail per group | set in the calibration | The cost per conversion the engine pursues and the value above which it enters emergency. |
Every item below exists in the engine today. Nothing here is a promise.
With the cost per conversion above the guard rail, the engine cuts the budget. When the rule would ask to pause or zero out, the engine converts it into a controlled reduction, of at most 50%, and the cut stops at the floor.
If the cost per conversion is less than 5% away from the target CPA, up or down, the engine does not touch it. An adjustment that small is not worth the auction again.
Up at 10:00, down at 11:00 and up at 12:00 does not pass. Each ad set has one direction reversal per day, and never less than 3 hours after the previous action.
After an increase, if the cost per conversion went up more than 10% in the following 6 hours, the engine does not increase the same ad set again.
The day's cumulative change counts the increases. Cuts have their own cap: an emergency is not blocked because the ad set already went up in the morning.
Beyond the cap per ad set, the workspace has an envelope: the sum of the ad set budgets does not exceed what you defined when the envelope policy is block or redistribute; in the alert-only policy, the overflow is recorded and the write proceeds.
After writing, the engine reads the value on the platform and compares. In Decisions each adjustment appears as applied, diverged or not checked.
The cycle checks each workspace's subscription before running. Without a valid subscription, the engine does not write and the owner is notified.
The engine reads the account every hour and decides on each ad set it operates, with the group's target CPA as the ruler. It is the regime for accounts with volume within the day.
At night, a cut of what proved inefficient in the closed day (volume-weighted cost above the guard rail), respecting the floor and limited to 30%. In the morning, the redistribution of the envelope among the eligible ad sets, preserving the total, with at most 35% change per ad set in the window.
The regime belongs to the workspace and appears in the calibration and in Rules. The limits on this page apply to both.
When you save the calibration, the engine enters observation: it runs in the chosen regime, decides as it would decide in operation and records every decision in Decisions, without writing anything to the account. You see what it would do before it does it. The simulation and the write test run in this phase, and it is the checked test that releases operation.
Accounts below 10 conversions per day stay in observation and do not leave it until the volume arrives or the conversion event changes: below that the engine would amplify noise instead of reducing cost. For the others, Optmos recommends at least 5 days and 20 recorded decisions before operating; what actually holds operation back is the checked write test and the minimum volume. The decision to operate is yours.
Decisions is the area of the console where everything the engine did or proposed is visible, in three tabs. To approve: the proposals outside the routine, with the reason, for you to approve or decline. Decided: what was approved or declined. Audit: every engine adjustment, with ad set, previous value, new value, reason, time and the result of the read-back.
What the Assistant proposes goes through the same place: it becomes a card, you approve or decline, and what is approved goes into Decisions like any other decision. Whoever has the viewer role sees all of this without being able to change anything.
The engine turns on and off in Rules › What the engine operates. Off, no budget is changed. To cut the access to the account, Settings › Workspace › Disconnect deletes the token at once; you can also remove Optmos in the app settings of Meta. The step by step, including deleting the whole account, is in Data deletion.
The factory defaults are 30 actions per day on each ad set, 50% cumulative change per ad set per day, 15 minutes between actions on the same ad set and R$10 per day of minimum budget. All are adjustable in Rules › Limits. The floor, the cap, the target CPA and the guard rail of each group are set in the calibration and adjustable in Rules › What the engine operates.
It enters emergency and reduces the ad set's budget. When the rule would ask to pause or zero out, the engine converts it into a controlled reduction, of at most 50% per decision, and the cut stops at the floor: never below R$10 per day nor below 5% of the current value. The engine never pauses, deletes or creates anything.
No. Each ad set has one direction reversal per day, and never less than 3 hours after the previous action. Within ±5% of the target the engine holds. And, after an increase that made the cost worse by more than 10% in the following 6 hours, it does not increase the same ad set again.
It is the Decisions area of the console: every engine adjustment with ad set, previous value, new value, reason, time and the result of the read-back on the platform (applied, diverged or not checked), plus the proposals you approved or declined. Whoever has the viewer role sees everything without being able to change it.
In the intraday regime the engine reads the account every hour and decides within the day. In the daily regime the engine decides in two windows of the business day: a cut at night, of what proved inefficient in the closed day, and a redistribution of the envelope in the morning. The limits apply to both.
Because every account enters observation when you save the calibration and stays there until you turn operation on, or because it is below 10 conversions per day on the declared event. In observation the engine reads, decides and records, without writing. Below the volume, it only leaves when the volume arrives or when the conversion event changes; with volume and the write test checked, the decision to operate is yours.
They appear in Rules › Limits from the first day, and in Today, on one line, every day.