Today
The state of the engine, what it did today and what needs you.
Optmos does not start by operating. It starts by reading. It connects the account, declares the conversion event, studies 90 days of the Meta account and only then, after the subscription, the calibration, the simulation with the write test and the observation, begins adjusting budgets inside your limits.
Sign in with email and password (or open the demo) and connect the ad account through Facebook Login for Business. Choose the ad account the workspace will operate.
Asks Meta for two permissions: ads_read, to read campaigns, ad sets and insights, and ads_management, used only to write the daily budget of the ad sets. Stores the token in the database and, at this step, only reads.
Say which event counts as a conversion: purchase, lead, sign-up, or a custom conversion.
Starts counting that event in the study, in the calibration and in the engine. It is what defines the cost per conversion of each group.
Wait for the study to finish. There is nothing to press: it starts when you enter the step.
Reads 90 days of the Meta account and delivers the day × time-slot matrix, the cost-per-conversion dispersion and the groups worth operating, with the volume of each one. Free, no card.
Decide whether you want to operate. If so, subscribe in the Stripe checkout. The card never passes through Optmos.
Charges a monthly fee on the budget of the groups enrolled in the engine (the ad sets checked in Rules), measured per day, with or without writes, on day 1 of each month, for the month just closed, and shows the amount in the product before the charge. Nothing is charged before this step.
Choose the groups the engine operates and set, for each one, the target CPA, the guard rail, the floor and the cap. Actions per day, cumulative change, time between actions and minimum budget start at the defaults.
Stores the rules per workspace and, when you save, turns the engine on in observation. Everything stays adjustable in Rules: what the engine operates, the limits and the suggestions.
Already in observation, see what the engine would have done on the history with your rules, decision by decision, and confirm the result of the test.
Runs the rules over the history without touching the account. In the write test, in the Meta account, it writes the current budget of the entity with the largest budget onto itself and reads it back: if the value matches, the credential writes; if it differs, some rule in the account is changing what we write. Only with the test checked can the engine leave observation.
Save the rules in step 05: that turns the engine on in observation. Follow in Decisions what it decided and why; if you pause it, turn it back on in Rules › What the engine operates.
Reads the account in the chosen regime and records every decision, without writing. Accounts below 10 conversions per day stay in observation until the volume arrives or the event changes.
Follow Today, Campaigns and Decisions; approve or decline what the engine proposes outside the routine; adjust limits whenever you want.
Adjusts, on Meta, the daily budget of the ad sets inside the limits, every hour (intraday regime) or in two windows of the day (daily regime). Records every decision with previous value, new value and reason. Never pauses, never deletes, never creates.
The state of the engine, what it did today and what needs you.
The account's campaigns and ad sets, with the current budget and what the engine operates in each one.
The record: proposals to approve, decisions taken and the audit of every adjustment with previous value, new value and reason.
What the engine operates (groups, targets, floor and cap, the engine switch), Limits and Suggestions.
By period and By day and hour: what the account delivered and the study's matrix, always up to date.
Workspace (connections, disconnect), Team (roles), Subscription and My account.
Roles: owner, admin and viewer. A viewer sees the six areas, but does not change rules, does not turn the engine on and, in Settings, only opens My account.
No engine decision changes the status of a campaign or ad set. When the rule asks to pause or zero out, the engine converts it into a controlled reduction, and the cut stops at the floor.
The engine does not delete campaigns, ad sets, ads or audiences. It only writes one field: the daily budget.
The engine does not create campaigns, ad sets, ads or creatives. What exists in the account is what you created on Meta.
In an emergency, with the cost per conversion above the group's guard rail, the engine reduces the budget down to the floor. That is the most it does.
To delete the whole account, or only the data of one ad account, the step by step is in Data deletion.
The first is connecting. The 90-day study comes before any charge.