---
name: execute-switch-boost-to-target-new-audiences
description: "Try a strong post with a new group. Keep the old proof and the new test easy to track."
category: Content Factory — Promote
stage: Promote
definitive_article: /dad
status: needs-work
---

# Execute switch boost to target new audiences

A post has helped one group of people. You want to test whether it helps another group too. This guide helps you keep the post, cost and results clear as you try the next audience.

**The path:** Verified pair → new audience hypothesis → separate test → updated map.

**Use this when:** A Promote-stage post has a qualified result and an untested relevant audience is proposed.

## Inputs
- Original post/ad IDs, full-window result and cost target; the current audience/creative map.
- The proposed saved/custom audience definition, date, eligibility and actual service-area fit.
- Account roles, authorized new-test or replacement scope, total commitments, spend controls and start/end dates.

## First-run prompt

> Prepare the next audience test from this verified winning post. Preserve the original evidence and use the same eligible post where supported. Check whether this is an additional test or replacement, avoid duplicate launches, and act only within the supplied budget and action scope.

## Steps
1. Confirm the original pair met its stated goal with enough evidence for a new test. Keep its actual post, audience, metric, window and budget record available; a display name alone is not enough.
2. Read the proposed audience definition and source. A saved preset from the insights task is a hypothesis, not proof of future results. Check service-area fit, permissions and any suggestion/expansion behavior.
3. Choose a separate test by default when the plan is to preserve a still-running winner. If the authorized plan is a replacement, record the old stop and new start explicitly. Do not accidentally change the old audience and destroy the comparison record.
4. Use the existing post ID in a supported preview, preserving it where the platform allows. If a format or account requires a new creative, label that derivative and the comparison limit; do not promise social proof transfers everywhere.
5. Keep the creative and goal comparable while changing the planned audience variable. Use the method’s $1/day, seven-day idea only where accepted. Account for differing launch dates, overlap and auction delivery; it is not a randomized causal test.
6. Add old and new spending commitments before activation. Reconcile current worker state and existing ads so this Promote task and the related Dollar-a-Day task do not launch the same test twice.
7. Read back authorized saved/active settings, then check early delivery and budget safety. Keep the intended review window stable unless an agreed protective rule requires a change.
8. At the due date, compare the same cost and result definition with the baseline. Record keep, stop or bounded hold, update the audience/creative map, and name the next stage only when its conditions are met.

## Definition of done (QA checklist)

- [ ] The winning pair and new hypothesis are source-backed and identifiable.
- [ ] Original evidence is preserved; any derivative or replacement is explicit.
- [ ] Actual budget controls, all commitments and dates fit scope.
- [ ] No duplicate test is created by overlapping recipes or retries.
- [ ] The updated map records the full result and its uncertainty.

## Example(s)

**Fictional teaching example:** The Promote log has one seat-fix winner in Cedar Town. A new Maple Town preset is eligible and relevant. The operator finds that another worker already staged that exact post/audience test under the Dollar-a-Day recipe, so the Promote task reviews and completes that record rather than launching a duplicate. The map links one actual test to the parent campaign. It does not count two paid executions merely because two guide names describe the work.

## Handoff and Content Factory context

This is the Promote-stage entry to [execute switch boosts to new audiences](https://local-service-spotlight.github.io/task-library/?task=execute-switch-boosts-to-new-audiences#task-execute-switch-boosts-to-new-audiences); use one real test record when the scopes overlap. Qualified pairs can feed [sequence content cold warm conversion](https://local-service-spotlight.github.io/task-library/?task=sequence-content-cold-warm-conversion#task-sequence-content-cold-warm-conversion) or a reviewed budget decision.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

One new audience test and its due readout. Further switches require a relevant hypothesis and existing authority, with no automatic spending loop supplied by a skill or model.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 5, gating 3 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** `create-new-saved-audiences-from-audience-insights`
- **Suggested next station:** `execute-switch-boosts-to-new-audiences`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Maintained method: https://blitzmetrics.com/dollar-a-day/
- Source mapping needs reconciliation: the preserved `definitive_article: /dad` points to the coaching program. The method page above is `/dollar-a-day/`; this record does not certify the coaching page as a task recipe.
- Exact task: [Execute switch boost to target new audiences](https://local-service-spotlight.github.io/task-library/?task=execute-switch-boost-to-target-new-audiences#task-execute-switch-boost-to-target-new-audiences)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Social Amplification Engine](https://blitzmetrics.com/social-amplification/)
- [Meta Advantage+ audience help](https://www.facebook.com/business/ads/meta-advantage-plus/audience)
- [Meta budget help](https://www.facebook.com/business/help/190490051321426)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- No account preview or new audience delivery was tested in guide authoring.
- An exact shared-post option may be unavailable; that is a documented limitation, not a reason to claim false continuity.