Meta product-data versions let eligible accounts vary catalogue content

What changed

Alternative images, titles and other fields can support different presentations while missing fields fall back to the default. Availability is limited; verify what your catalogue exposes before designing a testing workflow around it.

The account example separates product identity from presentation. Multiple data versions can retain the same product IDs while using different images, titles or other supported fields. Selecting a version at ad level offers a way to vary the product presentation without treating every variation as a separate underlying product.

Adria Ureña’s screenshot shows support for up to ten versions. Missing fields fall back to the default product data, which makes the default catalogue an important part of the review. An alternative title or image does not mean every field has been replaced, and an incomplete version may produce a mixture of alternative and default values.

Before building a test, inspect which fields the account actually supports and preview the resulting ads. Check the selected version, product IDs, destination and any fallback content together. Keep the factual product information consistent with the landing page and the offer a customer can buy.

Availability remains limited. The observation does not establish that every catalogue has the workflow or that it is suitable for every localisation or creative-testing plan. Where available, define the learning question before creating versions and compare outcomes under an appropriate campaign setup. More versions alone do not demonstrate better performance, and catalogue edits should remain traceable to the person responsible for product information.