The DMA map that actually matters for US ad verification

Why DMAs, not states

State-level geo-targeting is the wrong resolution for US ad verification. Campaigns are bought against Nielsen DMAs — the Designated Market Areas that define where broadcast TV signals reach and, by extension, where most TV-adjacent advertising buys its inventory. A brand that says "Chicago market" almost always means DMA 602, which spans seven counties in Illinois plus Porter and Lake counties in Indiana. A proxy exit in Gary, Indiana is "Chicago market" to the ad buyer. A proxy exit in Rockford is not.

There are 210 US DMAs. Almost every national campaign that buys regionally weights the top 50 at ~90% of total spend. The cases where state borders matter (state-level cannabis, lottery, gambling, certain healthcare categories) are edge cases. DMAs are the default.

The top 50 DMAs by share of national spend

Rough share of US national ad-buy across the top 50 DMAs (2024 Nielsen reporting; shares are approximate and vary by category):

1. New York — DMA 501 — ~8% of national spend. The single highest- value DMA, especially for financial services, fashion, and agency-side creative QA.
2. Los Angeles — DMA 803 — ~5%. Entertainment, DTC, automotive.
3. Chicago — DMA 602 — ~3.5%. Retail, insurance, B2B.
4. Dallas–Fort Worth — DMA 623 — ~3%. Retail, telecom HQ, automotive.
5. Philadelphia — DMA 504 — ~2.8%. Pharma, sports, regional retail.
6. Houston — DMA 618 — ~2.5%. Energy, healthcare, hispanic DTC.
7. Atlanta — DMA 524 — ~2.3%. Southeast retail, DTC, sports.
8. Washington DC — DMA 511 — ~2%. Government-adjacent, pharma.
9. Boston — DMA 506 — ~2%. Biotech, finance, universities.
10. SF Bay Area — DMA 807 — ~1.9%. Tech products, developer-facing.

DMAs 11–20 (~1.2–1.8% each): Tampa, Phoenix, Seattle, Detroit, Orlando, Minneapolis, Denver, Miami, Cleveland, Sacramento.

DMAs 21–50 (~0.5–1.1% each): Charlotte, Raleigh, Portland, St. Louis, Indianapolis, Nashville, Pittsburgh, Salt Lake City, Baltimore, San Diego, San Antonio, Hartford, Kansas City, Austin, Columbus, Greenville-Spartanburg, Cincinnati, Milwaukee, West Palm Beach, Las Vegas, Jacksonville, Harrisburg, Grand Rapids, Norfolk, Birmingham, Greensboro, Oklahoma City, Albuquerque, Louisville, New Orleans.

(Proxaro covers most of these; see our city-level index for the specific ones in our 20-state anchor set.)

Why DMA-level proxy rotation is worth the operational complexity

For ad verification, brand-safety, or adtech measurement workflows, the reason to rotate at DMA resolution rather than state is:

DMA-gated creative

Campaigns with DMA-level targeting show different creative per DMA. A DTC brand running both a NYC campaign and a Boston campaign may have different hero images, different promo codes, different shipping copy — all tuned to the market. A verification workflow that ignores DMA boundaries will see one of the creative variants, miss the others, and under-report coverage.

DMA-gated pricing

Retail pricing often varies by DMA. A grocery chain's online storefront may show a Chicago-resident price on DMA 602 IPs and a different price on DMA 605 (Des Moines–Ames) IPs, even though both are "Midwest" to a state-level resolution. Price-intel workflows that sample per DMA catch pricing edge cases that state-level workflows miss.

DMA-specific inventory

Some advertisers buy DMA-specific inventory that's invisible to out-of-DMA traffic. An ad placement bought "for Miami DMA 528 only" simply doesn't serve to a Jacksonville IP — not as fallback, not as creative variant, not at all. If you're verifying that a campaign reached its targeted DMAs, you need a proxy exit in each targeted DMA.

How to target DMAs from Proxaro

The API header is X-PX-Dma, which accepts a Nielsen DMA code:

curl --proxy http://USER:PASS@gateway.proxaro.io:7777 \
     --proxy-header "X-PX-Dma: 501" \
     --proxy-header "X-PX-Session: sticky-10m" \
     https://example.com

DMA codes are standard Nielsen assignments. 501 = NYC, 803 = LA, 602 = Chicago, etc. Our US country page lists the top 50 with their codes.

Alternative: use city-level targeting with X-PX-City and we'll map it to the DMA internally. Both approaches work; DMA is more explicit if you're already thinking in DMA terms.

Which carrier class for DMA-targeted ad verification?

For creative-render verification (does the ad look right to a real user?):

• Residential — closest to what a real user sees. Comcast or Spectrum rotating residential, per-request rotation, DMA-pinned. Best for the creative-render side of the workflow.
• Mobile — what a real mobile user sees. Mobile creative is often different from desktop; mobile verification requires mobile exits. T-Mobile or Verizon carrier, DMA-pinned, 15-min sticky.
• ISP / static — when the same verification endpoint needs to be accessed repeatedly from the same IP. Compliance monitoring, fraud- adjacent workflows.

For measurement verification (is the ad counting correctly?):

• Not residential or mobile — measurement endpoints expect verification-class traffic. Bright Data, Oxylabs, DoubleVerify all route measurement traffic through class-appropriate datacenter pools. Don't use residential for measurement; it's the wrong ASN class.

This is the "don't mix" rule: creative verification and measurement verification are different workflows with different ASN requirements. Run them as separate pools.

A common ad-verification workflow, spelled out

1. Pull the campaign's DMA list from Ads Manager / DV360 / The Trade Desk — likely 20-50 DMAs.
2. Map each DMA to a Proxaro city / state combination.
3. Spin up a rotation script that hits each DMA with 3–5 exit samples, captures the creative, stores it with DMA tag.
4. Compare rendered creative across DMAs — look for missing variants, unexpected geo-fallbacks, or stale creative.
5. Output a DMA coverage report to the campaign owner.

On a Coast plan, this workflow fits inside the 30 GB monthly bandwidth for a campaign with ~50 DMAs × 10 daily samples × 30 days. At Carrier-tier or above, you can include mobile in the same rotation.

Per-category DMA weighting

Some categories over-weight specific DMAs:

• Pharma: Northeast Corridor (NYC, Philly, Boston, DC) + RTP (Raleigh, NC) + Indianapolis. Brand creative testing routes Philadelphia / Cambridge / RTP heavily.
• Entertainment: LA over-weighted for studio creative; Nashville over-weighted for music-industry creative.
• Finance: NYC, Charlotte, San Francisco. Banking creative often A/B tests Charlotte vs SF for retail-banking variants.
• Retail DTC: SF Bay Area, NYC, LA, Austin. Testing markets for most US DTC launches.
• Automotive: Detroit (Michigan home metro) + Dallas (AT&T retail influence) + LA. OEM creative QA routes Detroit heavily.

Build your DMA rotation weighted to your category, not uniformly across the top 50.

References

• Nielsen DMA Regions (current): https://www.nielsen.com/dma-regions/
• Methodshop Nielsen DMA full list 2025 rankings
• US TV Database — 2024-25 market rankings

For our DMA-specific city landing pages, start at /us/4g-mobile or pick a state like California or Texas to drill into the metros.