Publishing an ad is the start of its life, not the end. Until this release, turning a campaign off or moving a budget meant leaving Nask AI for Meta’s own tools. On October 27 Nask AI shipped Live Ads, a page in the sidebar under Campaigns (marked Beta), and on October 28 a second release filled the gaps found on the first live launches.

What the Live Ads page shows

Live Ads reads the brand’s ad account from Meta and lists every campaign and ad set that is on or that spent in the last seven days, including the ones Nask AI did not publish. Ads load per ad set when you open it. A filter switches between Active or spent, 7 days, Everything and Paused only, and the columns show Spend, 7 days and Daily budget. A second view, Today, all brands, puts every brand’s account on one list for a morning check.

Only the ad accounts selected for the brand are listed or changed. When Meta does not return every object or the spend, the page says so in plain words and asks you to refresh instead of showing a partial picture as complete.

What you can change

  • Turn on and Turn off for a campaign, an ad set or an ad. Turning something on asks for one confirmation first.
  • Daily budget on ad sets that carry their own budget, and on campaigns that share one budget across ad sets. A raise above five times the current budget in a single step is refused, so a typo cannot multiply spend overnight.
  • Spending limit on ad sets: the minimum spend targets and caps Meta supports, added on October 28. When Meta refuses to turn an ad set on because of a minimum spend, Nask AI shows the campaign budget, the ad sets carrying limits, and the fix.
  • Duplicate an ad set. When Meta refuses a large copy, Nask AI now copies the ad set first and then each ad into it, paused, and reports which ads were and were not copied.
  • Move to another ad set for an ad. Through the Nask AI agent, an ad set can also be copied to another Facebook Page the account can promote, again created paused.

Every change is read back from Meta, and the read-back is what the page shows. If Meta refuses, its own message is shown. Some actions, such as turning ads on or moving them, need a workspace owner or admin.

The history

Each change is recorded with who made it, what it was before and after, whether Meta accepted it, and whether it came from the app or from the Nask AI agent. Open History on any row to see it.

Where it sits in the workflow

Live Ads is the step after publishing: the ads are running, and this is where they get adjusted without leaving Nask AI. See the whole sequence on how Nask AI works.