Skip to main content

Run a UGC batch

Updated October 10, 2026

A batch turns one product into many UGC-style ad variations. Every combination of hook × script × talent × call to action becomes a row. You prune the rows, set a cost cap, and the batch runs in two stages: cheap preview images first, then videos only for the rows you approve.

Build the batch

  1. On the product page, select Continue to hooks. The batch opens with its steps: Hooks, Scripts, Talent, Matrix & cap, Run, Compare, Approve & schedule.
  2. Hooks. Select Propose 5 hooks ✦. The estimate is shown next to the button. Tick the hooks to test, then Continue to scripts. A hook marked "Blocked by a compliance rule: it can’t be selected." stays unavailable.
  3. Scripts. Choose how many scripts per hook and select Generate scripts ✦. Each script shows Ready, Claims need review or Blocked. Select Continue to talent.
  4. Talent. Pick your personas and/or Stock AI actors. Each persona shows Disclosure OK or Disclosure missing. Only actors whose licence allows commercial use can be selected. Select Continue to the matrix.
  5. Matrix & cap. Add at least one call to action, apply the Prune by rule options or untick rows by hand, then select Preview matrix.
  6. Enter the Cost cap (credits). The Staged plan and cost card shows the upper bound and how many videos the cap covers.
  7. Select Review and launch, check the summary, then Launch the previews.

Run the stages

  1. Stage 1 makes a preview image for every kept row. Each row runs on its own; a failed row doesn't stop the others.
  2. When every preview has finished, tick the good ones with Approve for video and select Make videos. The cap is checked first.
  3. Follow progress and the budget meter on the Run step. Cancel remaining work stops queued rows and releases their credits.

What it costs

Hooks, scripts, previews and videos are paid. You see an estimate before each one; on confirm, up to that amount is reserved, only the actual cost is charged and the rest is released. Failed and canceled rows release their credits. The cost cap is a hard limit: used and committed credits never pass it. See How credits work.

What can block you

  • Permissions. Building a batch needs a role that can create content; launching paid steps needs a role that can spend credits (Owner, Admin or Creator / Editor).
  • Cap too low. "Over the cap — launch refused": raise the cap or prune rows. Nothing is reserved.
  • After launch, the matrix and cap are locked ("Matrix locked").

Messages you may see

  • "The estimate changed since you previewed it. Review the new numbers and launch again."
  • "Too many rows: keep at most … before launching."
  • "One of the actors isn’t licensed for commercial use. Remove it and try again."
  • "The provider’s content policy refused this row. Edit the script or drop the row."
  • "This row already reached the provider, so it isn’t sent again (a paid call is never sent twice). Prune it or launch a new batch."

More in UGC and products