For dynamic ads to work, the product IDs in your pixel events must match the IDs in your catalog feed. If they don’t, the ad platform can’t connect “this visitor viewed product X” to “product X in the catalog.” Your AI assistant can compare both sides, identify any discrepancy, and fix the PixelYourSite settings in one conversation.
To use this workflow, you need PixelYourSite MCP connected to your site and an AI assistant configured to use it. See Getting Started with PixelYourSite MCP for setup instructions.
Requires PixelYourSite Pro and Product Catalog Feed for WooCommerce 5.9 or later.
The scenario
A WooCommerce store runs Facebook dynamic retargeting. The catalog was set up a while ago using product SKUs. At some point the PixelYourSite content ID setting was changed to use the WordPress post ID instead. Now PYS sends 123 in the pixel’s ViewContent and AddToCart events, but the Facebook catalog has those products listed as TSHIRT-BLU-M. The IDs don’t match and dynamic ads won’t work correctly.
The store owner may not notice immediately. The pixel fires, the catalog exists, the campaign is running. But the platform will flag missing or unmatched IDs in Catalog Manager.
Step 1: Run the audit
Ask: “Check my tracking setup”
The assistant runs the full audit. If the catalog feed alignment domain comes back as a warning, it means a mismatch was detected. The assistant will tell you before going further.
Or go directly: “Check my catalog feed alignment”
Step 2: Review the comparison
The assistant calls get_catalog_feed_alignment and returns a comparison for each configured feed. For the scenario above it finds:
- PYS content ID source:
product_id(WordPress post ID) - Feed content ID source:
product_sku - Prefix in PYS: none
- Prefix in feed: none
- Result: mismatch
The assistant also flags the SKU risk: products without a SKU set return a blank ID in the feed, which silently drops them from catalog matching. It recommends reverting both sides to product_id.
Before proposing any fix, the assistant asks: “Is the Product Catalog Feed plugin the catalog actually connected in your Meta Catalog Manager? Or do you upload your catalog a different way?”
This matters because the tool detects the plugin, not the live catalog. If you upload the feed manually or use a different plugin, the comparison is against the wrong source. Confirm before proceeding.
Step 3: Apply the fix
Once you confirm the feed is the active catalog source, the assistant proposes the fix:
Recommended: revert both sides to product_id
PYS can change its own setting immediately. The feed plugin setting you change yourself in its admin. The assistant makes clear which side it can fix and which you handle.
“Yes, update PYS to use product_id”
Two-step confirm: the assistant shows exactly which platforms will be updated and what the content ID source will change to. You confirm. PYS is updated.
Then go to Product Catalog Feed for WooCommerce and revert the feed’s ID source to product_id as well. Both sides now send the same format.
Alternative: align PYS to match the feed’s SKU
If you specifically need SKU-based IDs (for example, because an external inventory system references products by SKU), the assistant can align PYS to match the feed instead. You confirm that SKU is required, and the assistant updates PYS accordingly. It will remind you that products without a SKU set will be missing from matching.
Per-platform mismatches
Content ID is stored per platform in PYS. If platforms were set differently at some point, the assistant surfaces each one. For example, Facebook might be on product_id while Pinterest is still on product_sku from an earlier setup.
Ask: “Show me the content ID settings per platform” and the assistant returns the full breakdown. You can then align specific platforms individually.
Prefix and suffix mismatches
Both PYS and the feed support a prefix and suffix around the product ID. A common issue: the feed was configured with a WC- prefix to distinguish WooCommerce products in a multi-source catalog, but PYS sends the bare ID. The result is 123 in events vs WC-123 in the catalog.
The assistant detects and reports prefix and suffix differences alongside the source comparison.
After the fix
Dynamic ads take time to start matching after a content ID change. The catalog needs to re-sync and the platform’s matching engine needs to process recent events. Allow 24 to 48 hours before judging whether retargeting has recovered.
You can also ask: “Check my catalog alignment again” after making changes to confirm the PYS side now matches.
What the assistant cannot do
- Change the feed plugin’s settings. PYS has no write access to the Product Catalog Feed plugin. Any feed-side changes you make manually in that plugin.
- Confirm the feed is connected in Meta, Google, or TikTok. It detects the plugin, not the live catalog. You verify that in Catalog Manager or Merchant Center.
- Fix a
custom_fieldmismatch automatically. If PYS is set to use a custom field as the content ID, the feed comparison cannot be made. The assistant will tell you this and explain the situation.