Продажи

Meta Ads QA in the signed-in browser, never write access

Conversion QA needs the ads UI. Write access is how you lose the account.

Что болело

Siamak Freydoonnejad’s article: Grok Bot shines when Meta conversion QA needs a signed-in ads UI on a remote computer while your laptop is off — event list, browser vs server, EMQ, last received. Use Claude or a connector when the data is already a clean API. Do not give either agent write access to the ad account.

Что установить или создать

One QA bot. Browser stays signed into Ads Manager on the bot computer. Scheduled look at Events Manager. Report only. No budget, no pause, no new ads. Tip + caution from the article — no invented prompt.

Боты

Ads QA
Looks at Events Manager on a clock. Reports EMQ / last received / red diagnostics. Never writes.

Плагины

Браузер
Нужен

Файлы

The cited article. Optional: a screenshot checklist of the Events Manager fields to copy each run.

Рутины

Morning look at Events Manager after one clean manual QA. Report only.

Промпт

Это совет, а не системный промпт, который можно вставить. Автор его не опубликовал. Следуйте шагам первого запуска.

Первый запуск

1Read the cited article. QA, not optimization.
2Sign into Meta Ads Manager yourself on the bot’s browser. Do not grant write.
3Name one QA bot: event list, browser vs server, EMQ, last received, red diagnostics.
4Run it once while you watch. Then hang a morning routine.
5If the job is “email me yesterday’s spend from an API,” use a connector instead. Still no write access.