We run a Square Online store with the Meta for Business sales channel connected (Online > Meta for Business). Our Meta catalog match rate (Commerce Manager > Events) is stuck at ~22% because of a content_id mismatch between our Meta Pixel events and our synced catalog.
Root cause: the Meta Pixel events fired by our Square Online storefront (POST to /app/cms/api/v1/sites/{site_id}/facebook/pixel-events) send content_id as the parent Square catalog Item ID. But the Facebook/Instagram catalog Square syncs via the “Square” app data source uses the Item Variation ID as the retailer_id - a different identifier for the same product.
Verified example (captured directly from a live AddToCart pixel event on our storefront):
- Product: “2026 Topps Football Super Box”
- Pixel event content_id: an Item ID (e.g. N3IZ42WP6JAHMIGZ5UNJFMVW)
- Catalog entry for the same product is keyed by its Item Variation ID (e.g. IEKD6BCS5VOSYI6ITTJIFXGE)
Meta’s own Commerce Manager diagnostics flagged additional mismatched content IDs from our pixel, and each one also resolves to a Square Item ID rather than the Item Variation ID the catalog holds - so this isn’t a one-off, it’s systemic. Since most of our products have a single “Regular” variation, this breaks catalog matching for nearly the entire catalog and blocks Advantage+ catalog / dynamic product ads.
I raised this with Square general support chat; they confirmed this needs the engineering team that owns the Meta for Business / pixel-catalog integration, since it’s a code-level ID alignment issue between the /facebook/pixel-events payload and the catalog sync, and pointed me here.
I have exact reproduction details - Meta Business ID, ad account ID, Pixel/Dataset ID, catalog ID, and several more verified Item ID / Item Variation ID pairs - ready to share. I’d rather not post those publicly; happy to provide them if a Square engineer replies here or reaches out.
Is this a known issue, and can someone from the Meta for Business integration team take a look?
We are experiencing the same issue with our Square Online store and Meta for Business integration.
Our Meta catalog is synced directly from Square and currently contains 52 products. Meta Commerce Manager is reporting a catalog match rate of only 46.9%, with Product Views matching at 14.5%, while AddToCart is 92.5% and Purchases are 100%.
We confirmed the mismatch directly in Meta Events Manager Test Events. For example, an AddToCart server event from our Square Online store sent:
content_ids: DBPAMJK7IEUXM4KIT3B6UY3Q
Meta reports that some content IDs being received do not match any product in the Square-connected catalog. Searching another reported content ID directly in the Square-synced Meta catalog also returned “No products found.”
This appears consistent with the issue described in this thread: Square’s storefront/event integration is sending an identifier that does not consistently correspond to the retailer_id/product identifier Square supplies to the Meta catalog.
Could someone from Square’s Meta for Business / Square Online integration team investigate this? Since both the catalog synchronization and the event integration are Square-managed, we would like to know whether this is a known identifier-mapping issue and whether a fix is being worked on.
Square Online storefront behavior, including the Meta for Business channel and the Pixel/Conversions API events it fires, isn’t something we can debug or commit to fixes for here — these forums cover the public Square APIs and SDKs. To be clear though, this isn’t a case for Meta’s support either. Both the catalog sync and the event payload are generated by Square, so Meta has nothing to correct on their side.
The path that reaches the owning team is Square Support, asking them to file a bug against the Square Online Meta for Business integration and referencing this thread. Please keep your Business ID, ad account ID, Pixel/Dataset ID, and catalog ID out of the public thread, and share those only in that case.
On expectations meanwhile: the synced Content IDs and the storefront’s tracking output aren’t editable from the Square Online dashboard, so there isn’t a seller-side workaround that restores catalog matching. Event Setup Tool’s “Don’t include content ID” will quiet Meta’s diagnostics, but it forfeits dynamic/catalog attribution, a mitigation, not a fix. Here are a couple of resources I found as well in case you haven’t seen them.