---
name: boost-with-dollar-a-day
description: "Test a thank-you post with a small ad. Use this when the goal and budget are set."
category: Thank You Machine
stage: Promote
definitive_article: /thank-you-machine
status: complete
---

# Test a Thank-You Post With a Small Ad

A small ad can test whether a good post helps your business. This guide helps you use a thank-you post with a clear goal and a set budget. Start with a checked post. Finish with the test result and a choice to stop or keep going.

**The path:** Checked post and budget → small test → measured next choice.

**Use this when:** the post is suitable for paid use and the owner has named a goal, audience, total budget and decision date.

## Inputs

- The checked live post, its organic results if available and rights for paid use.
- The goal and success measure, allowed audience, ad account, budget, dates and authorized actions.
- Working measurement for the chosen result; a view goal and a sales goal require different proof.

## First-run prompt

> Use this post and budget to prepare the Dollar-a-Day test. Check current account limits, calculate total possible spend across all ad sets, and show the settings. Run only the spending actions already authorized. At the review date, use actual results to propose the next step.

## Steps

1. Write the goal, source post and audience in plain words using the [Goals, Content, and Targeting brief](https://local-service-spotlight.github.io/task-library/?task=gct-goals-content-targeting#task-gct-goals-content-targeting). Choose a useful measure and target before launch; gratitude or a tag is not evidence of sales.
2. Read the current Dollar-a-Day method and the actual platform’s budget rules. The initial method is $1 per day for seven days where supported. Daily budgets can be averages; this is not a universal hard $7 cap.
3. Count every planned campaign or ad set and its currency, dates and spending limit. If a minimum exceeds the authorized amount, reduce scope where supported or return the exact decision needed. Do not silently increase the budget.
4. Use a relevant audience supported by the current account. Do not assume named-person targeting, sensitive attributes, arbitrary interests or access to the recipient’s audience. Confirm the exact post and paid-use rights.
5. Prepare the ad, objective, destination, placements and measurement. Check a preview silently. Save the settings and total budget calculation so the owner can review any new spending decision concretely.
6. Launch only within the authorized account and spend scope. Read back the saved settings and delivery status. Record pending review, rejected or not delivering honestly; save the ad ID and check time.
7. Observe the planned test, but stop or repair a broken destination, consent issue or spend error promptly. At the decision date, compare actual spend and the chosen outcome with the target. Mark sparse or untracked data as inconclusive.
8. Propose stop, revise or a bounded winner test. The maintained winner stage is $30 total over 30 days where applicable; it is not $30 per day and is not automatic approval. Record any authorized next action and verify its saved state.

## Definition of done (QA checklist)

- [ ] The specific post, paid-use rights, goal, audience and account are checked.
- [ ] Budget arithmetic covers all ad sets, dates, currency and actual platform rules.
- [ ] Saved settings and delivery state are verified if launched.
- [ ] The review uses actual measured results and identifies missing data.
- [ ] A next decision is recorded without guaranteed reach, return or automatic scaling.

## Example(s)

**Fictional teaching example — no client result or completed run.** A fictional test plan has two ad sets at a nominal $1 per day for seven days: $14 nominal spend, subject to the platform’s rules. With only $7 authorized, it cannot launch both. The prepared plan makes that mismatch clear instead of claiming a $7 campaign.

## Handoff and Content Factory context

Save the post and ad IDs, dates, spend, measured outcome and next decision in the project report. Use [Metrics, Analysis, Action](https://local-service-spotlight.github.io/task-library/?task=maa-cycle-metrics-analysis-action#task-maa-cycle-metrics-analysis-action) to explain what the numbers support. Add a repeat only through the actual agreed runtime.

This fits the [Content Factory](https://blitzmetrics.com/content-factory/): Produce a true story, Process it into useful files, Post only in the agreed places, and Promote a suitable post when its test has a budget. Each stage passes its checked files and next owner forward.

## When this runs

Run for a specific approved test, then at its review date. An instruction file does not start ads or schedule a seven-day review.

## First-run setup and continuity

Use the files and accounts this task actually needs. A skill is a written recipe; the [AI worker](https://blitzmetrics.com/build-agents/) needs suitable tools and access to follow it. This file does not install an app, connect an account or start a timer. Follow the [setup guide](https://localservicespotlight.com/install/) for the chosen app. Carry out work already covered by the user's instructions; ask only for an exact missing item or a new action outside that scope.

Save the source, current state, checked result and next owner in the project files. Check that record before retrying or handing work to another person. Configure a repeat only when requested, with its time zone, actual runtime and first successful firing. An app or model name does not prove persistence, memory or a schedule.

Keep every agent media check muted with volume zero before playback. If that cannot be verified, use captions, metadata or still frames and record the limit. Do not play sound through the user's speakers without their current request.

## Write up the real run

For each real attempt, [write the meta article](https://blitzmetrics.com/meta-article-prompt/): its task and source revision, starting point, work done, evidence, measured result, gaps and next handoff. Save one execution ID across retries and edits. Partial, blocked and failed work also gets a record. A saved draft satisfies writing while any public release is pending. Writing does not grant publication authority.

A teaching example is not a real execution. Do not count it, a repeated check or a revision as another run. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains the link between reusable instructions and actual work.


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

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

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 4, revenue 5, gating 2 (runs every factory cycle or weekly; ads/revenue path)
- **Suggested previous station:** —
- **Suggested next station:** —
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

- Exact task: [Test a Thank-You Post With a Small Ad](https://local-service-spotlight.github.io/task-library/?task=boost-with-dollar-a-day#task-boost-with-dollar-a-day)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/) — how to record one clear point.
- [Content Factory](https://blitzmetrics.com/content-factory/) — how the source becomes checked posts.
- [Dollar-a-Day guide](https://blitzmetrics.com/dollar-a-day/) — the paid test method; current platform controls still need checking.

## Review and evidence still needed

The original contributor state is preserved. Instruction review, article certification, account access and completed work are separate states.

- Source mapping needs repair: on September 6, 2026, the recorded /thank-you-machine/ hub redirected to /face-socks/, a gift-ordering guide. That live gift recipe does not certify this video workflow. Keep the task ID and contributor state; use the relevant video and process guides below until the owner resolves the canonical video hub.
- Add a dated, real execution record with the actual checked output. The example below does not fill that gap.