Name UGC Variants Clearly: Use stable IDs for hooks, proof and CTA in UGC variants; Record each export with a unique ID, not overwriting files; Check ACCC compliance when claiming product fit or performance
Image: UGC Brand Guide

Editing and Placements

Naming UGC variants by hook, proof and call to action

Use a hook, proof and call-to-action naming pattern while keeping exact UGC exports and test results traceable.

Name a UGC variant for what viewers see: opening hook, supporting proof and call to action. Give it a stable ID. The readable name helps colleagues recognise the idea; the ID keeps its record intact if the label changes.

Name the creative combination

The hook label describes the opening approach, such as a fit question or an immediate product action. The proof label describes the shot or sequence supporting the message. The call-to-action label describes what viewers are asked to do. Labels such as “strong”, “authentic” and “final” do not reveal which scenes changed.

Define short labels in a shared list. One possible pattern is concept ID / hook / proof / CTA / variant ID. For an imaginary bag demonstration:

Field / Illustrative value

Concept ID
BAG-SETUP-04
Hook
Q-LAPTOP-FIT
Proof
PACK-ONE-MODEL
CTA
VIEW-DETAILS
Variant ID
V03

This is a naming example, not a tested asset. “PACK-ONE-MODEL” describes one filmed demonstration; it does not claim every laptop fits. For a real product, check the filmed model and any stated fit. The ACCC can require businesses to back up claims about their products or services, and may take compliance or enforcement action if a business misleads.

UGC Variant Naming: Hook, Proof and Call to Action

Hook
Describes the opening approach (e.g., fit question or immediate product action)
Proof
Describes the supporting shot or sequence (e.g., filmed demonstration of product use)
Call to Action (CTA)
Describes what viewers are asked to do (e.g., view details, shop now)

Give each finished file its own ID

Use the variant ID for the creative combination and a separate export ID for each finished file reviewed or uploaded. A captioned vertical cut and a wider cut may share a hook, proof and CTA, but they are different exports. Record each export’s source edit, product variant and approval.

Do not overwrite a file called V03-final.mp4 with a changed version. If a proof scene changes substantially, decide under the team’s naming rule whether it creates a new variant. A spelling correction still creates a new export, with the correction recorded. The boundary between variant and export is a team convention; document it so others apply it consistently.

Read the names before reading the result

Compare the proposed test rows before launch. If both hook and proof differ, the result cannot isolate the hook. TikTok lists initial hooks among creative assets available as split-test variables and permits one selected variable per split test, subject to campaign compatibility. A naming scheme does not itself make a comparison controlled.

Keep platform ad IDs, exact export IDs and run dates beside the names. Record the result against the file that served, rather than a loose label such as “bag video”.

More from Editing and Placements

Asset Library

Building a record of what each creative test changed

Create a UGC test register that captures exact file changes, campaign conditions, delivery, results and the next decision.