Facebook and Instagram Ads for Online Stores — Meta Ads, Catalogue and Dynamic Retargeting

For an online store in 2026, Meta ads — advertising on Facebook and Instagram — are purely a channel that drives traffic to your own website; the transaction finishes somewhere else. In-app checkout inside Meta's apps has been discontinued globally, and Poland is not on Meta's list of countries that support Shops. What remains, and what actually works, is the mechanism Meta documents clearly: the product catalogue in Commerce Manager, Advantage+ shopping campaigns, dynamic retargeting as an ad format, and the Pixel together with Conversions API as the data source behind measurement. Each of these is described here from Meta's own documentation.

Shops on Facebook and Instagram — the 2026 picture

Before planning a campaign, it is worth settling a question that comes up at every audit: can a merchant sell directly on Facebook or Instagram, inside the apps, without sending the buyer to their own website? According to Meta's own documentation, the answer depends on the country — in Poland it is a plain no, and even where Shops is available, it still is not a direct answer.

Meta's list of supported countries for Shops has three tiers (read 2 October 2026). The full Shops and Shops ads experience is available only in the United States. An open beta "for the full Shops and Shops ads experience", in which "some sellers may not have full capabilities", covers among others Canada, Brazil, Mexico, the United Kingdom, Norway, Switzerland, Australia, Japan and Singapore — and seven EU member states: Denmark, France, Germany, Italy, the Netherlands, Spain and Sweden. A third tier with limited Shops functionality, where sellers cannot run Shops ads, currently holds only Ukraine and Indonesia. Poland is not named on any of the three tiers, and Meta determines a shop's country by the location of the commerce account behind it — so a Polish commerce account has no Shops, and "Shops in the EU" does not have one single answer.

The second change applies regardless of country or tier. According to Meta's page on changes to Shops and payments, since September 2025 "Shops on Facebook and Instagram now use website checkout", and "payment processing has been discontinued for Shops. You can no longer conduct transactions in your Shops on Facebook and Instagram." In other words: even where Shops is formally available, and in whichever tier, a purchase still finishes on the merchant's own website, not inside the app.

The same country-list page signals this directly with a banner at the top: "Some features related to Shops and checkout on Facebook and Instagram are no longer supported." For a store in Poland, this means one thing: a Facebook or Instagram profile makes sense as an organic channel and a touchpoint with customers, not as a stand-alone sales channel. How to run that kind of profile is covered separately in our article on an organic social-media profile; here we stay with paid advertising that drives traffic to your own website.

Commerce Manager and the product catalogue

Commerce Manager is the central place in Meta's panel where you manage the product catalogue later used by ads. The Commerce Manager page describes its scope: managing product catalogues, configuring Shops on Facebook and Instagram, reviewing sales activity, and — for eligible businesses — enabling checkout, which, as above, has redirected to the merchant's own website for every market since September 2025 regardless. From an advertising perspective, what matters is the catalogue itself: it is what feeds campaigns with product data.

The mechanism is simple: the catalogue holds images, names, prices and availability, and Meta automatically uses that data to build and refresh ads without manually creating every creative by hand. Meta's developer documentation for dynamic ads puts it directly: you create a feed from your catalogue that automatically supplies images, descriptions and prices in your ads. It is the same mechanism Google Ads calls a product feed in Merchant Center — the platform differs, not the underlying principle. If you already maintain a clean product feed for Google, moving it into Meta's catalogue is, in practice, repeating work you have already done, not starting from zero.

The catalogue is not itself an ad format — it is the input for two formats covered later in this article: Advantage+ shopping campaigns, which choose on their own which product from the catalogue to show to which person, and dynamic retargeting, which builds an ad from the same catalogue tailored to one specific person based on what they have already viewed. Without a well-maintained catalogue — current prices, availability and images — neither format has anything to build an ad from, no matter how large the budget behind it.

Advantage+ shopping campaigns: automated advertising on Facebook and Instagram

Advantage+ shopping is Meta's automated sales-campaign product. Its product page describes it as an "automated campaign setup" that "uses AI to optimise your targeting, creative, placements and budgets in real time to help drive sales." Meta's system tests and delivers the highest-performing creative across all the advertiser's preferred placements itself, serving each customer the ad they are most likely to engage with.

In practice, this means four decisions — who sees the ad, in which placement, with which creative, and how the budget is split — are optimised automatically and in real time by Meta's system, rather than resting solely on settings entered by hand by the advertiser. The quality of that optimisation depends on the data it receives: the product catalogue, and events from the Pixel and Conversions API, both covered below. Your job shifts from setting targeting by hand to looking after the quality of that data.

Cost is a separate matter. Meta's page on ad costs does not publish a price list — it states that many factors contribute to a campaign's cost, including ad quality, bidding strategy, performance goal, budget type and campaign objective — and ads reach people through an auction. The advertiser sets their own budget: daily (an average amount spent each day) or lifetime (an amount for the whole run), at campaign or ad-set level.

Dynamic retargeting — how catalogue-based Facebook and Instagram ads work

Dynamic retargeting is an ad format that automatically shows a user specific products from your catalogue, chosen based on what that person has already done on your website or app — for example, which products they viewed. The mechanism pulls the creative straight from the product catalogue and targets it using purchase-intent signals collected on the site and in the app, matching a product to a specific person instead of showing one generic ad to everyone.

The format combines the two data sources described in this article. The catalogue supplies the creative: image, name, price and availability. The Pixel and Conversions API supply the signal: who viewed what on the site. If either fails — an out-of-date price in the catalogue, or events not arriving from the site — dynamic retargeting will either show an offer that no longer exists or not know whom to show it to.

One naming inconsistency on Meta's own pages is worth knowing. The same catalogue-based mechanism appears under two different names at once. Meta's marketing page calls it "dynamic ads," running on Facebook, Instagram and Audience Network. The developer documentation for the same catalogue mechanism uses the name "Advantage+ catalog ads" and describes it as a way to promote the right products from your whole catalogue on every device. Neither page points to the other as a new or old name — so this is treated as two names Meta uses in parallel for the same product, not a confirmed, dated rename. Materials and conversations with an agency may use either name — that is not an error, simply the absence of one consistent name at Meta itself.

Pixel and Conversions API — measurement behind Meta ads

Everything described above — Advantage+ shopping, dynamic retargeting, real-time optimisation — only works as well as the conversion data Meta receives. Two measurement tools sit behind that.

Meta Pixel is a piece of JavaScript code installed on a store's website. The developer documentation defines it as a piece of JavaScript code that lets you track visitor activity on your website. It collects HTTP headers, pixel-specific data and button-click information; form-field values are captured only if you include them through Advanced Matching or as optional values. Pixel data is used to measure ad performance in Ads Manager, build audiences, and feed dynamic retargeting itself.

Conversions API (CAPI) is a second path for the same data — sent not from the customer's browser, but from the store's server, CRM or app. Meta's documentation describes it as a way to connect an advertiser's marketing data — from a server, a store platform, a mobile app or a CRM — to Meta's systems, which optimise ad targeting, lower the cost per result and measure outcomes. Events sent through CAPI can be used for measurement, reporting and optimisation in the same way as events from the Meta Pixel or mobile SDKs. Conversions API best practices explicitly recommend using CAPI alongside the Pixel and sending the same events through both ("redundant event setup"), because CAPI can deliver events from the site that the Pixel may lose to connection problems or page-load errors. So that the same event is not counted twice, both events need an identical name plus either a matching event_id or a combination of external_id and fbp — Meta then deduplicates them.

In practice, the Pixel and CAPI are not alternatives to each other — Meta recommends them together, as two paths for the same events, with the server-side one filling in what the browser loses. If your store does not yet have GA4, server-side Google Tag Manager, and Meta Pixel together with Conversions API set up, it is worth putting that in order before increasing campaign budgets — we handle that measurement setup ourselves, while campaigns on Google and Meta are coordinated with a partner advertising agency; see our online marketing and branding offer.

The EU: the subscription for no ads and less personalised ads

One more change matters to an EU advertiser, because it affects how many people see a personalised ad on Facebook and Instagram at all. On 30 October 2023, Meta announced a paid "subscription for no ads" for users in the EU, EEA and Switzerland, Poland included, available from November 2023 at €9.99 a month on the web, or €12.99 a month on iOS and Android. On 12 November 2024, Meta announced a change: the price was cut by 40%, from €9.99 to €5.99 a month on the web (from €12.99 to €7.99 on iOS/Android), from the following day, 13 November 2024. Explaining the model, Meta pointed to moving to the GDPR legal basis of "consent" — in the context of GDPR's interpretation after a ruling of the Court of Justice of the EU and the entry into force of the Digital Markets Act — stating that the CJEU had found the subscription model a valid form of consent for an ads-funded service.

The surcharge for each additional account under the same subscription changed too: from 1 March 2024 it was €6 a month on the web and €8 on iOS/Android, falling after the November 2024 cut to €4 on the web and €5 on iOS/Android. Meta's announcement states all these prices in euros.

In the same announcement, Meta said it would roll out, over the following weeks, a free option for people who do not want to pay for no ads but also do not want fully personalised advertising: "less personalised ads." This option relies on less data — ads are selected based on context (what a person is viewing in that session on Facebook and Instagram) and a minimal data set, including age, location, gender, and how that person interacts with ads. In this variant, Meta also introduces ad breaks, where some ads cannot be skipped for a few seconds.

For a store running EU campaigns, the consequence is mechanical, not a matter of numbers: some users who choose the paid no-ads option will not see your ad at all, and some choosing the free, less-personalised option will see it matched less closely to their behaviour, because Meta has fewer signals about them to feed dynamic retargeting. Meta did not state, in the announcement, what share of users chose which option.

Consent and measurement

The Pixel and Conversions API are tools for transmitting personal data — per the Pixel's own documentation, among other things an IP address from HTTP headers, a Facebook cookie, and on-site behaviour — so using them for advertising purposes requires user consent, collected through a cookie banner, before the tag starts sending data. The legal basis for that processing is consent under Article 6(1)(a) GDPR, not any default "marketing consent" written into a store's terms — and, as described above, Meta itself based personalised advertising in the EU on "consent." In Poland the data protection authority is the President of the Personal Data Protection Office (Urząd Ochrony Danych Osobowych, UODO).

The mechanics of consent mode in Google's tags — what happens to tags when a user does not consent, and how that affects reporting — are covered separately in our article on consent mode. Meta's Pixel is not part of Google's consent mode, so before increasing your Facebook ad budget, check separately whether your site's cookie banner actually holds the Pixel back until consent is given.

The consequence for the formats described above is mechanical: if a large share of traffic does not give consent, Advantage+ shopping and dynamic retargeting get a weaker signal to optimise on — not only reporting accuracy, but the algorithm's own choice of audience and creative loses precision, because part of the Pixel's events simply never arrive. CAPI, sent from the store's server, does not fix this automatically — it changes the technical path the data takes, not the GDPR obligations, so server-side events need the same legal basis as Pixel events.

In the EU, then, the signal behind a campaign weakens at three levels at once. People with the paid no-ads subscription will not see your ad at all. People who chose less personalised ads will see it selected mainly by context and a minimal data set. And visitors to your site who have not consented will not send the events Meta builds dynamic retargeting from. You have no influence over the first two. The third at least depends on you: whether your consent banner and measurement work correctly. A conversion that started with a Meta ad can also surface later as a branded search or a direct visit, so platform reports rarely agree with each other — how to read those gaps is covered in our article on performance marketing.