---
name: set-up-tiktok-campaigns
description: "Plan a small TikTok ad test at its real price. Use a strong clip and check the result."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: needs-work
---

# Set up TikTok campaigns

You have a useful clip and want to test it on TikTok. The test may cost more than one dollar a day. This guide helps you check the real price and decide if it fits your plan.

**The path:** Proven clip → actual minimum → bounded test → useful result.

**Use this when:** A proven video fits TikTok’s audience and the owner wants a bounded paid test at the platform’s actual cost.

## Inputs
- The eligible TikTok Ads account, authorized identity and roles; actual billing currency, allowed budget and dates.
- A proven video with commercial music/footage rights, readable captions and an appropriate destination.
- Goal, target and required event measurement; exact current campaign/ad-group settings and minimums.

## First-run prompt

> Prepare a TikTok test from this approved clip and goal. Read the current minimum budgets and state the full real cost. If it exceeds the authorized amount, return that gap rather than launching. Keep account setup, creative approval, delivery and result evidence separate.

## Steps
1. Use the owned Dollar-a-Day discipline: proven useful content first, then a bounded test. A winner from another platform is a candidate, not proof it will perform the same on TikTok.
2. Confirm the actual ad account, identity and content permission. Review rights for commercial use, including music; do not assume a song allowed in an organic post is cleared for an ad.
3. Write the goal and metric, then choose the eligible objective and measurement route. A website conversion goal needs its actual event path checked; an on-platform view goal does not automatically require a website pixel.
4. Prepare the video for the chosen format with a clear opening, useful lesson, fitting next step and captions. Check placement crops with media muted. Native style can be a creative approach; raw footage is not guaranteed to outperform edited work.
5. Read the current budget rules before building a matrix. TikTok’s official guide states daily budgets must exceed $50 at campaign level and $20 at ad-group level; lifetime rules differ. Confirm the controls used by this actual campaign and quote the real commitment, not a renamed “dollar.”
6. Select supported audience settings tied to the actual market and goal. Record constraints, suggestions and eligibility instead of copying every age/interest layer from Meta. Use fewer tests if the permitted budget and review capacity require it.
7. If authorized and feasible, set the real budget, dates and creative, then read back the saved state and early delivery. If the minimum does not fit, leave the paid test pending and retain the organic candidate. Do not switch budget type or expand scope just to make launch pass.
8. At the due review, compare the matching cost, view/watch metrics and useful response with the goal. Send stop, hold or further-test decisions to the campaign owner. Any later increase is a separately checked change; ≤2× is not a promise about TikTok learning behavior.

## Definition of done (QA checklist)

- [ ] Creative rights, identity and cross-platform evidence limits are recorded.
- [ ] The actual objective and necessary measurement match the goal.
- [ ] Minimums, budget type, full amount and dates are explicit.
- [ ] Infeasible spend stays pending without an automatic increase.
- [ ] Saved settings, delivery and performance verdict have distinct evidence.

## Example(s)

**Fictional teaching example:** A shop has only $21 authorized for all testing this week. Its seat-fix clip is a good organic candidate, but the chosen TikTok ad setup requires a daily amount above $20 at the ad-group level. A seven-day paid plan cannot fit $21. The planner records the exact mismatch and keeps the TikTok paid step pending; no new card is added and no budget is raised. The same clip may still be reviewed for an existing organic posting plan. This is a completed feasibility check, not a completed ad campaign.

## Handoff and Content Factory context

Send a feasible authorized campaign’s log to [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). The campaign owner resolves a budget mismatch; the content owner retains useful clips for appropriate organic or later paid work.

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

One bounded setup/test. A weekly performance review applies only to an actual active campaign under an agreed arrangement. A guide or downloaded pack does not schedule 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:** Promote
- **Importance:** 4/5 `●●●●○` — frequency 4, revenue 4, gating 2 (runs every factory cycle or weekly; creates the asset ads amplify)
- **Suggested previous station:** `create-youtube-campaigns-using-aducate-model`
- **Suggested next station:** `run-twitter-x-promotion-for-thought-leader-threads`
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: [Set up TikTok campaigns](https://local-service-spotlight.github.io/task-library/?task=set-up-tiktok-campaigns#task-set-up-tiktok-campaigns)
- 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/)
- [TikTok Ads Manager budgets](https://ads.tiktok.com/resources/help/article/budget?lang=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 TikTok budget screen, account eligibility, creative approval or campaign was tested.
- Current account currency and supported budget controls must be verified before a paid plan is accepted.