Meta Built Your Ad. Your Best Selling Point Stayed in a Paragraph.

In this article: the part of Interpretability Engine Optimization (IEO) that takes what you've already written and declares it where a machine expects it. No new facts, no new copy. Its job is to notice that "hand-knit from 100% merino wool" names a material, and to put that material in the field an ad system reads as material.

Here is what happens without it.

A home store sells a throw blanket. The product page says:

Our Chunky Throw is hand-knit from 100% merino wool in a soft cream. Generous 50 × 60 in. Spot clean or hand wash cold.

Meta's Advantage+ catalog ads take that catalog and do the rest. They choose which products to show, to whom, and assemble the ad for each person. Picture Meta deciding whether this blanket belongs in front of someone who has been browsing wool home goods, or someone furnishing a cream-and-neutral living room.

In the catalog it received, the product is called "Chunky Throw", and the description is there in full. Material: undeclared. Color: undeclared. Pattern: undeclared. The ad still runs. But the one fact that would have placed this blanket with wool shoppers was never declared where Meta's catalog has a field for it. It was left inside a sentence, for the system to pull out if it does, and however it does.

Why the fields are empty

Meta's catalog requires a short list: ID, title, description, availability, condition, price, link, image, brand. Then it accepts a longer list of optional fields: color, size, material, pattern, gender, age group, product type, product category, and custom labels.

Optional is the problem. Because Meta doesn't require them, catalogs often leave them empty. And a feed tool that maps your store to Meta's format copies an empty material field into an empty material column, faithfully.

A feed tool that only maps fields moves empty fields faster.

That sounds harsh, so here is what it means. The tool isn't broken. It did exactly what it was asked: move what's in field A to field B. Nobody asked it to read the description, notice the merino, and declare the material. That's a different job.

The technical name: representation deficiency

In IEO this condition has a name: representation deficiency. The fact exists. It's in prose, legible to any human, and in this case the system even received the sentence. But it isn't expressed in the form the task needs. Here the task is "decide whether this blanket fits a wool shopper", and what Meta's catalog expects for that is a material, declared as a material.

A paragraph isn't a deficiency by itself. The description is doing its job: it sells the blanket to a person. The deficiency is that the same fact has no second home in the field built for it.

When the evidence already exists, no research is needed; the work is structuring. On the blanket, three moves:

1. Read the description for facts. Merino wool. Cream. Hand-knit. 50 × 60 in. Spot clean.
2. Declare the ones Meta has a field for: material, color, size, product type. The rest ("hand-knit", "spot clean") stay in the description, which Meta also receives.
3. Leave the description alone. It's still the best thing on the page.

Where it lands: the catalog fields

Here is the blanket, in the catalog Meta received and in the one it could have received:

Every value in the right column traces to the store's own sentence. One is derived rather than quoted: the product type is the category the sentence places the blanket in, not a phrase from it, and that kind of derivation is legitimate because the sentence supports it. And one field stayed empty on purpose. "Soft cream" names a color; it doesn't say there's no pattern. Filling it would be a guess.

We're not claiming filled fields guarantee better ads. Meta's delivery depends on signals that aren't visible from outside. The simpler point stands on its own: an ad system can use what it receives in the form it expects.

What to do this week

1. Open your catalog in Commerce Manager and look at five of your best-selling products.
2. Check four fields: Is material declared, or only in the description? Is color a field, or only in the photo? Is product type specific ("Throw Blankets") or generic ("Home")? Does the title say what the product is, or only what you named it?
3. For every empty field, read the description. If the answer is there, declare it. If it isn't, leave the field empty; don't guess the material from the photo.
4. Fix the five, then do the next five. This is the kind of work that goes faster once you've done it ten times.

Practical example

An appliance store sells a blender. The description says: "1,200 watts of power, six preset programs, a 64-oz BPA-free pitcher, and a self-cleaning cycle. Quiet enough to run before anyone's awake."

The catalog fields hold: title "Pro Blender", price, availability, image.

Before you read on, decide what becomes an explicit attribute, what stays in the paragraph, and what Meta can actually take.

Becomes explicit in the product record: Power: 1,200 W. Programs: 6 presets. Pitcher: 64 oz, BPA-free. Cleaning: self-cleaning cycle. Keep "BPA-free" on the pitcher, which is what the sentence says, not on the whole blender.

Stays in the paragraph: "Quiet enough to run before anyone's awake." It's a feeling, not a measurement. No decibel figure on the page means no noise field gets filled.

What Meta takes: its catalog has fields for material, color, size and product type, but none for wattage or programs. So for Meta, the title and product type get sharper ("1200W Blender with Self-Cleaning Cycle", Home › Kitchen Appliances › Blenders) and the rest stays in the description, where Meta does receive it. Build the record once, with everything explicit; each destination takes what it has a place for.

That's the representation deficiency described in section 5 of the IEO Methodology: evidence that exists in prose but isn't in a form the machine can resolve for the task. The remedy is structuring, and the limit is the same as always: only what the page actually says.

Check what's explicit, what's missing and what contradicts itself on one of your products → Run the free audit

To go deeper → The IEO Methodology, section 5 (doi.org/10.5281/zenodo.22416784) · nsolvia.com/ieo

Sources: Meta for Business, "Advantage+ Catalog Ads" · Meta for Developers, "Catalog Fields" (required and optional product fields).

← Your Product Page Is Perfect. The Sale Fails at Shipping and Returns. · ⌂ IEO · Next: "Organic", "Made in Italy", "Doctor-Founded". Which of Your Claims Can a Machine Trust? →

Series: Interpretability Engine Optimization · Knowledge Domain: Interpretability (IEO)

Interpretability Engine Optimization (IEO)
The UNDERSTAND Layer
nsolvia.com/ieo