Meta Switched From Nielsen DMA to Comscore Markets for Automotive Ads on June 22, 2026. Here's What Changed.

Meta ended Nielsen DMA targeting for automotive model ads on June 22, 2026. How to migrate vehicle offer feeds to Comscore Markets, plus reporting impact.

Meta Switched From Nielsen DMA to Comscore Markets for Automotive Ads on June 22, 2026. Here's What Changed.

On June 22, 2026, Meta ended Nielsen Designated Market Area (DMA) targeting for automotive model ads and switched to Comscore Markets. Any campaign that still relies on dma_codes in its vehicle offer feed stops delivering today. If you advertise vehicles on Facebook or Instagram, your feed has to use Comscore Market IDs from now on. There is no graceful fallback, and there is no extension.

Meta announced the change on March 13, 2026, opened the migration window on March 23, and started issuing feed-ingestion notifications on April 20. June 22 is the hard cutoff. This piece covers what changed, why Meta made the move, how to migrate a feed that is still on DMA codes, and what to watch for in reporting now that the underlying market data is different.

What changed today

Meta's automotive model ads product is the ad format that pulls vehicles from a structured vehicle offer feed and shows them dynamically across Facebook, Instagram, and the Meta audience network. The feed has a geo-targeting field that tells Meta which market each vehicle inventory belongs to. Until today, that field used Nielsen DMA codes. From today, it uses Comscore Market IDs.

The practical effect of the switch:

The migration is not optional. If you do nothing, your campaigns pause and you lose delivery until the feed update propagates.

Why Meta made the switch

Meta has been moving away from Nielsen for measurement and market definitions across several products for the better part of a year. The official framing is that Comscore offers a more sustainable and scalable solution for long-term performance and measurement, and that Comscore's data set spans both linear television and digital media, which fits how Meta thinks about cross-platform automotive demand.

Both providers cover the same 210 geographic areas in the United States, so the map of markets has not changed. What changed is the ID schema and the underlying methodology. Comscore uses panel data combined with census-based modeling; Nielsen uses set-meter and panel data. Boundary lines between markets are largely the same, but a handful of edge counties move between markets under the two providers, which means a small percentage of vehicle offers will get reclassified.

The deeper reason is contractual and economic. Meta's relationship with Nielsen was a legacy partnership inherited from years of television-era measurement standards. Comscore offers Meta better integration on the digital side, more flexible licensing terms, and a partnership structure that aligns with Meta's broader push toward first-party measurement and away from third-party panel data where possible.

How the migration works

If your vehicle offer feed is current, you already did this work between March and June. If you have a feed that still references DMA codes, you need to update it today.

The migration path Meta published has three pieces:

1. Replace the dma_code field in your vehicle offer feed with a Comscore Market ID. Meta published a mapping table on March 13, 2026, that translates every Nielsen DMA to its corresponding Comscore Market. The table is available through Meta's developer documentation and through the feed validation tools in Commerce Manager.

2. Update any custom audiences or saved targeting that referenced DMA-level definitions. If you have audiences scoped to specific Nielsen DMAs (for example, a custom audience for the Chicago DMA), rebuild them against the Comscore Markets equivalent. Most rebuilds are one-to-one and take minutes, but a few will require splitting or combining audiences where the underlying boundaries shifted.

3. Re-validate the feed. After the field swap, run a feed validation in Commerce Manager. Successful validation produces a green status and confirms that vehicle offers will be matched to Comscore Markets going forward.

Feeds that fail validation typically fail for one of three reasons: dma_code field still present without the Comscore Market ID, mismatched market ID format (Comscore IDs use a different numbering convention), or vehicles flagged with market codes that do not exist in the Comscore set. All three are fixable inside Commerce Manager.

What to expect in reporting

Reporting changes in two ways once the migration completes.

First, market labels in your Ads Manager reports now reference Comscore Markets rather than Nielsen DMAs. The names are very similar in most cases (Chicago, Dallas-Fort Worth, Los Angeles all read the same), but a handful of markets are labeled differently. Pay attention to mid-sized markets where boundary definitions diverge.

Second, year-over-year and pre-cutover comparisons will have small attribution noise. A campaign that delivered 1,000 leads to the Cleveland DMA in May 2026 will deliver leads to the Cleveland Comscore Market in July 2026, but the population mix inside that market is slightly different. Expect a low-single-digit shift in CPL and conversion rate purely from the data definition change, not from any real performance change.

If you report on Meta automotive performance to a dealer client or an automotive group, flag this in your June and July reporting. Note clearly that the market definitions changed on June 22, 2026, and that small variance in market-level metrics is expected and not a campaign performance issue.

What this means for dealer groups and automotive marketers

Three things are worth thinking about beyond the literal migration:

The cross-platform measurement story for automotive is fragmenting further. Different platforms are now using different market data providers, which makes apples-to-apples cross-channel comparison harder. If an account runs Meta automotive ads alongside Google vehicle ads and connected TV buys, the geo splits across those platforms will not line up perfectly. Reporting should be built around the account's own attribution model, not platform-native market labels.

Comscore's panel methodology has implications for smaller markets. Nielsen's set-meter coverage in major DMAs is dense; Comscore's panel coverage is broader but thinner per market. For very small markets, expect slightly noisier delivery patterns and slightly less reliable market-level CPL data for the first month or two after the cutover as Meta's optimization recalibrates.

Vehicle offer feeds are now a more sensitive piece of infrastructure than they were last year. Between this migration, the move from product-id-based to vehicle-id-based feeds last fall, and the catalog API changes coming in 2026-07, the feed is the single highest-leverage piece of an automotive ads stack on Meta. Treat it accordingly: monitor feed health weekly, log every change, and assign a documented owner for the feed.

What automotive accounts should be doing right now

If a dealer or automotive account is running Meta model ads, here is the practical playbook for the next 30 days:

1. Confirm the feed is migrated. Pull the active vehicle offer feed and verify that dma_code is gone and Comscore Market IDs are in place. If anything still references DMA codes, that campaign is paused as of today; fix it before doing anything else.

2. Re-validate in Commerce Manager. A green status confirms vehicle offers will match correctly to Comscore Markets. If validation fails, check for the three common errors: dma_code still present, mismatched market ID format, or codes that do not exist in the Comscore set.

3. Rebuild any DMA-scoped audiences. Custom audiences or saved targeting that referenced specific Nielsen DMAs need to be rebuilt against Comscore Markets equivalents. Most are one-to-one and take minutes. A few will need to be split or combined where boundaries shifted.

4. Flag the cutover in client reporting. Any June or July report that crosses June 22 should note that market definitions changed and small variance at the market level is expected. This prevents a normal data-definition shift from getting misread as a performance issue.

5. Rebuild market-level dashboards. Looker Studio, Supermetrics, or any custom reporting that pulled DMA names from a static lookup table needs the lookup pointed at the Comscore Markets mapping. One-time work, roughly an hour per dashboard.

6. Watch market-level CPL for 30 to 60 days. Comscore's panel methodology can produce noisier delivery in smaller markets while Meta's optimization recalibrates. Do not over-react to first-week variance, but track it.

7. Document the feed owner. Whoever maintains the vehicle offer feed at the agency or in-house should be named and on the hook for weekly feed health checks. Feeds are now too consequential to treat as set-and-forget.

8. Look ahead to the 2026-07 catalog API changes. Meta's catalog ads API moves to a new version later this summer with adjustments to feed metafields and field formats. Block time on the calendar now so the next feed-maintenance window does not get missed.

Frequently asked questions

What is Meta's switch from Nielsen DMA to Comscore Markets?

Meta replaced Nielsen Designated Market Area (DMA) data with Comscore Markets data as the geographic targeting and reporting standard for automotive model ads. The change took effect June 22, 2026, and applies to vehicle offer feeds, campaign targeting, and reporting market labels.

What happens if I do nothing?

Any automotive model ads campaign with a vehicle offer feed that still references dma_codes stops delivering on June 22, 2026. There is no automatic conversion. You have to update the feed to use Comscore Market IDs and re-validate it in Commerce Manager before delivery resumes.

Does the switch affect non-automotive Meta ads?

No. The change is scoped to automotive model ads and vehicle offer feeds. Standard catalog ads, lead ads, and conversion campaigns for other product categories are not affected. Geographic targeting at the city, state, and country level uses the same controls as before.

Will my historical reporting still make sense?

Mostly. The market names are very similar between Nielsen DMA and Comscore Markets because both providers cover the same 210 US geographic areas, but boundary definitions diverge in a handful of edge counties. Expect low-single-digit variance when comparing pre-June-22 metrics to post-June-22 metrics at the market level. Document the cutover date in any client report that spans the change.

How do I find the right Comscore Market ID for each vehicle?

Meta published a Nielsen DMA to Comscore Markets mapping table on March 13, 2026. The table is available through Meta's developer documentation for the catalog ads product. Most mappings are one-to-one. A few markets split or combine slightly under Comscore boundaries, so review the edge cases manually.

What other Meta changes should automotive advertisers watch this year?

The catalog ads API moves to a new version (2026-07) later this summer, which adjusts how feed metafields work and changes a few field formats. Vehicle inventory feeds are also moving toward more structured pricing and incentive fields. Plan to spend a few hours each quarter on feed maintenance and validation rather than treating the feed as set-and-forget infrastructure.

Bottom line

Meta's switch from Nielsen DMA to Comscore Markets for automotive model ads is a hard cutoff, not a soft transition. Vehicle offer feeds that still use dma_codes stop delivering today. The migration itself is straightforward: replace the DMA field with the Comscore Market ID using Meta's published mapping table, rebuild any DMA-scoped audiences, and re-validate the feed in Commerce Manager. Expect minor variance in market-level reporting for a month or two as Meta's optimization recalibrates, and update any client-facing reports to flag the change so that small swings in CPL or conversion rate do not get misread as performance issues.

*Want help auditing your automotive ad feeds before they pause? Book a call with us.*

Related articles