Optimize Product Ranking in Meta Carousel Ads with product_priority Attributes

Understanding the product_priority attribute in Meta Catalogs #

Meta provides a set of optional catalog fields - product_priority_0 through product_priority_4 - that allow advertisers to directly influence how products appear in carousel ads. Instead of leaving the product order entirely to Meta’s optimization algorithms, these attributes give you a practical and predictable way to nudge specific products toward more or less visibility.

Each field accepts a floating-point value ranging from 0.7 to 1.3, where 1 is the neutral baseline. Higher numbers increase the likelihood of a product being shown, while lower numbers reduce its chances. If a value is not provided, Meta treats it as 1.

This mechanism does not override Meta’s machine-learning based delivery, but it does provide a scalable and controlled signal similar to weighting. You can use it to highlight key items, support new launches, or push seasonal inventory that matters most to your campaign.

How the Priority Fields Work #

• Range: 0.7 - 1.3
• Neutral value: 1
• Higher number: Increases the chance the product appears in carousel ads
• Lower number: Decreases visibility within the carousel

Each priority index - product_priority_0 to product_priority_4 - behaves independently. In Meta Ads Manager, you can choose which one to apply at the ad set level. This allows you to run controlled experiments, create campaign-specific strategies, or test multiple product weighting configurations without rewriting your catalog.

Example use cases #

• Promote new arrivals or bestsellers by assigning 1.15 to 1.25
• Reduce emphasis on overrepresented SKUs by assigning 0.85 to 0.9
• Use different priority sets across campaigns to evaluate performance

Flexify Support for product_priority_0–4 #

Flexify fully supports mapping catalog metafields to these priority attributes. Through Metafields mapping rules, you can automatically populate product_priority_0–4 based on your product data, tags, metafields, availability, or internal scoring system.

This means you don’t need to manually edit hundreds or thousands of items. Instead, you define a rule once, and Flexify keeps your priorities synchronized across your catalog.

For more details on metafield mapping, see our article:

Automatically set Catalog Fields

Best Practices #

• Start with a single priority field, such as product_priority_0, and validate its impact before scaling.
• Use modest adjustments first - Meta is more responsive to incremental signals.
• Avoid setting extreme values across the entire catalog. Keep high-priority adjustments narrow and purposeful.
• When running A/B tests, assign different priority fields to different ad sets to get clean results.