---
name: identify-signals-worth-amplifying
description: "Find posts that helped people. Use that proof to choose what to boost."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: complete
---

# Identify signals worth amplifying

You do not need to guess which post to boost. Look for posts that people already found useful. This guide helps you make a short list from your own results before you spend on ads.

**The path:** Recent posts → fair baseline → useful proof → short list.

**Use this when:** The team needs proven content for a small paid test or a fresh winner shortlist.

## Inputs
- The account’s available recent organic posts and metrics, ideally 60–90 days, with post URLs, dates and formats.
- The business goal, audience, ordinary baseline and content/media rights.
- Evidence for names, claims and results; current ad eligibility and a place to save the shortlist. Read-only exports are enough for this task.

## First-run prompt

> Rank these posts against their own account’s comparable baseline. Show the numerator, denominator, sample size and useful response behind each candidate. Select only proven, relevant, usable posts. Return the shortlist and gaps without spending, posting or inventing missing metrics.

## Steps
1. Collect the available recent organic history. Record the actual date range and any missing posts or metrics. Separate already-paid results so paid reach does not masquerade as organic proof.
2. Group comparable formats and goals. A 20-second clip and a long interview need different watch-time context; different platforms may define a view differently.
3. Compute a consistent engagement measure where reach exists: (reactions + comments + shares) ÷ reach × 100. Label this an interaction rate, not a unique-person rate. If reach is zero or missing, do not invent a ratio.
4. Compare with the account’s own median for a comparable group. The source’s two-to-three-times baseline can be a shortlist heuristic, not a universal win threshold. If the median is zero or the sample tiny, show absolute counts and that limit.
5. Read the actual responses. Questions, useful shares and relevant discussion may matter more than low-effort reactions. Remove spam or irrelevant response from the qualitative argument; do not secretly rewrite the source export.
6. Check whether each post helps the stated audience and goal. Keep proof tied to its source moment. Do not upgrade a co-appearance into a customer story, endorsement or close relationship.
7. Verify that the original post, media rights, captions, destination and current ad rules allow the proposed use. A strong post with an unresolved claim or rights issue remains on hold for paid use.
8. Choose up to three to five qualified candidates, with the evidence, reason and intended goal for each. If none qualifies, return that finding and a content task. Test fresh ideas organically first; do not divert an assumed 10% of paid budget into unproven content.

## Definition of done (QA checklist)

- [ ] Dates, paid/organic split and comparable groups are recorded.
- [ ] Every ratio has the correct denominator and a sample-size limit.
- [ ] Each candidate has useful response and goal fit, not only a popularity rank.
- [ ] Claims, rights and ad eligibility gaps remain explicit.
- [ ] The short list can be reproduced from linked post records; no budget action occurred.

## Example(s)

**Fictional teaching example:** A shop’s ten recent repair clips have a median interaction rate of 2%. The seat-fix clip has 20 reactions, six comments and four shares on 500 people reached: 30 ÷ 500 × 100 = 6%. That is three times the median. The reviewer reads the comments and finds real repair questions. A joke gets more likes but no buyer relevance, so it is not picked for this goal. The seat clip goes on the shortlist only after its music and claims are checked.

## Handoff and Content Factory context

Give the campaign owner the evidence-backed shortlist for [build audience layers](https://local-service-spotlight.github.io/task-library/?task=build-audience-layers#task-build-audience-layers). If useful source content is missing, return to [record one minute videos](https://local-service-spotlight.github.io/task-library/?task=record-one-minute-videos#task-record-one-minute-videos) with the actual questions found in the comments.

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

Run before a paid-test batch or during the already agreed content review. A repeated scan requires actual access to current exports and a configured trigger; a skill file does not watch an account on its own.

## 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:** `email-and-dm-client-about-published-article`
- **Suggested next station:** `run-dollar-a-day-campaign-on-winning-content`
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: [Identify signals worth amplifying](https://local-service-spotlight.github.io/task-library/?task=identify-signals-worth-amplifying#task-identify-signals-worth-amplifying)
- 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/)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/)

## 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 real account history, content rights or paid-use approval is supplied here.
- The owned article’s broad algorithm and income claims are not used as evidence that a given post will win.