Meta Ads Catalog and Content ID Audit for Shopify

Meta catalogue ads depend on a clean connection between three systems:

1. The products in the ecommerce store
2. The items in the Meta catalogue
3. The content IDs sent through Pixel and Conversions API events

When those identifiers do not match, Meta may receive product-view, add-to-cart and purchase events without knowing which catalogue item they belong to. Dynamic product ads can lose coverage, reporting becomes less useful and the platform has weaker product-level signals.

This audit shows how to diagnose the connection without assuming that an installed integration is automatically correct.

What a content ID does

A content ID identifies the product or variant involved in an event.

For an ecommerce event, Meta may receive information such as:

1. Event name
2. Content ID
3. Content type
4. Value
5. Currency
6. Quantity
7. Event ID
8. Customer information

The content ID should correspond to the identifier used by the connected catalogue.

A common problem is that one system uses the Shopify product ID while another uses the variant ID, SKU or a prefixed identifier.

Map the identifier used by every system

Create a table before changing anything.

The goal is not to force every internal system to use one ID. The goal is to ensure that the event ID sent to Meta matches the catalogue identifier expected for that item.

Decide whether the catalogue is product-level or variant-level

Variant-level catalogues are useful when price, availability, image or destination differs by variant.

Product-level catalogues may be simpler when variants are not advertised independently.

Check whether:

1. Every sellable variant appears
2. Variant prices are accurate
3. Variant availability is accurate
4. Images match the selected variant
5. Product URLs open the correct product or variant
6. Content IDs use the same level

A product-level event cannot always map cleanly to a variant-level catalogue item.

Audit the catalogue item ID

For several representative items, record:

1. Catalogue item ID
2. Retailer ID
3. Product or variant title
4. SKU
5. Product URL
6. Variant URL
7. Price
8. Currency
9. Availability
10. Image

Include:

1. Bestseller
2. Product with many variants
3. Sale product
4. Bundle
5. Subscription product
6. Recently added product
7. Out-of-stock product
8. Product with a previous ID change

Test ViewContent

Open a product page and inspect the event received by Meta.

Confirm:

1. ViewContent fires once per intended page view
2. Content ID is present
3. Content type is correct
4. Value is reasonable
5. Currency is correct
6. The ID exists in the catalogue
7. The selected variant is represented correctly
8. Browser and server events are not creating unintended duplicates

A ViewContent event with the wrong content ID may still appear as a healthy event while failing to match a catalogue item.

Test AddToCart

Add several variants to the cart.

Confirm:

1. AddToCart fires after the actual action
2. Correct variant ID is sent
3. Quantity is correct
4. Price is correct
5. Currency is correct
6. Multiple quantities are represented correctly
7. Cart drawer and full cart behave consistently
8. Quick-add buttons use the same identifier logic

Quick-add, bundle and subscription widgets often use different scripts from the standard product form.

Test InitiateCheckout

Confirm that checkout events contain the items actually in the basket.

Review:

1. Item IDs
2. Quantity
3. Value
4. Currency
5. Bundle components
6. Subscription items
7. Discounted items
8. Free gifts

The value definition should be consistent with the purchase event.

Test Purchase

Complete a controlled order and record:

Confirm:

1. Every purchased item is represented
2. Content IDs exist in the catalogue
3. Browser and server events refer to the same order
4. Deduplication identifiers match
5. Value and currency agree
6. Quantity is correct
7. Test orders can be identified
8. Failed payments do not create completed purchases

Review event match and catalogue match separately

Customer-data match quality and catalogue-item matching are different problems.

Customer-data matching may use information such as hashed email, phone or browser identifiers.

Catalogue matching depends on content IDs and catalogue item identifiers.

A setup can have strong customer-data matching while product IDs remain inconsistent.

Common Shopify identifier patterns

Shopify integrations may use patterns such as:

1. Product ID only
2. Variant ID only
3. Product ID plus variant ID
4. A prefix combined with product or variant ID
5. SKU
6. Country or market-specific identifiers

Do not guess the pattern from one event. Compare a real product in Shopify, the Meta catalogue and the event payload.

Audit bundles

Bundles create special problems.

A bundle may be represented as:

1. One bundle product
2. Several component variants
3. A virtual product that does not exist in the standard feed
4. A discounted collection of regular products

Decide whether Meta should receive:

1. The bundle item ID
2. The component IDs
3. Both, through separate documented logic

The purchase value must not be duplicated across the bundle and its components.

Audit subscriptions

Confirm whether the catalogue contains the standard product, subscription variant or both.

Review:

1. First-order purchase
2. Subscription discount
3. Renewal events
4. Product ID used at checkout
5. Cancellation and refund handling
6. Whether renewals should be included in acquisition reporting

A renewal should not be treated as a new customer acquisition event without a clear reason.

Review feed health

Content IDs cannot solve a weak catalogue.

Check:

1. Missing products
2. Duplicate products
3. Rejected items
4. Incorrect prices
5. Stale availability
6. Broken URLs
7. Low-quality images
8. Missing variant attributes
9. Unsupported claims
10. Country or market mismatches

Dynamic ads can only use eligible catalogue items.

Review product-set rules

Product sets may be built from:

1. Product type
2. Collection
3. Brand
4. Price
5. Availability
6. Custom labels
7. Margin tier
8. Bestseller status

Confirm that rule-based sets still include the intended products after feed changes.

A renamed product type or missing custom label can empty a product set without changing the campaign itself.

Audit landing-page destinations

For catalogue items, check that the click opens:

1. The correct product
2. The correct variant where possible
3. The correct market
4. The correct currency
5. An available item
6. A mobile-friendly page
7. The advertised price
8. The correct offer

A perfect identifier match cannot rescue an inaccurate landing page.

Build a mismatch report

Classify issues:

1. Missing in catalogue
2. Product-versus-variant mismatch
3. Prefix mismatch
4. SKU mismatch
5. Stale product
6. Bundle logic
7. Market-specific mismatch
8. Duplicate item

Prioritize fixes

Critical

Purchase IDs do not match the catalogue, values are duplicated or the wrong products are reported.

High

Best-selling product views and carts fail to match.

Medium

Low-volume variants or product sets are incomplete.

Monitor

Small explained differences that do not affect eligible advertised products.

Retest after changes

After changing the feed, integration or event logic:

1. Allow the catalogue to refresh
2. Recheck item IDs
3. Test product view
4. Test add to cart
5. Test checkout
6. Complete a purchase
7. Confirm deduplication
8. Confirm dynamic product eligibility
9. Review campaign delivery
10. Document the final identifier pattern

Common mistakes

Assuming the official app guarantees perfect matching

Custom themes, bundles, subscriptions and old scripts can still create conflicts.

Checking only the event name

Purchase fires, but the product IDs are wrong.

Using SKU without stable SKU governance

SKUs change or remain blank for some variants.

Mixing product and variant IDs

Different funnel events refer to different catalogue levels.

Ignoring markets

Country-specific feeds or URLs create mismatches.

Fixing IDs without testing the full order

ViewContent works, but Purchase still fails.

Final principle

Meta catalogue tracking is healthy only when the exact products customers view, add and purchase can be matched back to eligible catalogue items.

Map the identifier pattern, test every funnel stage, reconcile browser and server purchases, and document special handling for variants, bundles, subscriptions and international markets.

Continue with the Dynamic Product Ads guide and Shopify tracking audit.

Book a free Beelog profit audit to review your Meta catalogue, Pixel, Conversions API and Shopify product data together.