Purchase vs ThruPlay Optimization

Purchase Optimization

Points Meta's delivery system at people predicted to complete a checkout, bidding for buyers rather than for clicks, sessions, or cart activity.

Meta needs a steady stream of purchase signals, from the pixel, the Conversions API, or both, to model who buys. It is the correct default for any store with real sales volume, since every shallower event is a proxy. The failure case is running it at a budget that cannot generate enough weekly purchases per ad set: delivery starves, the ad set never exits learning, and costs swing wildly.

ThruPlay Optimization

Buys video views that run to completion, or to at least fifteen seconds on longer cuts, instead of counting brief glances.

Meta charges on impressions but delivers toward users predicted to watch through, which filters out feed scrollers. It fits awareness, brand storytelling, and creative testing where watch depth is the signal you care about. The misread is treating ThruPlays as intent. A completed view costs little and predicts almost nothing about purchase, so never judge a conversion campaign by video metrics alone.

Use Purchase Optimization when

• Your business goal for this ad set is revenue and you have a functioning purchase event.
• You have enough weekly purchase volume per ad set to keep the algorithm out of a stalled learning phase.
• You want the reported result metric to translate directly into ROAS or cost per acquisition you can defend to finance.
• You are past the awareness stage and are running a bottom-of-funnel sales push.

Use ThruPlay Optimization when

• The goal of this campaign is brand awareness or message delivery, not a direct sale.
• You are testing which video creative holds attention before committing budget to it elsewhere.
• You have no purchase event, or volume too thin to sustain Purchase optimization, and want a video-native goal instead.
• You are building a video-view retargeting pool to use in a later, deeper campaign.