How a performance team deployed creative across Meta, TikTok and Snapchat from one upload

An illustrative scenario — a composite of cross-platform creative refresh workflows, with realistic numbers.

The setup

A performance team refreshing creative every two weeks across Meta, TikTok and Snapchat: typically 6 concepts × 2–3 ratios × 2 languages ≈ 30 assets, each needing the right ad sets/ad squads and the right copy variant. The manual version took an afternoon per refresh, and the test readouts were noisy — twice in one quarter a copy variant shipped paired with the wrong video, corrupting the comparison the refresh existed to run.

What was set up

• The naming convention, enforced — {MARKET}_{Concept}_{Ratio}_{Version} (e.g. US_UGC_Hook3_9x16_v2.mp4), parsed automatically
• The destination map — concepts → designated campaigns/ad sets/ad squads per market, stored once
• Validation — ratio/duration/size per destination platform; missing-variant flags (a 9:16 without its required 1:1); language-to-market matching
• Copy pairing — primary text, headline, CTA per concept per language from the copy doc
• The ritual — one preview listing all ~30 ads with destinations and copy; approve; created paused; rejections (one oversized Snap video) reported per ad

The numbers

What changed operationally

Refresh cadence stopped being gated by deployment capacity — the team moved from biweekly to weekly creative tests with the same headcount. Test readouts cleaned up: when routing and pairing are rule-enforced, week-over-week comparisons compare creatives, not deployment accidents.

What stayed human

Concept selection, the copy itself, the read on what's fatiguing — and the approval on every preview.