Promote promising ad tests into a scaling queue
Review experimental creatives against defined criteria and prepare approved candidates for main campaigns.
How this works
Review experimental creatives against defined criteria and prepare approved candidates for main campaigns. A creative that performs well in a test can fail when moved to a different audience or budget. Promotion should be an explicit handoff with eligibility evidence, destination constraints, and a way to distinguish the original test from the scaled deployment.
Evaluate creatives against pre-agreed maturity and performance criteria. Preserve the asset version and test context, then prepare approved candidates for destination campaigns. Use observed receipts to record transfers; a recommendation is not proof that an ad is running.
Before you start
Promotion rubric
Define minimum observations, quality criteria, and disqualifying conditions.
Destination settings
Specify campaign objective, audience, placement, and budget limits.
Asset identity
Use stable creative IDs and exact file versions.
Prepare the inputs
- test_results
- Required
Creative-level metrics
Include observation window and outcome maturity.
- promotion_rules
- Required
Versioned criteria
Separate continue-testing from scale-ready.
- asset_registry
- Required
Files and versions
Match results to the exact creative tested.
- destination_plan
- Required
Campaign settings
Check compatibility with the original test.
- approval_log
- Required
Owner decisions
Avoid duplicate promotion requests.
Implementation, step by step
Freeze eligible test results
- Select the agreed observation window and exclude incomplete outcomes.
- Retain small-sample candidates as pending rather than silently treating them as failures.
Checkpoint: A mature test-result set.
Apply promotion criteria
- Calculate required measures deterministically and record each criterion's outcome.
- Keep business-quality signals separate from click or view engagement.
Checkpoint: A rule-traced candidate queue.
Review transfer compatibility
- Compare destination audience, placement, objective, and format with the original test.
- Flag context changes that require another bounded test.
Checkpoint: A destination-fit assessment.
Prepare exact assets and settings
- Resolve the tested file version, copy, landing page, and naming convention.
- Create a draft transfer package with the proposed budget and owner.
Checkpoint: An inspectable promotion package.
Apply authorized promotions
- Use the configured platform only for approved changes, or hand off an import file.
- Record the destination ad ID and actual receipt rather than assuming creation succeeded.
Checkpoint: A confirmed or pending transfer record.
Monitor the promoted cohort
- Compare mature destination results with the test hypothesis and agreed stop rules.
- Keep test and production performance separate to avoid circular winner selection.
Checkpoint: A post-promotion review.
Decisions along the way
Engagement is strong but qualified outcomes are weak
Continue investigation rather than promote based on clicks alone.
The destination audience differs materially
Treat transfer as a new bounded test.
Asset version cannot be matched
Hold promotion until the tested version is identified.
What you will produce
creative-promotion-queue.csv
CSVSupports reviewed scaling.
Include: creative_id · version · eligibility · evidence · destination · decision · status
promotion-receipts.json
JSONLinks the transfer to later results.
Include: test_id · destination_ad_id · settings · receipt · review_date
Check the result
- Match metric rows to exact asset versions.
- Recalculate promotion criteria and sample eligibility.
- Verify destination budgets and placements.
- Confirm no creative is counted as promoted without a receipt.
When something goes wrong
Metrics join to the wrong variant
Repair the asset mapping and rerun eligibility.
Transfer creates duplicate drafts
Inspect existing destination IDs and keep one approved instance.
Performance drops after promotion
Apply the agreed review rule and investigate context differences.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Select creatives to move from testing into the main campaign.
Inputs
Synthetic example. Synthetic V1 has 8 mature qualified leads and meets the rule requiring 5; V2 has many clicks but only 1 mature lead.
Expected result
Synthetic expected result. V1 enters the promotion review queue. V2 remains in testing or review; click volume alone does not make it scale-ready.
Run a small pilot
Start small
A few promotions with known asset IDs and comparable destinations.
Record the baseline
Record transfer effort, mapping errors, and later qualification outcomes.
Agree success criteria
Agree acceptable promotion precision and context-change handling.
Stop or revise
Stop transfers when asset identity or destination limits are unresolved.
Keep the scope clear
- The queue prepares decisions; only established authorization permits account changes.
- Do not describe an experimental winner as universally effective.
Check before using
Check sample size, attribution delays, audience differences, and spending caps before changes.
Business activities
- Run advertising and acquisition tests
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Experimental campaign results · Creative identifiers and tags · Promotion and stop criteria
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow