Skip to content
Ecomwith

Cross-Platform UGC: Preserve the Promise and Proof

  • Intermediate
  • 34 minutes
  • Pro

One cross-platform user-generated-content (UGC) test keeps the same buyer doubt, promise, proof, product, offer, page facts, and rights scope. Each destination gets a version shaped for how people watch and act there. Compare it with a same-platform baseline: click-through rate (CTR) relates the selected click event to its impression denominator; cost per acquisition (CPA) relates spend to attributed acquisitions; return on ad spend (ROAS) compares attributed revenue with ad spend. Those measures answer different questions, and their association with a creative change does not prove causation.

The buyer doubt an asset answers is its angle. A hook gives the viewer a reason to keep watching in the first 1-3 seconds. A cut is one specific edit of a script or master. Check the creator's commercial relationship and the reuse scope separately.

Google Ads' Performance Max (PMax) combines text, image, and video assets in an asset group. A campaign-level result describes combined delivery; it does not identify which one UGC asset produced it.

Continues from: Creative Fatigue: Refresh, Reuse, or Reshoot

Carry the fatigue-reuse boundary into platform rewrites

If you have just done a fatigue review, carry its conclusion: separate light refresh, reuse, pause protection, or reshoot, and keep the angle, proof, comments, post ID, and rights that still hold. In platform rewrites, keep the same leak-proof promise and proof, and rewrite only the opening, captions, CTA, safe zone, and page support. If TikTok works and Meta weakens, inspect the cut and platform support before rejecting the angle.

Keep one promise and proof

A Platform Rewrite Record starts with the same angle, main promise, proof, product or stock keeping unit (SKU, the inventory code for a product or variant), offer, product detail page (PDP), product-feed facts, and rights scope. It then records the opening, proof order, captions and call to action (CTA, the next-step prompt or button), safe-zone layout, asset ID, date window, and platform-specific acceptance signal.

Use one pet travel bottle example throughout: the buyer worries it will leak in a car. The promise is leak-proof travel use. The demonstration is an inversion test and a shake in the car cup holder. The product facts, offer, and product page stay fixed while the expression changes.

Keep these three pieces fixed:

PreserveWhy it stays fixedGuardrail
The same buyer doubtOtherwise a review cannot separate platform fit from a new angle.Do not change the offer, page, and main promise together.
The same proof logicA stable evidence chain lets you compare opening and pacing.Reorder a demonstration or review when needed, but do not swap it for a different benefit.
The same rights boundaryPlatform, region, paid use, term, and editing scope must be known before work starts.If the scope is unclear, hold cross-platform paid use.
Self-check · 1 question0/1 answered

Which version is adapted?

A TikTok bottle winner is moving to Meta. Which choice tests platform adaptation?

Self-check not answered

Pro · Parts 2-12 · 11 parts

Complete the platform rewrite

Inspect each platform version, check the handoff fields and stop lines, then save a blank learner-owned rewrite record.

This part includes

  • Keep the same promise and proof across platforms with a rewrite matrix
  • Check opening, rights, safe zone, and page support for each platform
  • Save a blank cross-platform rewrite record

Pro $20 / monthYearly $16 / month

Choose a plan, sign in with your email or Google account, and complete payment. You'll have instant access to all member benefits.

  • Unlock every premium lesson
  • Advanced tools and member resources
  • Member-requested courses and ongoing updates
  • Pro community and priority support

Checking your membership…

See the Pro plan
What's the difference between monthly and yearly?

Yearly plans save you 20% with annual payment. Monthly plans offer more flexibility for short-term needs.

What you finished

No checkpoint finished in this lesson yet. Start with “Go to the exercise”.

Self-check not answered

FAQ

Cross-platform UGC questions

Does adaptation mean cropping one video into several sizes?

No. Keep the same promise and proof first, then rewrite the opening, proof order, caption density, CTA, and safe zone for each platform, and write its acceptance signal.

What if TikTok is strong and Meta is weak?

Do not blame the angle yet. Compare each version with its own platform task and baseline, then check the opening, page, product feed, rights, and offer.

If a creator video can be edited, can it be used in ads, on the product page, and in email?

Not from editability alone. Editing permission, paid-media rights, product-page use, and email use are separate grants with their own scope and expiry. Check the current contract and platform terms, then record who approved which use and until when; a file you can edit is not a file you may broadcast.

Related lessons

Sources

The Meta and FTC guidance cited here was checked on 2026-10-03; TikTok format and Google multi-format guidance were checked on 2026-07-23. Platform guidance sets boundaries to check at launch. It cannot choose the promise, prove page support, clear rights, or attribute a result to one asset.

Next lesson · 8 of 8

You take away: 1 self-check question

Edition notes

  • Author Ranfeng Wei
  • Published
  • Updated
  • Reviewed
  • Next review

This update: Completes the bilingual explanations, handoff tables, and platform boundaries for cross-platform UGC; preserves each platform's example output and a blank rewrite record, with clear limits on metric, rights, and scaling decisions.