What Meta reads

DPA performance is catalog performance.

Advantage+ decides which products to show whom from the attributes in your catalog. Thin data narrows the matching. Broken variants split it. The campaign optimizes whatever the catalog allows - no more.

Meta-spec catalog

Titles, identifiers, categories and imagery formatted to the Commerce Manager spec.

Attribute completeness

Category, gender, age group, color and material fields populated by rule, so matching has range.

Variant clarity

Item groups keep product families organized, so the right variant renders in the ad.

Current price and stock

Scheduled updates keep ads and shops aligned with your store.

How it works

Live on Meta in three steps.

01

Connect your store

Your full catalog imports automatically - products, variants, imagery, inventory.

02

Map to Meta's spec

A maintained template covers Commerce Manager requirements; your rules tune the rest.

03

Sync and monitor

Pushes run on schedule with feed health visible in one dashboard.

1

catalog behind Facebook, Instagram and every Meta surface.

40+

channels one connection can feed.

0

catalog rejections from fields a rule could fill.

Questions, answered

Meta catalog questions.

What does Commerce Manager require?

Structured products with identifiers, imagery, price, availability and category attributes - validated against the spec before every sync.

Why do products get rejected?

Missing required fields, policy mismatches and broken variant groups. Pre-push validation catches them before Meta does.

How fresh is price and stock?

As fresh as your schedule. Both can refresh more often than the full catalog.

Other AI agents

Be readable everywhere shoppers ask.

No items found.

Make your catalog the answer

Light closer. Renders for AI agent type only, which spends its dark beat on the hero.

Start freeTalk to us