PlaysbyMoat8
Back to the library
The workflow guideMarketing

Test generated variants of an advertising hook

A creative team used organic-video research to develop alternative characters, scenes, and openings for paid ads, then compared the variants with campaign data. This adaptation uses permissioned references.

6 implementation stepsIntermediate

How this works

A creative team used organic-video research to develop alternative characters, scenes, and openings for paid ads, then compared the variants with campaign data. This adaptation uses permissioned references. This workflow tests the opening of an ad while holding its commercial message stable. It is useful when a team can produce several original scenes but needs evidence about which variation earns attention without misleading the audience.

Define one test variable, create a small set of permissioned original treatments, and attach every export to a variant identifier. Keep the body, offer, destination, audience, and measurement window consistent where practical. Treat observed performance as a bounded experiment rather than a universal creative rule.

Before you start

Approved creative foundation

Have a verified product message, usable footage, and permissioned references or original concepts.

Test plan

Agree primary outcome, secondary viewing metrics, budget, minimum observation window, and stopping conditions.

Production access

Use an available generator and editor, or deliver storyboards and assembly instructions when rendering is unavailable.

Prepare the inputs

hook_concept
Required

Creative brief

Describe the mechanism to test without copying a creator's distinctive scene or likeness.

fixed_body
Required

Approved assets and script

Preserve offer, claims, duration, and destination across variants.

variant_matrix
Required

Table

Specify the changing opening element and hold other factors stable.

test_rules
Required

Plan

Define allocation, spend bounds, attribution window, and decision criteria before launch.

optional_results
Optional / conditional

Campaign export

Include variant identifiers, exposure, spend, conversions, and maturation status.

Implementation, step by step

  1. Frame the hypothesis

    • State why a different opening might improve the defined outcome.
    • Choose a small number of variants and identify the exact scene, character, or framing difference.

    Checkpoint: The test has a single interpretable creative question.

  2. Design original treatments

    • Write a storyboard for each opening using permitted references as conceptual inspiration.
    • Avoid real-person imitation, unverified testimonials, and scenes that imply nonexistent product behavior.

    Checkpoint: Every variant is independently describable and rights-aware.

  3. Generate and assemble

    • Produce or storyboard the openings with the available tools.
    • Attach the same approved body and label each file with a stable variant ID.

    Checkpoint: Changes outside the intended opening are documented.

  4. Inspect exports

    • Review synthetic imagery, captions, product representation, sound, and the opening-to-body transition.
    • Reject visually broken or misleading variants before they consume test budget.

    Checkpoint: Each eligible file meets the same quality standard.

  5. Run the authorized test

    • Prepare campaign drafts or execute only an explicitly authorized bounded test.
    • Record allocation, dates, targeting, and delivery differences that could confound comparison.

    Checkpoint: The results can be joined to the exact tested files.

  6. Compare and decide

    • Compute viewing and acquisition metrics from source counts with compatible denominators.
    • Report uncertainty, immature conversions, and whether the planned decision rule was met.

    Checkpoint: The recommendation is continue, revise, or stop with a clear evidence basis.

Decisions along the way

A variant changes the offer as well as the opening

Separate it into another experiment or label the comparison confounded.

Viewing improves but qualified acquisition worsens

Do not call it a winner; examine the preselected business outcome.

Exposure is insufficient

Return inconclusive and extend only within authorized limits.

What you will produce

Variant package

Video files or storyboard folder

A controlled set of original creative treatments.

Include: variant_id · opening · body_version · asset_permissions · qa_status

Test readout

Table and note

A reproducible comparison tied to the actual exports.

Include: variant_id · exposure · spend · outcome · window · limitations · decision

Check the result

  • All compared files use the same approved product claims.
  • Conversion windows and exposure counts are comparable.
  • A generated character is not presented as a real customer testimonial.
  • The selected winner follows the agreed outcome rather than a convenient vanity metric.

When something goes wrong

Generation changes the product

Replace with approved footage or redraw the affected segment.

Campaign delivery is unbalanced

Report the imbalance and avoid claiming randomization.

Results cannot be matched to variants

Repair the mapping before drawing conclusions.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Test two openings for the same scheduling-product ad.

Inputs

Synthetic example. Variant A begins with a cluttered calendar; B begins with a missed handoff. Both use the same 15-second product body. A has 2,000 views and 20 signups; B has 2,000 views and 16, but qualified outcomes have not matured.

Expected result

Synthetic expected result. The readout reports observed signup rates of 1.0% and 0.8% and marks the qualified-acquisition decision pending. It does not declare a reliable winner from this small sample or change campaign budgets without authorization.

Run a small pilot

Start small

Two original hooks with one fixed body and a bounded authorized test.

Record the baseline

Record production time and the current opening's measured performance.

Agree success criteria

Track usable variants, mapping completeness, and the planned outcome after maturation.

Stop or revise

Stop on misleading imagery, broken measurement, or the authorized spend ceiling.

Keep the scope clear

  • Visual similarity or editing does not establish rights to reuse another creator's material.
  • Drafting or rendering creative does not authorize campaign launch or spend.

Check before using

Check permissions, product claims, and synthetic imagery before testing. Similarity or visual edits do not resolve rights automatically, and the source’s unlicensed reposting step is excluded.

Business activities

  • Create and publish content
  • Run advertising and acquisition tests

Editorially adapted workflow; not independently tested.

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: Permissioned reference concepts · Product message and approved footage · Campaign testing criteria

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗