---
name: create-youtube-campaigns-using-aducate-model
description: "Use a helpful video in a small ad test. Check the cost, views and next step."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: needs-work
---

# Create YouTube campaigns using ADUCATE model

You have a video that teaches one useful thing. This guide helps you test it as a YouTube ad. Start with the viewer’s problem and the result you want the test to measure.

**The path:** Useful video → fitting format → bounded campaign → measured result.

**Use this when:** A proven teaching video fits the campaign goal and the owner wants a paid YouTube test.

## Inputs
- Exact Google Ads account, YouTube video/channel, required account roles and link permissions for the chosen features.
- Approved video, media rights, captions, destination and goal; conversion setup only when that goal needs it.
- Currency, dates, allowed budget, success target, campaign type and test log; the source’s ADUCATE label does not supply an acronym definition.

## First-run prompt

> Use this approved teaching video and goal to prepare a bounded YouTube test. Verify the current format, campaign-level budget and reporting fields. Keep the documented teaching structure, and do not invent an expansion of ADUCATE. Execute only authorized steps and distinguish draft, delivery and outcome.

## Steps
1. Start with the owned Dollar-a-Day method: useful content with organic proof, then a small test. Write the viewer’s question, the lesson, its evidence and one fitting next step. The linked owned source does not define every letter of ADUCATE; do not invent those definitions.
2. Confirm the video is available on the correct YouTube channel and usable in the chosen ad. Review captions, factual claims, rights and the destination. Keep the opening useful instead of inserting an unsupported promise.
3. Choose a current campaign type and format for the goal. For skippable in-stream, the viewer can skip after five seconds, so put the point early. In-feed and Shorts work differently; do not apply a five-second skip rule to every format.
4. Choose supported audience and location settings that fit the offer. If using viewer remarketing, check the actual format, audience eligibility and permissions. A view does not guarantee that person can enter a retargeting list.
5. Set the budget at the campaign level. An ad group can have its own bids or targeting, but it does not provide a separate Google Ads budget. Separate budgeted tests need an appropriate campaign structure, with overlap and total commitments checked.
6. For a fixed test, consider the supported campaign-total option when creating a new campaign. It has a total amount and end date; existing campaigns cannot simply switch budget type. An average daily budget is flexible and may spend more on a day, so do not label $1/day a hard $7 weekly cap.
7. Before an authorized launch, re-read dates, networks/placements, objective, bidding, budget and video ID. Check early delivery and destination behavior with media silent. Do not click your own paid ad to test a landing page.
8. At the due review, use the actual format-specific metrics. Keep Google Ads TrueView views, public YouTube views, paid watch time and organic Studio metrics distinct. Report cost for the matching result; missing retention stays unknown.

## Definition of done (QA checklist)

- [ ] The teaching structure and proof are clear; no unsupported acronym is invented.
- [ ] The chosen format, video rights, captions and destination pass review.
- [ ] Campaign-level budget, amount, pacing and dates match scope.
- [ ] Early status and delivery read-back is distinct from the final performance review.
- [ ] The report names metric definitions and avoids mixed-source or mixed-denominator calculations.

## Example(s)

**Fictional teaching example:** A repair video opens with a loose seat and shows the fix. The planner chooses a supported skippable format and a new campaign with a $14 total budget over seven days, because that amount is the approved test. It is labeled a $14 test, not renamed a $1/day test. At review, the account reports $12 spend and 240 TrueView views, so cost per TrueView view is $0.05. That does not establish 240 unique people, full-video completions or new customers. The next step depends on the written goal.

## Handoff and Content Factory context

Give the campaign owner the campaign/video IDs and matching metrics for [analyze cost per result and engagement](https://local-service-spotlight.github.io/task-library/?task=analyze-cost-per-result-and-engagement#task-analyze-cost-per-result-and-engagement). Missing media goes to [upload processed video to youtube](https://local-service-spotlight.github.io/task-library/?task=upload-processed-video-to-youtube#task-upload-processed-video-to-youtube); a true conversion-path gap goes to [set up digital plumbing pixels tracking](https://local-service-spotlight.github.io/task-library/?task=set-up-digital-plumbing-pixels-tracking#task-set-up-digital-plumbing-pixels-tracking).

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

Set up one bounded test. Any periodic readout uses the actual campaign’s dates and existing monitoring scope. No recurring spend or new scheduler is created by the 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:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `review-budget-allocation-by-channel`
- **Suggested next station:** `set-up-tiktok-campaigns`
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: [Create YouTube campaigns using ADUCATE model](https://local-service-spotlight.github.io/task-library/?task=create-youtube-campaigns-using-aducate-model#task-create-youtube-campaigns-using-aducate-model)
- 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/)
- [Google video ad formats](https://support.google.com/google-ads/answer/2375464?hl=en)
- [Google Ads campaign budgets](https://support.google.com/google-ads/answer/2375454?hl=en)
- [Google Ads total budgets](https://support.google.com/google-ads/answer/10486938?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.
- The dedicated ADUCATE definition and a verified real example remain missing from the supplied owned source.
- No campaign or tracking access was tested; actual supported options and policy eligibility remain account-specific.