# Rabbot for Meta (Facebook & Instagram)

> Rabbot connects to Meta (Facebook & Instagram) and notifies you when a product is rejected. Paid plans read verdicts every day and alert the same day.
> Published: 2026-10-14
> Updated: 2026-10-14
> Canonical: https://rabbot.ai/integrations/meta/

---

- **Channel:** Meta (Facebook & Instagram)
- **Status:** Live, Meta Advanced Access granted
- **Plans:** Starter, Growth and Pro
- **Channels per plan:** Starter: one channel, Growth: three channels, Pro: every channel
- **Verdicts read:** Daily
- **Not included:** Free (no channel connections)

## What the Meta catalog is

Meta reviews the products you sell on Facebook and Instagram through a catalog. Meta's developer documentation describes a catalog as a structured data file that holds information about the items in your inventory, with each row representing an individual product [1]. Catalogs are managed in Meta's business tools, and results appear in [Meta Commerce Manager](/glossary/meta-commerce-manager/).

## What Rabbot does with it

On paid plans, Rabbot connects to Meta (Facebook & Instagram) and notifies you when a product is rejected. It reads Meta's own verdicts on your catalog every day, the same review results you would find in Commerce Manager: products Meta rejected, items still in review, and data-quality issues. Four Meta checks cover the catalog.

A rejection opens as a critical finding. An item in review or a data-quality issue opens as a warning. Each finding names the product, what Meta decided, and what to do next.

A rejection is emailed and, on paid plans with [Slack set up](/integrations/slack/), posted to Slack the same day Rabbot reads it. Warnings are emailed on paid plans. Every verdict appears in the dashboard and the weekly digest, and an AI agent can read them over [MCP](/docs/mcp/what-the-mcp-server-is/).

Rabbot's own feed cross-check runs beside it. It compares the data your [product feed](/glossary/product-feed/) is built from with what the live storefront shows (price, availability, required identifiers, missing or blank data) and raises a gap as disapproval risk before Meta reviews the product. Meta access for Rabbot has been granted, and the connection is live on paid plans.

## How to connect

Open Settings, find the Meta (Facebook & Instagram) card, and choose Connect. Connecting a channel needs Starter or above. On Free, the card shows See plans, and the Free plan gets the day-zero cross-check only.

[The Meta channel](/docs/feeds/meta-channel/) has the full steps. [Plans at a glance](/docs/billing/plans-at-a-glance/) and [switching channels](/docs/billing/switching-channels/) cover how many channels each plan watches and how to change them.

## What the connection covers

- Rabbot reads your catalog and leaves the catalog and your Shopify products to you.
- Rabbot reads verdicts every day, and a rejection reaches you the same day Rabbot reads it.
- Meta makes the decision and Rabbot reports it with the product named. You fix the cause.
- Rabbot reads on its own schedule, then notifies you.
- Commerce Manager stays where you manage the catalog itself.

## Where to read next

[What feed monitoring is](/docs/feeds/what-feed-monitoring-is/) explains both layers, and [feed alerts and disapproval risk](/docs/feeds/feed-alerts-and-disapproval-risk/) covers the alert types. A [disapproved product](/glossary/disapproved-product/) on Google follows similar logic, covered in the [Google Merchant Center integration](/integrations/google-merchant-center/). Identifier problems often start with a missing [GTIN](/glossary/gtin/).

## Sources

- [1] [Meta for Developers: Catalog overview](https://developers.facebook.com/docs/commerce-platform/catalog/overview)