How catalogue *ID matching* holds
Feed IDs must equal event IDs or measurement quietly breaks. This guide makes identifiers agree everywhere.
Product IDs in catalogues must match the IDs transmitted in Pixel and CAPI events for product-level measurement and DPA optimisation. Mismatches silently starve optimisation while dashboards report normally, making ID discipline the highest-leverage boring work in shopping ads.
The contract#
One SKU, one ID, everywhere: feed, data layer, Pixel parameters, CAPI payloads. Generate IDs systematically (never titles, never prices), document the scheme, and gate feed publishes on validation. Reddit catalogue documentation states the matching requirement directly. Reference: Reddit catalogues help; DPA view: DPA page.
Validation routine#
Sample products weekly: feed ID versus event ID versus reported ID, availability flags versus reality, price parity versus landing pages. Automate the diff and alert on drift; manual spot-checks catch what automation mis-specifies. Reporting home: reporting latency.
Availability and price parity#
Out-of-stock products in ads burn trust; price mismatches burn it faster. Sync availability intraday for fast movers, daily minimum for the rest, and pause products the feed cannot keep honest. Shoppers forgive absence; they punish bait. Feed sync: Shopify integration.
Imagery minimums#
Square imagery at 500 pixels or larger per product, current and representative. Catalogue creative refreshes with seasons; grey placeholders convert nobody. Treat feed imagery with the seriousness of ad creative, because it is ad creative. Visual data: image creative data.
Breakage autopsy#
When product ROAS collapses overnight, check IDs before bids: feed migrations, platform upgrades and agency handoffs all silently rewrite identifiers. Log every feed change with dates; most catalogue mysteries solve in the changelog. Dedup twin: dedup guide.
Putting ID discipline into practice#
Run the full ID audit this week: feed versus events versus reports on a product sample, availability versus reality, prices versus landing pages. Fix every mismatch before the next budget conversation; identifiers are the foundation budgets stand on.
Automate the weekly diff with alerts and gate feed publishes on validation. Automation: Shopify integration and reporting latency.
Frequently asked questions#
Why must catalogue and event IDs match?
Matching IDs power product-level measurement and DPA optimisation; mismatches silently starve both.
How are IDs validated?
Weekly sampled diffs of feed versus event versus reported IDs, plus availability and price parity checks.
How fresh must availability be?
Intraday for fast movers, daily minimum otherwise; pause products the feed cannot keep honest.
What imagery do products need?
Square, 500 pixels or larger, current and representative: feed imagery is ad creative.
What breaks catalogues most often?
Silent identifier rewrites from migrations, upgrades and handoffs; check IDs before bids.
What is the highest-leverage boring work?
The full ID audit: feed versus events versus reports, then automation.
Read more on this topic#
The Reddit Ads Hub
Free tools, format guides and live news for every Reddit Ads format.
Open the hubReddit Shopify integration: catalogue and pixel in sync
Native sync for Shopify merchants.
Read the entryReddit Smartly integration: automation at scale
Third-party automation for scale.
Read the entryHome Depot on Reddit: the evergreen DPA case
Evergreen catalogues beating social averages.
Read the entryWant Reddit Ads managed properly?
folkfox runs Reddit campaigns that respect the thread: native creative, separated ad groups and honest reporting. Talk to us before your next test.