---
name: run-dollar-a-day-campaign-on-winning-content
description: "Use small ad tests on strong posts. Check the results and keep control of the money."
category: Content Factory — Promote
stage: Promote
definitive_article: /dad
status: complete
---

# Run Dollar a Day campaign on winning content

You have posts that people already find useful. This guide helps you test them with a small ad budget and learn from the results. Start with the proof, the goal and the total you can spend.

**The path:** Qualified content → priced tests → due verdicts → next bounded cycle.

**Use this when:** The owner has a supported offer, useful customer proof and qualified content for an authorized paid-amplification plan.

## Inputs
- The prerequisite finding, source posts with rights and organic metrics, and the goal/target.
- Exact platform/account, audience plan and measurement required for that goal; current roles and action scope.
- Currency, budget controls, total commitments, start/end dates, stop rules and existing test log/reviewer.

## First-run prompt

> Run this bounded campaign from the supplied qualified posts and goal. Reuse current verified setup, price every test and avoid duplicate active rows. Carry out only authorized actions, check early delivery and spend, and give each due row an evidence-based verdict. Record the actual result without inventing future winners.

## Steps
1. Review [verify prerequisites product customers content](https://local-service-spotlight.github.io/task-library/?task=verify-prerequisites-product-customers-content#task-verify-prerequisites-product-customers-content) and the actual goal. A catalog complete label is not a client-readiness pass or spend permission. Preserve unresolved business or proof gaps that affect this plan.
2. Select qualified original posts through [identify signals worth amplifying](https://local-service-spotlight.github.io/task-library/?task=identify-signals-worth-amplifying#task-identify-signals-worth-amplifying). Recheck rights, claims, captions and current paid eligibility. Do not use a new derivative’s inherited popularity as proof of its own performance.
3. Confirm only the tracking and account assets needed for the chosen goal. A view/engagement test and a website-sale test have different requirements. Reuse valid setup instead of demanding every analytics system be installed first.
4. Build the budget-supported audience/creative rows. The core method may layer one post per day; simultaneous tests are optional. Record each goal, amount, dates and due reviewer. Use the correct budget level for the chosen platform.
5. Price the nominal $1/day for seven days where supported, plus all overlapping commitments and relevant fees. Verify actual spend controls and platform minimums. A 20-row nominal week is $140, not a single $7 test or a zero-risk commitment.
6. Before any authorized launch, read the final settings and current shared log. After saving, record IDs/status and check early delivery, links and spending. Avoid unnecessary edits while retaining existing protective-stop authority.
7. At each full-window due date, score the matching cost and useful result. Stop failures under the agreed rule; hold inadequate evidence with a date and spending decision. About 90% retirement is not a forced quota.
8. For a qualified winner, consider the current $30 total/30-day continuation or a separately scoped increase at no more than 2× per step. New audiences and nurture stages require their own inputs. Close the cycle with a [Metrics, Analysis, and Action](https://blitzmetrics.com/maa/) report; repeat only under a real existing arrangement.

## Definition of done (QA checklist)

- [ ] Offer/proof and content qualify without invented readiness or rights.
- [ ] The goal’s actual measurement and audience conditions are checked.
- [ ] Every commitment fits the real budget controls and end dates.
- [ ] Early safety checks and full-window verdicts are both recorded.
- [ ] Next cycles, increases and overlapping recipe counts do not happen automatically.

## Example(s)

**Fictional teaching example:** A shop has two qualified clips and $14 for their nominal seven-day tests in an eligible account. The shared log shows one clip already has a staged test, so the campaign completes that row and adds only the missing one. At review, one has useful evidence and one does not. The report pauses the weak row within scope and proposes a $30 total/30-day continuation for the qualified one. That proposal is not labeled applied, and no new campaign is counted merely because a second guide helped review the same run.

## Handoff and Content Factory context

The campaign report feeds [apply metrics decomposition](https://local-service-spotlight.github.io/task-library/?task=apply-metrics-decomposition#task-apply-metrics-decomposition) when a component needs analysis, [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) for an eligible new audience, or [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) when a stage path is ready. Choose the actual needed handoff, not all of them by default.

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 bounded cycle by default. The method supports a weekly MAA loop for an ongoing campaign with real budget, owner, tools, durable state and trigger. A task file does not activate those parts.

## 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 4 (runs every factory cycle or weekly; ads/revenue path; gates a phase)
- **Suggested previous station:** `identify-signals-worth-amplifying`
- **Suggested next station:** `boost-top-3-5-facebook-posts`
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: [Run Dollar a Day campaign on winning content](https://local-service-spotlight.github.io/task-library/?task=run-dollar-a-day-campaign-on-winning-content#task-run-dollar-a-day-campaign-on-winning-content)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/)
- [Metrics, Analysis, and Action](https://blitzmetrics.com/maa/)
- [Social Amplification Engine](https://blitzmetrics.com/social-amplification/)
- [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, campaign or scheduler was activated during authoring.
- The current SAE article’s universal all-tool shipping gate and the strategist skill’s universal no-agent-action wording are flagged for their source owners rather than silently adopted.