Lazyweb

Which App Categories Ask for ATT and Location Permission Most?

Download Markdown

Among the ATT and location apps in Lazyweb Research's corpus, shopping leads ATT asks (8 apps) while food & drink leads location asks (6 apps) [1]. All counts are small — absolute company counts, not rates. Commerce apps drive ATT (ad personalization), and delivery/local-discovery apps drive location.

Shopping leads ATT asks (8 apps) and food & drink leads location asks (6 apps) — Lazyweb Research, July 2026.

By Ali Abouelatta · Lazyweb Research · n=45 · Published 2026-07-07 · Updated July 2026

mobilemonetizationonboardingsaasnotifications
Frontier Splash Screen screen — real in-market example tracked by Lazyweb Research
Spothero Notifications Permission screen — real in-market example tracked by Lazyweb Research
Instacart Account Setup screen — real in-market example tracked by Lazyweb Research
Alexa Splash/App launch screen — real in-market example tracked by Lazyweb Research
Real in-market screens from Frontier, Spothero, Instacart, Alexa — tracked by Lazyweb Research
Count — The finding
ShoppingShopping: 88Food & DrinkFood & Drink: 77EducationEducation: 66Health & FitnessHealth & Fitness: 44EntertainmentEntertainment: 44
Count — The finding
ItemCount
Shopping8
Food & Drink7
Education6
Health & Fitness4
Entertainment4

The finding

By category, absolute company counts only [1]:

ATT companiesCountLocation companiesCount
Shopping8Food & Drink6
Food & Drink7Navigation5
Education6Shopping4
Health & Fitness4Travel3
Entertainment4

Shopping and food & drink appear at the top of both lists — commerce and delivery are the permission-heavy verticals [1].

Why these categories

ATT concentrates in commerce (shopping 8, food & drink 7) because those apps monetize via ad personalization and can honestly frame tracking as 'better deals.' Location concentrates in food & drink (6) and navigation (5) because the core value — delivery, directions, nearby results — literally requires the user's location. Fintech and Social are too small for ATT or location cuts; notification is their only defensible slice [1].

How to apply it

Commerce apps should expect to run both an ATT ask (with a deals or personalization frame) and often a location ask. Delivery, navigation, and local-discovery apps should treat location as core-value-linked and frame it as nearby/near-you (the dominant location pattern). Match the ask to what your category's peers already do.

Caveats

All cuts are below the percentage threshold — absolute company counts only, no per-vertical rates [1]. Fintech and Social lack the volume for ATT/location analysis entirely. Category totals are floors given incidental capture.

The numbers

StatComputed from
ATT: shopping 8, food & drink 7, education 6, health & fitness 4, entertainment 4. Location: food & drink 6, navigation 5, shopping 4, travel 3att_and_location_by_vertical: COUNT(DISTINCT company) GROUP BY category, ATT and location label sets
Methodology. Universe: 45 ATT apps and 30 location apps (of 807), grouped by companies.category, July 2026. All vertical Ns are small, so counts only; capture is incidental, making totals floors.

Sources & citations

  1. [1] Lazyweb Research analysis of 45 ATT apps and 30 location apps (807-app corpus), July 2026. Absolute company counts per category; all below the percentage threshold, so counts only. Fintech/Social too small for ATT/location.

Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-07-07.

Explore the evidence

Related questions

More in Notification, permission, and ATT prompt timing →

Explore the underlying screens, flows, and A/B tests inside Lazyweb. More research