Campaigns

Campaigns from Meta and Google appear in a single, consistent layout. A platform switcher at the top flips between them, so comparing spend or pausing things on both platforms is a matter of seconds, not two browser tabs. A hide-inactive toggle keeps paused and ended campaigns out of the way when you want a clean view.

A column picker controls which metrics the table shows: spend, impressions, clicks, CTR, CPC, purchases, CPA, ROAS, and frequency. Pick the few that matter to you; the choice is yours per table.

Meta follows its native hierarchy: drill from a campaign into its ad sets, and from an ad set into its ads. At each level you can edit in place:

• Campaigns and ad sets: budgets, schedules, and bid strategy.
• Targeting on ad sets: geography, age, gender, interests, and custom audiences.
• Creatives on ads: edit ad creative, upload new images, and preview the result before saving.
• Duplication: clone campaigns, ad sets, or ads as a starting point for variants.

Google gets the same treatment across its own object types:

• Campaigns: name, status, budget, and bidding targets.
• Ad groups and their RSA ads and keywords.
• Performance Max asset groups: text assets, search themes, and per-asset performance labels so you can see what Google considers strong or weak.
• New Search campaigns: create them from the Create menu; they are created paused so nothing spends before you are ready.

Every Google Search campaign has a search terms report showing the real queries that triggered your ads. Any term can be turned into a negative keyword with one click, as exact or phrase match, without leaving the report.

Select multiple rows on either platform and act on all of them at once:

• pause or enable,
• duplicate,
• export the selection as CSV,
• edit budgets in bulk.

Status changes come with an undo: if you pause or enable the wrong thing, one click puts it back.

Draft mode lets you queue up Meta edits instead of applying each one immediately. Make as many changes as you like, review the full list of queued edits, then publish them in one step. It is the safe way to do a larger restructuring: nothing reaches the Meta API until you hit publish.