An AI ad agent needs separate review decisions for planning, paid generation, publishing, and account changes. Spark asks before supported spend-affecting actions by default. Review the actual proposed operation, not just the creative preview. Both image and video ads can be published directly to Meta with approval by default.
This guide explains operational approval around an agent. For team sign-off on design files and revisions, use the creative approval workflow. A designer approving an image and a buyer approving campaign spend are different decisions.
Know what you are approving
A conversation can move from research to creative to publishing in a few messages. Keep the boundaries visible so an instruction to explore an idea does not become a vague authorization to run it.
| Work | Review before proceeding |
|---|---|
| Planning and analysis | Product facts, evidence, dates, and missing information |
| Credit-consuming generation | Brief, selected output, model-dependent cost, and intended scope |
| Creative approval | Product accuracy, claims, offer, composition, and destination |
| Image and video publishing | Account, page, asset, campaign settings, and budget |
| Budget or status changes | Exact change, affected objects, and rationale |
| Recurring task | Task scope, schedule, mode, and who reviews its output |
This table is a review checklist. It does not imply that every plan or campaign action is supported, or that every team member has identical permissions.
Spark's default approval behavior
Spark asks by default before it creates a campaign or ad set, changes a budget, pauses or enables ads, or publishes to Meta. At an approval request, users can approve once, decline, or allow the action going forward.
Scheduled automations begin in Review mode so results wait for review. Switching a task to Autopilot changes how it can apply changes on its own. Review the task and its permissions before making that choice.
The practical point is that default review and persistent permission are different states. If you have allowed an action going forward, do not assume the next occurrence will ask exactly as it did the first time.
Current generation terms are described in the pricing document. Review the displayed cost before approving generation, especially when video footage or repeated revisions are involved.
Review the brief before paying for production
Suppose a homeware brand wants a new storage-box ad. The page has multiple sizes and a temporary promotion. Before generation, confirm the advertised SKU, included items, offer, approved benefit, and image.
Ask Spark to flag missing information and propose the concept first:
Draft a plan for this storage-box ad. Confirm the size, current offer, destination, and product photo. Do not generate or publish. List anything you need me to resolve.
Correct the plan, then approve a contained production task. This reduces the chance that you pay for many drafts built on the wrong SKU. It also gives the reviewer a clear description of what the output should contain.
Approval is only useful when the proposed work is understandable. “Make some ads” is weaker than “make one image draft for the space-saving concept, keeping this offer and photo.”
Review the asset before reviewing the campaign
Inspect the creative in its intended placements. Check text, product, claim, offer, CTA, and composition. For video, inspect scenes and captions rather than approving from the first frame.
Make revisions explicit. If the product and offer are correct, ask to preserve them while changing the opening. Re-review the changed asset; a correction can introduce a new issue elsewhere.
An approved image or video is ready for a launch proposal, not automatically live. Spark can publish either format directly to Meta after campaign approval. Keep creative approval and launch authorization distinct in your production process.
Review the proposed Meta action
Before publishing an image or video ad or changing an account setting, inspect the affected account and objects. Verify the intended page, destination URL, asset, campaign or ad set, budget, and any relevant schedule.
The question is “Is this the exact action I intend?” rather than “Does the ad look good?” A correct ad can still be sent to the wrong destination or account.
For a budget change, review the before and after amounts and the reasoning. Check whether the account context still supports the action. An earlier approval of a creative concept is not a blanket approval of later spending changes.
If something material is unclear, ask for a revised proposal. Declining a proposal can be the right outcome while the brief or account context is corrected.
Confirm what executed
After execution, check the result in the connected account. Did the intended object change? Is the creative present? Is the destination correct? Distinguish a proposed operation from a successful one.
If an operation fails, inspect the reported state before retrying. Do not assume the first attempt made no changes, and do not treat a conversational statement as stronger evidence than the actual account result.
Record the relevant identifiers in the team's review notes. They make it easier to inspect the right ad later and connect its results to the original concept.
Start recurring work with a narrow task
A useful first recurring task could summarize recent creative performance and suggest a next brief for review. It gives the team a chance to inspect the evidence and recommendations before relying on autonomous changes.
Specify the intended account, product, report period, and output. Keep the task's purpose understandable to the person reviewing it. “Explain last week's result for these concepts” is easier to assess than “optimize everything.”
Use Review mode while evaluating the task. Consider broader automation only after the team understands the behavior and the actions it may perform. Revisit scope when the offer, product, or account strategy changes.
Keep client responsibilities clear
For agencies, the client's creative approval may differ from the buyer's campaign approval. Agree who can approve product claims, promotional offers, and spending actions.
Document those responsibilities in the team's workflow; do not assume a subscription feature replaces an agreement about who owns decisions. The multiple-brand guide covers brand context and handoffs across clients.
If several tools can act on the same account, assign ownership to each kind of operation. Otherwise an approved decision can be undone or duplicated by another system.
Frequently asked questions
Does Spark spend without asking by default?
By default it asks before supported spend-affecting actions. Users can grant ongoing permission, and scheduled tasks can be changed from Review mode to Autopilot. Understand those choices before enabling them.
Does approving generation approve a campaign launch?
Treat them as separate decisions. Generation consumes credits; a launch changes a paid advertising account. Review the launch proposal explicitly.
Can Spark publish a video ad directly?
Yes. Spark can publish both image and video ads directly to Meta with approval by default. Review the finished creative and the launch proposal before proceeding.
What should I evaluate before allowing recurring changes?
The task's account, purpose, schedule, mode, supported actions, evidence, and executed results. Begin with a narrow task whose recommendations you can assess.
