← back to this week

Settings › Ads

specs/07-META-ADS.md — the app never creates a campaign; it creates a publicity in an existing ad set from what it just published, pauses the previous one, and (later) reads the results back. Three ad sets, made by hand in Ads Manager, are referenced here by id.

Connection

User token on file

Scopes: pages_show_list, ads_management, ads_read, business_management, instagram_basic, instagram_content_publish, pages_read_engagement, pages_manage_posts, public_profile

Ad account & ad sets

Ad account "This week" ad set id "Retargeting" ad set id "Boost template" ad set id

Each id is read back from the API when you save — a wrong or unreadable one is refused rather than stored.

"Visitors" ad set id (optional)

The Visitors "Tonight" ad set — the app never posts an ad here (its catalog ad is made by hand), only reads its monthly totals back for the block below. Optional: leave blank to skip it.

Monthly cap (€)

€120.00 remaining this calendar month.

Default per-night boost budget (€)

Only a suggestion, shown as placeholder text next to the remaining monthly cap wherever a budget is typed (the Week screen's "Boost with Meta Ads" field, and the manual Boost form) — never applied on its own. A boost is only ever created for the amount a person actually typed.

Dry run — log every boost, send nothing to Meta

This month by campaign

GitHub issue #18 — each fixed ad set's own totals, read directly from Meta, not only the ads the app itself created; docs/plan-marketing.md § 9.7's targets are shown next to the figure they apply to.

Campaign	Spend	Reach	Cost/purchase	Cost/click
Visitors	€0.00	0	—	— (target < €0.40)
This week	€0.00	0	— (target < €6.00)	—
Retargeting	€0.00	0	— (target < €6.00)	—
Boosts	€0.00	—	— (target < €6.00)	—

This month's boosts

None yet this month.