Applying your Segment Prioritisation strategy
Save your SP strategy.
In the "Apply the strategy" section, select the virtual account that contains the Ad set you want to apply your SP strategy to.
You'll be automatically redirected to the Campaign Insights.
Tick the checkbox next to the selected Ad set.
At the top menu, click Edit, then choose Segment Prioritisation from the dropdown.
Switch Segment Prioritisation ON and pick your saved strategy.
Review the settings and click Apply.
ℹ️ Note: After applying, you can go to Campaign Insights and check the Product prioritisation column (at the ad set level) to confirm where SP is active and which strategy is applied.
If the column is not visible, click Customize view in the right menu, go to Meta → Special → Segment Prioritisation, and click Apply.
Applying your strategy to ad sets with multiple catalogs
Each Segment Prioritisation strategy is created for a specific catalog.
If an ad set includes ads linked to multiple catalogs, multiple strategies may be used within that ad set. However, each strategy applies only to the catalog it was created for.
More details are explained below. ⬇️
Step by step: How it works
When applying a strategy to an ad set that contains ads linked to multiple catalogs, the apply flow stays the same as for any other ad set.
The difference comes when you are about to select your SP strategy. 👇
At this point, one of two things can happen:
🔗 Scenario 1: Two strategies are applied
Some SP strategies are linked and will be selected together (full ad set is covered). Each Segment Prioritisation strategy is applied only to the catalog it was created for and neither takes priority over the other.
Example:
Your ad set contains ads from Catalog A and Catalog B.
You select a strategy created for Catalog A and a linked strategy is also available for Catalog B.
In this case, both strategies are selected and applied - one to Catalog A and the other to Catalog B.
How are strategies linked?
Strategies created for different catalogs are automatically linked when they are assigned to the same catalog field.
When you select a strategy for a multi-catalog ad set, any linked strategy is selected automatically as well. This linking cannot be adjusted manually.
📍 Scenario 2: Only one strategy is applied
If none of your SP strategies are linked, you can select only one strategy. That strategy will apply only to ads from its matching catalog. Ads linked to other catalogs will continue running without Segment Prioritisation and will not be affected.
Example:
Your ad set contains ads from Catalog A and Catalog B.
You select a strategy created for Catalog A but there is no linked strategy available for Catalog B.
In this case, Segment Prioritisation is applied only to ads from Catalog A. Ads from Catalog B continue running without Segment Prioritisation.
Example use cases
🏷️ Different brands in one ad set
You use one ad set, but the ads inside it are linked to different brand catalogs. Segment Prioritisation lets you apply the right strategy to each catalog without splitting the ad set.
🍂 Seasonal vs. evergreen catalogs
One catalog contains seasonal products, while another contains evergreen items. You can keep them in one ad set and still apply different Segment Prioritisation strategies.
🧩 Simpler campaign structure
Instead of creating multiple separate ad sets for different catalogs, you can keep the setup simpler and manage Segment Prioritisation within one ad set.
FAQ
Why can’t I apply SP to my ad set (or why do I get an error)?
Why can’t I apply SP to my ad set (or why do I get an error)?
SP works only in manual sales campaigns where:
The catalog is selected on the campaign level
The product set is selected on the ad set level
(SP cannot be applied in campaigns where the product set is selected on the ad level, such as ASC or campaigns with an app objective.)
❌ Not supported:
ASC campaigns
Campaigns with an app objective
✅ Supported:
Manual sales campaigns where the product set is chosen on the ad set level
📅 Coming soon:
Meta plans to enable SP for ASC and app campaigns in H1 2026.