Meta Ads Formats and Placements: A Readiness Test

For the surrounding account decisions, compare Meta Ads Audiences: Broad vs Narrow Targeting and use Meta Ads Creative Hooks: A Controlled Test as the next diagnostic.

In short

This guide owns one decision artifact: the filled, auditable structure below. Reader-supplied thresholds stay explicit; missing evidence stays missing.

Placement-readiness checklist

Copy the current requirements shown for each selected placement at build time; Meta specifications can change. Re-check the primary Meta Ads Guide before export; accessed 2026-08-27.

Target placement	Ratio / resolution	Safe zones	Duration	Captions/audio	Ready / not-ready rule
Feed	Record the exact current feed ratio and minimum resolution from Ads Guide	Keep claim, product, price, and CTA inside the preview-safe crop	Record the current accepted duration for the chosen format	Captions carry meaning when sound is off	Ready only after every selected feed preview preserves content and evidence
Stories	Record the current vertical requirement	Verify UI overlays do not cover claim, proof, or CTA	Record current maximum for the selected story asset	Burned-in or uploaded captions match speech	Not ready if a feed crop is merely stretched or critical content is obscured
Reels	Record the current Reels ratio and resolution	Inspect top/bottom/side overlays in the live preview	Record current Reels duration requirement	Audio rights documented; captions synchronized	Ready after vertical-native preview, rights, and caption checks pass
Right column, if selected	Record the exact desktop requirement	Product and claim remain legible at rendered size	Use the accepted static/video constraint shown at build	Message cannot depend on audio	Not ready if legibility or destination continuity fails

Readiness rate = placements passing every declared asset requirement ÷ selected target placements. This release-control metric is not an economic outcome and must not choose a winning placement.

Interpretation boundary

Use the placement asset release checklist only for its stated decision. Record current ratio, resolution, safe-zone, duration, caption, audio-rights, and live-preview requirements for every selected placement. An asset is not ready when critical evidence or CTA is cropped, speech lacks accessible captions, or a feed crop is stretched into vertical. Reader-supplied thresholds remain inputs, not universal standards.

Where implementation depends on Meta behavior, re-check Meta’s current Business Tools Terms and linked product documentation before release; accessed 2026-08-27. The tables below are operator contracts unless a primary Meta source is linked.

Can software help?

Bach.ai audits your connected Meta account against 100+ checks, ranks what it finds by estimated impact, and proposes specific fixes. It stays read-only until you approve a change, then executes the approved change on Meta; connected Google Ads data is used for intelligence only. Think of it as an automated audit layer that surfaces issues and proposed fixes for your review — not a replacement for your team’s judgment, and it does not generate your creative.

FAQ

What should you check before releasing an asset across Meta placements?

Record current ratio, resolution, safe-zone, duration, caption, audio-rights, and live-preview requirements for every selected placement.

Which asset problems mean a placement is not ready?

An asset is not ready when critical evidence or CTA is cropped, speech lacks accessible captions, or a feed crop is stretched into vertical.

Does placement readiness prove that an asset will perform better?

It compares the declared cells in the placement asset release checklist. A causal interpretation additionally depends on valid assignment, stable invariants, adequate power, and contamination within the preregistered limit.