2026 Geo-Panel Audit: Mobility Coverage Post-FTC

The honest 2026 answer to "how big is your mobility panel" is smaller than any 2022 deck said it was, and the difference is not marketing — it is structural. Between 2024 and 2026, the Federal Trade Commission settled three consecutive consent orders that reshaped location-data supply: the X-Mode Social / Outlogic order banning the sale of sensitive-category location data, the InMarket Media order barring precise-location use for advertising without affirmative consent, and the Mobilewalla order requiring deletion of historically-collected location data lacking consent. The cumulative effect is not a rebrand — it is a measurable reduction in daily device-record volume and a meaningful change in what operator-grade coverage looks like. This piece is the working audit: what got pulled, what panel math actually reads today, what supply is replacing the deleted tranches, and the four questions a buyer should ask any mobility vendor before licensing. For the catalog surface see Global Mobility Location Data and POI + Geofencing; for the enforcement baseline see FTC location data enforcement: what data buyers need to know and data brokers post-FTC consent orders: procurement diligence in 2026.

The Three FTC Consent Orders Reshaped Supply

Between January and December 2024, the FTC ran three back-to-back consent orders that structurally reshaped mobility-data supply. The X-Mode Social / Outlogic order (January 2024) was the first: it bans X-Mode and its successor Outlogic from selling or sharing sensitive-category location data — data that identifies visits to medical facilities, places of religious worship, domestic-violence shelters, reproductive-health clinics, and similar venues. The InMarket Media order (same month) went further: it bars InMarket from using precise consumer location data for advertising-related purposes without affirmative consent, specifically addressing the consent-chain gap where SDK partners embedded InMarket code without disclosing the ad-targeting use. The Mobilewalla order (December 2024) closed the year by requiring deletion of historically-collected location data lacking consent provenance, and banning the sale of sensitive-category visits. Reading the three orders together, the FTC drew a clear operational line: precise-location supply requires documented, traffic-specific affirmative consent at the point of collection; sensitive-category scrubbing must happen before egress; and historical data collected under weak or missing consent is subject to deletion. Every major mobility vendor restructured its SDK-partner network and consent documentation in response. The practical consequence: the honest supply-side headcount in 2026 is materially smaller, materially cleaner, and materially better-documented than 2022 decks projected. For buyer diligence specifics see data brokers post-FTC consent orders: procurement diligence in 2026.

Panel Math Post-Deletion: How Coverage Actually Looks

The question a buyer should ask is not "how many total devices are in your panel" — that number is a rollup that mixes observed-once devices, consented active devices, and legacy-tranche devices that may be subject to deletion. The operator-grade question is daily unique devices observed inside a specific geography with documented consent provenance. Typical honest 2026 numbers for the top-tier mobility vendors in a US-metro geography land in the 40-60% range of their pre-2024 figures for that same geography. The composition also shifted: the surviving panel skews toward the Android SDK-consented lane (because Apple's ATT framework had already compressed iOS opt-in rates to roughly 25-35% in the relevant cohorts), and away from the sensitive-category venues that sensitive-category scrubbing now removes before egress. The same panel math extends into panel-sizing decisions for measurement: a foot-traffic panel sized at 1-2% of a metro population is still statistically valid for most aggregated-measurement use cases, but the panel-effective ratio for small-footprint chains dropped with the overall supply contraction, and buyers should re-run their power calculations against the 2026 panel rather than the 2022 one.

What Replaces the Deleted Supply: Consented SDKs + Carrier Aggregates

The supply-replacement question is where vendor decks diverge most widely. The honest 2026 answer is that three distinct sources fill different parts of the gap, each with different coverage characteristics and different compliance boundaries:

• Directly-consented mobile SDKs. Smaller than 2022 but cleaner. Vendors that retained an SDK-consented lane publish affirmative-consent flows at the point of collection, document SDK-partner disclosure language, and run sensitive-category scrubbing before egress. This is the operator-grade tranche — expect 40-60% of pre-2024 volume, but meaningfully cleaner than the deleted historical tranches.
• Carrier-panel aggregates. Larger reach, coarser granularity. Carrier-sourced aggregates cover essentially the full US mobile population at the census-block-group or ZIP-plus-4 level but typically do not resolve to device-level traces. Useful for aggregate origin-destination, metro-level mobility shifts, and CRE site-selection work; less useful for device-level retargeting or small-footprint attribution.
• CTV household resolution. Complementary, not substitute. CTV/ACR panels resolve at the household level (TV IP + device graph), and while the signal is not mobility, it fills the ad-targeting gap for cross-channel audiences where a mobility-only panel is now too thin. The IAB Tech Lab cross-device measurement framework treats CTV + mobility as complementary signals, not substitutes.

A vendor deck that claims to have "fully replaced" pre-2024 coverage with a single source is usually conflating one of these lanes with another — typically selling a carrier-aggregate feed as a mobility-panel equivalent, or selling CTV household resolution as if it produced device-level visit traces. For the complementary-signal framing see privacy-safe retail measurement: foot traffic + card panels + CTV attribution and cross-channel measurement for privacy-first advertisers.

Reading a Vendor Deck: Four Questions That Surface Real Coverage

Mobility vendor decks are uniformly optimistic. Buyer diligence in 2026 should lean on four questions that surface what the rollup numbers hide:

1. What is your daily-unique-devices count inside my specific geography with documented consent provenance — not panel-wide, not observed-ever. Require a number tied to a named DMA or metro-area polygon, measured over a recent rolling window (30/60/90-day), with the consent-chain documentation available on request.
2. What do your SDK-partner consent flows look like today — specifically the disclosure language shown to the end user before location-data collection, the opt-in mechanism (in-app toggle vs install-time prompt), and the partner-list that sources into your panel. The FTC InMarket order establishes that weak-consent SDK integrations are a real enforcement risk; the buyer should see the actual disclosure copy, not a summary.
3. What sensitive-category scrubbing runs against the panel output, and what venue-category list is applied? The X-Mode and Mobilewalla orders draw an explicit list — medical facilities, religious-worship venues, domestic-violence shelters, reproductive-health clinics, substance-abuse treatment facilities. A vendor that cannot show the scrubbing-category list in operation is not reading the consent-order landscape correctly.
4. What did the 2024 deletion-event cohort remove from your panel — was it a distinct historical tranche with documented weak consent, was it merged back in after new SDK-consent collection, or did the vendor never carry the tranche at issue? The answer tells you how the vendor's panel was assembled and whether any inherited risk remains in the current feed.

A vendor that answers all four questions cleanly is a candidate for operator-grade procurement. A vendor that deflects on any of them is trading on the optimism of pre-2024 decks, and the exposure lives with the buyer once the feed is in production. For the procurement-diligence checklist see data brokers post-FTC consent orders and for the compliance frame overall see FTC location data enforcement.

What Operator-Grade Geo-Panel Coverage Means in 2026

An operator-grade 2026 mobility panel does not promise pre-2024 coverage — that promise was not honest in 2022 either and is definitely not honest now. Operator-grade means three things: (1) a documented consent chain from end-user collection through SDK-partner disclosure through vendor egress, surviving audit; (2) honest geography-level math reported as daily-unique-devices in a named polygon, not rollup panel totals; (3) sensitive-category scrubbing applied before egress, with the scrubbing-category list available to buyers. Vendors that operate this way are meaningfully smaller than 2022 vendors were, but they are stable under regulatory scrutiny and their data is usable for the ad-tech, measurement, and retail-analytics use cases that generate the revenue. The buyer's side of the exchange is pricing the honesty in — not punishing vendors for the smaller number, but rewarding them for the documented consent and the operationally-audited scrubbing. For the catalog surface see Global Mobility Location Data, POI + Geofencing, and Audience Targeting solution; for the measurement frame see Cross-Channel Measurement solution and Retail industry hub; for cross-audit companions see foot-traffic vs credit-card panels and geofencing best practices.