What Adease reads from Meta
The campaign, ad set and ad structure of the connected ad account, with its settings — objectives, budgets, audiences, placements, schedules — and its delivery metrics: spend, impressions, reach, frequency, clicks, results and cost per result, for Facebook and Instagram placements. Thirty days are synced on connection and the account is kept in step from then on.
The permissions, explained
- ads_read and ads_management — read the ad account and apply the changes you approve. Without ads_management the agent could only report.
- business_management — list the ad accounts your business has so you can choose which one to connect.
- pages_show_list and pages_manage_ads — list your Pages and attach one to ad creative, because every Meta ad is published from a Page. Adease never publishes organic posts, never reads Page messages and never reads Page insights.
- public_profile — the standard Facebook Login permission, used only to complete the sign-in.
Meta is where the agent goes furthest
Because the Marketing API supports it and the Page permission allows it, the agent can build a Meta campaign end to end from a brief — objective, ad sets, audiences, budgets and the ads themselves, using the client's Shopify catalogue — and publish it paused for your review. It can also copy a Google, TikTok or Pinterest campaign into Meta with targeting remapped to Meta's taxonomy.
Disconnecting
Disconnect from Integrations in the client's workspace, or remove Adease under Business Integrations in your Facebook settings. Either cuts access immediately. Disconnecting deletes the synced campaign data for that account from your workspace.
Where it fits
A good fit if you
- run Meta for e-commerce or lead-gen clients
- want campaigns drafted from a brief but published paused
- want a written record of every audience and budget change
Not a fit if you
- want an agent that acts on its own without review — Adease will not do that
- want Adease to post organic content to a Page — it does not
- work on Linux, or need a dashboard a distributed team opens in a browser
Questions people ask
Does Adease post to my Facebook Page?
No. The Page permissions are used only to attach a Page to ad creative, because Meta ads are published from a Page. Adease never publishes organic posts, never reads Page messages and never reads Page insights.
Can I connect several Meta ad accounts?
Yes. Connect each ad account inside the client workspace it belongs to. One Facebook login can connect every account it has access to, and each connection stays scoped to its client.
What happens when Meta expires the token?
The connection shows "Reconnect required" in Integrations. Reconnect with the same Facebook login and the synced data continues from where it left off.
Can it change my campaigns without asking?
No. There is no autonomous write path to a live ad account. Every change the agent proposes is queued in Approvals as a diff and applied only once a person approves it, inside the spend guardrails set for that workspace. Rejecting a proposal sends nothing to the platform.
Is my data used to train models?
No. Ad accounts, campaigns, knowledge cards and reports are never used to train machine learning models, and there is no setting that turns that on. Ad account credentials are never included in what is sent to the model.