Skip to content

Automatic ad management

SparkleTree can run your campaigns as Meta ads: you deploy from the campaign itself, start and pause the ads from SparkleTree, and SparkleTree keeps the status and figures in sync with Meta.

Note: Automatic ad management is Meta-only today. Bluesky has no ads by design, and Reddit and TikTok ads are in preview — see Connect your accounts for where each platform stands.

  • A workspace admin has connected your Meta account in Dashboard → Settings.
  • You have the editor role or higher. Members and viewers can see Meta insights but can’t deploy.
  1. Open your campaign from the dashboard.
  2. On the campaign detail page, open the Deploy to Meta dialog.
  3. Review the details and confirm.

Your campaign is now a Meta deployment, managed from SparkleTree.

A new deployment is created on Meta paused, so nothing is spent until you decide. Press Start in the campaign’s Meta ads panel to begin delivery. After that the same button reads Pause while the ads run and Resume once they are paused.

If someone paused individual ads by hand in Meta Ads Manager, Start and Resume leave those ads paused, and the panel says how many were left that way.

SparkleTree reads each deployment back from Meta: the campaign and ad status, the figures (impressions, clicks, click-through rate, spend), and changes made in Meta Ads Manager. It does this when you open the panel and the last check is more than 10 minutes old, and on its own every 3 hours. The panel shows when it last checked (“Updated 4 min ago”).

The same figures count in Dashboard → Analytics: Meta impressions, clicks and conversions are added to the Impressions, Clicks and Conversions totals, and Meta reach is shown as its own figure, never added to Sessions. See Analytics.

What the status means:

  • Deploying: SparkleTree is creating the campaign and ads on Meta.
  • Running: Meta is delivering the ads.
  • Paused: the ads are paused, by you or in Ads Manager.
  • In review or Rejected: Meta’s ad review has not approved the ads yet, or turned them down.
  • Not delivering: the ads look active but Meta is not showing them, for example because the ad account has an unpaid balance or is disabled.
  • Deleted or Deleted in Ads Manager: the campaign no longer exists on Meta.
  • Deploy failed: the deploy did not finish.

Budgets and spend are shown in your Meta ad account’s currency.

If an ad is copied in Ads Manager and the copy replaces the original, SparkleTree follows the copy and keeps counting its figures under the same variant. Ads created directly in Ads Manager that match no variant are not counted, and the panel notes how many there are.

Delete removes the campaign from Meta. SparkleTree reads the latest figures first and keeps them, so the spend and results stay in your workspace after the ads are gone. A campaign deleted in Ads Manager shows as Deleted in Ads Manager, and the figures collected up to then are kept the same way. To run the campaign on Meta again, use Deploy again.

Pressing Start or Resume begins spending your Meta ad account’s budget. Editors and admins can both do this; there is no separate approval step before spend begins. To keep someone from starting ads, give them the viewer role.

The Emergency stop is the guardrail of last resort: one admin-only action that pauses all of your workspace’s Meta deployments at once.

Use it when something is wrong and you don’t have time to triage — a broken landing page, a pricing error, a post that must not run another minute. Stop everything first, sort it out second.

Two things to know:

  • Admin-only. Only workspace admins can trigger it.
  • It fails safe. SparkleTree pauses your deployments both locally and on Meta’s side. If Meta’s API partially fails during the stop, SparkleTree still pauses everything locally — you’re never left with the button pressed and nothing recorded.

After an emergency stop, resume deployments individually once you’ve fixed the underlying problem.

Florence, your AI marketing assistant, can review your ad performance and propose next moves as part of her strategic loop. She works within the same role and autonomy gates as everything else — see Meet Florence.

Action Who can do it
Deploy to Meta Editor or higher
Start, pause or resume a deployment Editor or higher
Delete a deployment Editor or higher
Refresh status and figures Everyone in the workspace
Emergency stop Admin only
View Meta insights Everyone in the workspace