Built for accounts that spend real money.
Limits per ad account, a kill switch, roles with per-account access, Meta access that never reaches the chat, and a record of everything that touched an account.
One sentence stops every automation on an account.
Owners, admins and buyers on the account can freeze. Only owners and admins can unfreeze. While frozen, the only allowed action is pausing.
- Rulesacting
- Manual actionsall
- Unfreeze—
Paused until verified
New ad sets and ads are created paused and switched on only after the read-back matches the plan.
Live re-read before budgets
If someone changed a budget after the plan was built, the write is blocked instead of overwriting it.
Daily limits per account
Caps on new ad sets, new ads, activations and total budget growth per day. Over the cap, nothing runs.
Your Meta access stays out of the chat
You connect accounts on app.adherd.net. Access is encrypted and never appears in ChatGPT, logs or tool responses.
Roles and per-account access
Owners, admins, buyers and viewers, each limited to the ad accounts they were given.
Audit log for every change
Who asked, what plan, who confirmed, what Meta returned. Everything that touches an account is recorded.
A misunderstood request hits a wall.
Every ad account has daily caps on what can be created, switched on and spent. They are shown in every plan, checked again at apply and before every rule write.
- Caps on new ad sets, new ads and activations per account day
- A cap on total daily budget growth, counted from the start of the day
- An optional ceiling on any single ad set’s daily budget
- Amounts in the account currency, days in the account time zone
- Only owners and admins change limits, through a confirmed plan
Four roles. Access per ad account.
Buyers and viewers see only the ad accounts they were given. Roles are checked on the server on every call, and removing a member revokes their access at once.
Your keys stay out of the conversation.
Connected on the web, never in chat
Meta access is added on app.adherd.net. It is never requested in or shown to ChatGPT, and there is no generic Graph API tool.
Encrypted, used in one place
Access is encrypted with your organization’s key and decrypted only in memory, right before a request to Meta. After saving, you see its last four characters and a date.
Never in logs or responses
Not in logs, errors, tool responses, URLs or the browser.
Checked on connect
adherd checks the access works, the permissions, the ad accounts it can see, write access and the app mode before anything runs.
Broken access stops everything
If Meta rejects the access, the connection is marked broken, jobs and rule writes stop, and an alert goes to every channel. Reconnecting keeps accounts, rules and history.
Pilot and after
In the pilot you connect a Business Manager system user. Facebook Login for Business follows once Meta’s app review is done.
Who asked, what ran, what Meta said.
Every organization’s data is isolated at the database level, and everything that touches an ad account is written to an audit log nobody can rewrite.
- Who, when and through which channel: ChatGPT, the web or a server job
- What action, on which ad account and object, with before and after
- The plan and request it belongs to
- Changes to settings, roles and connections, and failed permission checks
- Append-only: the application cannot edit or delete entries
- Filters and CSV export on app.adherd.net