---
name: create-dollar-a-day-ad-creatives
description: "Turn a useful post into an ad file. Keep its true message and show what test it is ready for."
category: Content Factory — Process
stage: Process
definitive_article: GAP — to be written
status: needs-work
---

# Create Dollar a Day ad creatives

An ad works best with a clear point worth sharing. This guide helps you turn a post with real response into files for a small test. Start with the source post and its measured results.

**The path:** Measured source → Placement brief → Useful variants → Checked creative handoff.

**Use this when:** The promotion owner requests creative files from content with documented organic signal.

## Inputs
- The real post/clip/article and its observed metrics, measurement date and comparison period.
- The [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) brief and intended campaign/placement, audience and content rights.
- Current specifications for those exact placements and access to an existing design/video editor.
- The Content Library folder, requested variant count and named promotion owner. Creative preparation does not itself spend money.

## First-run prompt

> Prepare the requested ad files from this source and dated organic evidence. Keep the claim true, inspect current placement specs, and make clearly tracked variants. Return checked assets and a test hypothesis. Keep untested ideas labeled and do not spend or launch outside the separate campaign scope.

## Steps
1. Read the organic evidence and why this content was chosen under [Dollar a Day](https://blitzmetrics.com/dad/). A view, share or comment is a signal, not proof of sales. If no evidence exists, prepare a clearly untested concept only if requested, and route validation to Post rather than marking it a winner.
2. Write a brief for each actual placement: purpose, asset type, ratio, duration, text fields, landing page and rights. Check current provider requirements; Facebook feed, Stories and YouTube formats do not share one universal size.
3. Keep the source’s supported claim and context. Adapt it for sound-off understanding with readable text/captions. Do not add a new performance promise just because the asset is now an ad.
4. Create the agreed variants, commonly two or three under the source method. Change one meaningful feature such as the opening crop or headline, and record the difference. Variant results are unknown until tested.
5. Export for the selected placements and inspect visible safe areas so controls will not cover the speaker, caption or key point. Google supports different ratios by format; YouTube does not mean horizontal-only.
6. Check copy lengths in the actual placement preview and verify the canonical landing URL. A provider preview passing does not certify the truth of a claim or approval of an ad.
7. Name each file by date/source/platform/variant and store it in the actual creative folder, using 04-Promote-Creatives when that is the project convention. Record dimensions, duration, file path, source-post ID and metric receipt.
8. Hand over the package with the hypothesis, difference between variants and unresolved eligibility checks. Launching, targeting and spend follow the separate already-authorized campaign task, not an automatic action caused by exporting files.

## Definition of done (QA checklist)

- [ ] Each selected winner has actual dated organic evidence, or is explicitly an untested requested concept.
- [ ] Claims, rights, caption text and source context are preserved.
- [ ] Each requested placement has a checked final export and clearly named variant.
- [ ] The handoff records the test hypothesis and real readiness; no campaign or revenue result is invented.

## Example(s)

**Fictional teaching example — no ad or real metrics.** A sample shop post got six useful customer questions over seven days. That invented teaching signal suggests testing its photo checklist; it does not prove sales.

Variant A opens with “Show the whole bike.” Variant B opens with “Help the shop see the issue.” Both use the same source demonstration and preserve the need for an inspection. The delivery sheet records which crop and line changed, the requested placement, and “test not launched.” It does not add a $1/day schedule or claim either version won.

## Handoff and Content Factory context

The promotion owner receives the assets for [Run the scoped Dollar a Day campaign](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) when its own inputs and authority are ready.

Produce supplies the real source. **Process**, this stage of the [Content Factory](https://blitzmetrics.com/content-factory/), turns it into useful finished assets. Post saves or publishes them on the agreed channels. Promote tests and distributes suitable work within its own scope. The handoff above names this task’s actual next step; catalog neighbors alone are not prerequisites.

## When this runs

Per selected source and defined creative batch. New variants follow observed test evidence; this task creates no recurring ad spend.

## 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:** Process
- **Importance:** 5/5 `●●●●●` — frequency 5, revenue 5, gating 4 (runs every factory cycle or weekly; ads/revenue path; gates a phase)
- **Suggested previous station:** `write-email-newsletter-from-video-key-insight`
- **Suggested next station:** `write-meta-article-documenting-agent-work`
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Process-stage artifact examples include `transcript.md`, `gct.md`, `article.html` (or a staged draft), `clips/`, or `04-Promote-Creatives/`. These are examples, not requirements for every task. Follow this task's actual Inputs and Handoff sections for the required output, evidence, and next owner. Pass the files or records, not one vendor's memory.

## Model routing (same factory, any engine)

- **This task's lane:** `any` — Any capable chat model (Claude, ChatGPT, Grok, Gemini). SOP following, drafts, checklists.
- **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

- Dedicated canonical article: not mapped in this source record. Use the maintained owned training below until that article gap is reviewed.
- Exact task: [Create Dollar a Day ad creatives](https://local-service-spotlight.github.io/task-library/?task=create-dollar-a-day-ad-creatives#task-create-dollar-a-day-ad-creatives)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Google video-ad specifications](https://support.google.com/google-ads/answer/13547298?hl=en-GB)
- [Meta placement specifications](https://www.facebook.com/business/ads-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.
- Dedicated article is unmapped; real metrics, rights and placement/account eligibility require project evidence. Meta specification page required login in this review.