How to Set Up Parallel Meta Catalogs (Optional)

📘
Why two catalogs?
Meta uses the purchase signals connected to a catalog to train ad optimization. If Angler and BAU events feed the same catalog, it can lead to over-attribution of other campaigns in your ad account, especially outside of a testing environment. If in-platform metrics are your source of truth, you may want to leverage catalog duplication — two catalogs with the same product feed on different pixels/datasets.

1. Copy your existing feed URL

In your current catalog, go to Data Sources → click your data feed → Settings tab. Copy the feed URL.

2. Create a new catalog for Angler

In Commerce Manager, go to Catalogs → + Add Catalog.

Select E-commerce and name it clearly (e.g., "Brand — Angler Catalog")
Assign it to the correct Business Portfolio
Under Data Sources → Add Items → Data Feed → Use a URL, paste the same feed URL from Step 1
Set the same fetch schedule as your existing catalog (hourly or daily)

3. Connect the Angler Events dataset

In the new catalog's Settings, under Event Sources, connect your Angler Events dataset. Do not connect it to the original BAU catalog.

4. Leave the BAU catalog untouched

Your existing catalog and all live campaigns keep running as-is. The BAU catalog stays connected to your standard Meta pixel only.

5. Verify feed parity

After the first fetch completes, confirm product counts match between both catalogs under Data Sources → Diagnostics. Check for feed errors (missing fields, broken image URLs) before launching campaigns.

6. Launch Angler campaigns against the new catalog

When setting up new ad sets, explicitly select the Angler catalog's product sets — not the BAU ones. This ensures Angler's signals power your new campaigns end-to-end.

Questions? Reach your Angler CS team or visit getangler.ai.