Skip to content
English
More support Sign in
Contact Us
  • There are no suggestions because the search field is empty.

Resolving Meta Catalog Match Rates

How to identify and resolve low Meta Catalog match rates caused by missing Content IDs.

Low match rates in the Meta Catalog typically occur when the vehicle inventory feed is active, but shopper activity on the website is not being linked to specific items in that feed.

Root Cause

The primary cause is missing Content IDs. While the inventory feed is healthy, the dealership website is not firing the required Content ID events to the Meta Pixel during a user's visit. Without these IDs, Meta cannot "match" a visitor to a specific vehicle in the catalog.

Resolution Steps

  1. Script Installation
    Install the Orbee tracking script on the dealership website. This script bridges the communication gap between user behavior and the Meta Pixel.

  2. Event Validation
    Verify that "Vehicle View" events are correctly segmenting. The script must successfully pass the unique Content ID to the Pixel for every vehicle viewed.

  3. Data Synchronization
    Once IDs are captured and transmitted, Meta will begin matching "Vehicle View" to the catalog, stabilizing the match rate.

Impact of Consent Management Tools

Privacy and consent configurations directly affect data collection:

  • User Opt-Out: If a visitor opts-out via a consent banner, tracking will be disabled and Content ID events will not fire for that session.

  • Opt-In Default: If the website tool is configured to block tracking by default, no data is collected until the user explicitly accepts. Both scenarios will naturally result in lower reported match rates.