# Meta vs Pinterest: feed requirements compared

Meta and Pinterest are the two most image-driven channels documented here, and their feed requirements are correspondingly light on identifiers. The differences are in cadence, in market structure and in what a good image means: Meta enforces resolution minimums on Shops, Pinterest rewards vertical crops.

- **Canonical URL:** https://www.feedlab.io/knowledge/compare/meta-vs-pinterest
- **Last reviewed:** 18 September 2026
- **Source:** feedlab knowledge base
- **Licence:** free to quote and cite with attribution to feedlab


## Short answer

A Meta catalogue feed is a good starting point for Pinterest, because the attribute set is close and neither channel leans on identifiers. Two things need attention: Pinterest wants one feed per country and language pair, and its once-a-day fetch means the accuracy you are used to on Meta is not available here at any price.

## Attributes treated differently

| Attribute | Meta | Pinterest |
| --- | --- | --- |
| `brand` | Recommended | Optional |
| `condition` | Required | Optional |
| `gtin` | Recommended | Optional |
| `item_group_id` | Required in some cases | Optional |

## Every attribute, side by side

| Attribute | Meta | Pinterest |
| --- | --- | --- |
| `availability` | Required | Required |
| `brand` | Recommended | Optional |
| `condition` | Required | Optional |
| `custom_label_0` | Optional | Not documented here |
| `description` | Required | Required |
| `google_product_category` | Not supported | Not documented here |
| `gtin` | Recommended | Optional |
| `id` | Required | Required |
| `image_link` | Required | Required |
| `item_group_id` | Required in some cases | Optional |
| `link` | Required | Required |
| `mpn` | Optional | Optional |
| `price` | Required | Required |
| `sale_price` | Optional | Optional |
| `title` | Required | Required |


## Differences a table cannot show

### Meta requires condition, Pinterest does not

Condition is mandatory on every Meta item and optional on Pinterest. If you already feed Meta, you have the mapping and can leave it in place. It is the only requirement-level difference that would block anything.

### Pinterest needs one feed per market

Meta handles multiple countries within a catalogue through its own market settings. Pinterest expects a separate data source per country and language combination. A store selling into several markets goes from one Meta catalogue to several Pinterest feeds, which is a pipeline change rather than a mapping one.

### Cadence is hourly versus daily

Meta supports hourly scheduled fetches and a batch API for individual updates. Pinterest fetches once every 24 hours with no sub-daily option and no routine push API. A product that sells out will be wrong on Pinterest for longer than on Meta, and no amount of regeneration changes that.

### Both care about images, for different reasons

Meta enforces minimum resolutions on Shops surfaces, so an undersized image fails a check. Pinterest has no equivalent gate but displays the image so large that a landscape theme crop underperforms visibly. One is a validation problem, the other is a performance problem, and they have different fixes.

### Variant grouping is required on one and optional on the other

Meta uses item_group_id to build the variant picker in Shops, so it is required wherever a product has variants. Pinterest treats it as optional. Sending it anyway keeps one mapping serving both, and costs nothing.




## Reusing one feed for the other channel

1. **Publish the Meta mapping as a starting point** — Nothing in a Meta feed will cause a Pinterest rejection, so start by pointing Pinterest at the same output and confirm it ingests cleanly before changing anything.
2. **Split the output by country and language** — Generate one feed per market, each carrying its own currency, prices and product URLs. This is the step that most often gets skipped, because a single multi-market file uploads successfully and then behaves oddly.
3. **Reconsider which image you send** — Meta pushed you towards a large square image to satisfy Shops. Pinterest rewards vertical. If the store has a portrait image in a metafield or as a second product image, map it for this channel only.
4. **Align regeneration with the daily fetch** — Pick the fetch time in Pinterest and regenerate shortly before it. On Meta you could regenerate on any cadence and let hourly fetches catch up; here the timing is the only lever you have.
5. **Set expectations about stock accuracy** — With a single daily fetch, a sold-out item can stay pinned as available for most of a day. That is a channel limitation rather than a feed defect, and it is worth saying out loud before someone reports it as a bug.







## Frequently asked questions

### Can I use my Meta catalogue feed for Pinterest?

Yes, with one structural change: Pinterest wants a separate data source for each country and language pair, so a multi-market catalogue needs splitting into one feed per market.

### Does Pinterest require condition like Meta does?

No. Condition is mandatory on every Meta item and optional on Pinterest. If you already map it for Meta, leave it in place for both.

### Which channel keeps stock more current?

Meta, clearly. It fetches as often as hourly and accepts pushed updates through its batch API. Pinterest fetches once every 24 hours, so its catalogue is structurally further behind.

### Should I send different images to Meta and Pinterest?

If you have the images, yes. Meta enforces a resolution minimum on Shops surfaces, while Pinterest displays images large and favours vertical crops. A square image that satisfies Meta is rarely the best-performing image on Pinterest.




## Primary sources

- [Meta: Product catalogue data feed reference](https://www.facebook.com/business/help/120325381656392)
- [Pinterest: Data source ingestion and formatting](https://help.pinterest.com/en/business/article/data-source-ingestion)