---
name: sequence-content-cold-warm-conversion
description: "Put useful posts in a clear order. Match each one to what the reader needs next."
category: Content Factory — Promote
stage: Promote
definitive_article: /dad
status: needs-work
---

# Sequence content: cold → warm → conversion

A new reader may need an answer before they are ready to buy. A returning reader may need proof or a clear next step. This guide helps you match your posts to those needs.

**The path:** Introduction → useful depth → fitting offer → checked stage results.

**Use this when:** Several source posts have proven useful and the campaign needs a clear path across awareness, engagement and conversion.

## Inputs
- Actual posts with source links, rights and evidence; the real offer and destination.
- Eligible current audience sources/rules with time windows, consent and size/availability limits.
- Goal and metric for each used stage, total budget, action scope, dates and existing campaign records.

## First-run prompt

> Map the approved posts to what each audience needs next. Show actual stage metrics and supported audience rules, with missing eligibility visible. Keep the default nurture path without claiming all strangers must be excluded from every offer. Apply only the authorized setup and record actual delivery separately.

## Steps
1. Read each post and give it a primary job: introduce why it matters, explain how the work helps, or offer a relevant next action. The owned WHY/HOW/WHAT method is useful context; do not force a piece into a stage solely from its title.
2. Build the content map with the source URL, stage, intended audience, result and actual next link. Missing proof or offer material remains a production gap; do not invent case studies to fill a sequence.
3. List eligible audience sources for the intended path. Page engagement, supported video views and site events can have different rules. A pixel is not a universal prerequisite for an entirely on-platform engagement path.
4. Read actual inclusion, exclusion and expansion behavior. Keep a suggested audience distinct from a strict boundary. Do not promise an automatic escalator that captures and retargets every person who saw a post.
5. Use the source’s nurture path as the default: useful introduction, relevant depth, fitting offer. A specific high-intent goal may justify a direct offer to new people; document the reason instead of declaring all such ads invalid.
6. Allocate only stages that the approved plan and eligible audiences can support. Use small tests where feasible and count all commitments. No rule requires a tiny account to fund three active stages before any one can be useful.
7. Verify the configured stage map and actual saved settings. Where actions are authorized, check delivery and source/offer links without playing media aloud. Report created audiences, eligible audiences and actual stage delivery separately.
8. Review the matching stage metrics on the agreed cycle. Low warm-audience growth may reflect eligibility or consent as well as content. A weak conversion stage may involve measurement, audience or offer. Diagnose before asserting a cause, then name one supported next step.

## Definition of done (QA checklist)

- [ ] Each source piece has a real primary job and suitable next step.
- [ ] Audience eligibility and expansion limits are explicit.
- [ ] The path does not promise universal viewer capture or automatic movement.
- [ ] Funded stages fit actual budget/scope and have matched metrics.
- [ ] The review distinguishes possible causes and actual delivery evidence.

## Example(s)

**Fictional teaching example:** A shop maps its founder story to introduction, a repair demonstration to depth and a tune-up page to the offer. The platform reports too few eligible site visitors for the intended offer audience, though it has enough on-platform engagement for a depth test. The map records that exact limit. It does not call the founder clip a failure because the site audience is small. A separate high-intent search visitor may still see the tune-up offer under the existing search plan.

## Handoff and Content Factory context

This Promote-stage map uses the same method as [sequence content from awareness to conversion](https://local-service-spotlight.github.io/task-library/?task=sequence-content-from-awareness-to-conversion#task-sequence-content-from-awareness-to-conversion); keep one parent plan when scopes overlap. A supported website-visitor follow-up can go to [set up remarketing ads for landing page abandoners](https://local-service-spotlight.github.io/task-library/?task=set-up-remarketing-ads-for-landing-page-abandoners#task-set-up-remarketing-ads-for-landing-page-abandoners).

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

Design once and review within the active campaign’s agreed cadence. The source’s weekly flow check is optional until an actual recurring arrangement exists; no automatic sequence or schedule comes with this guide.

## 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:** `execute-switch-boosts-to-new-audiences`
- **Suggested next station:** `sequence-content-from-awareness-to-conversion`
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: [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)
- 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/)
- [Social Amplification Engine](https://blitzmetrics.com/social-amplification/)
- [Meta Advantage+ audience help](https://www.facebook.com/business/ads/meta-advantage-plus/audience)
- [Google Ads data-segment eligibility and duration](https://support.google.com/google-ads/answer/2472738?hl=en)

## 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 audience population or end-to-end stage delivery was verified in this authoring batch.
- The source article’s broad viewer-retargeting claims need their own correction.