I have isolated a reproducible Square-side Meta integration defect that is causing a 0% Meta catalog match rate.
For the same product:
Product: Modern Round Statement Earrings with Gold-Tone Accents
Square SKU: FB-0052
Square catalog Token: 7Z3RBQWTPH4A2RVXOKUYSJJX
Meta catalog Content ID: 7Z3RBQWTPH4A2RVXOKUYSJJX
Square-installed Meta Pixel AddToCart content_ids: 7PLTPNU27N7PBCWD2FKOVLH6
So Square’s catalog feed sends one identifier to Meta, while the Square-installed Meta Pixel sends a different identifier for the exact same product.
Meta therefore cannot match Pixel events to catalog products.
Square support already acknowledged this as an integration payload defect between Square Online and the Meta Business SDK wrapper, but standard support chat has not provided a persistent engineering escalation or known-issue number.
Can a Square moderator please escalate this to the Square Online / Meta integration engineering team or confirm whether this is a known issue?
The needed fix is for the Pixel content_ids and catalog Content IDs to use the same product identifier.
