# Should ATT Prompts Frame Tracking as Personalization or as Better Deals?

Source: Lazyweb Research
Published: 2026-07-07
Sample size: n=42
Tags: mobile, monetization, ux-patterns, onboarding
HTML: https://www.lazyweb.com/research/att-personalization-vs-deals-framing
Markdown: https://www.lazyweb.com/research/att-personalization-vs-deals-framing.md

**Answer.** Across 42 apps with a described ATT screen in Lazyweb Research's corpus, personalization framing (personalized ads/recommendations/shopping) appears in 23 apps (55%) versus 10 (24%) that promise better deals, offers, or discounts [1]. Personalization is the majority frame by more than 2 to 1. Choose deals framing only if your app has a genuine commerce or savings hook.

> ATT prompts use personalization framing more than twice as often as deals framing — 23 vs 10 of 42 apps — Lazyweb Research, July 2026.

## The finding

Among 42 ATT apps with descriptions, 23 (55%) frame tracking as personalization and 10 (24%) frame it as better deals, offers, or discounts [1]. These are not mutually exclusive per app, but personalization is clearly the default justification and deals the specialized commerce hook.

## The two frames side by side

| Frame | Apps | Share | When it fits |
|---|---|---|---|
| Personalization [1] | 23 / 42 | 55% | Content, ads, or recommendation-driven apps |
| Better deals / offers [1] | 10 / 42 | 24% | Retail, commerce, savings apps |

Back Market blends both — its explainer frames tracking as best deals plus app-improvement analytics plus relevant ads [2]. Chewy leans personalization: tracking personalizes items, offers, and ads [2].

## How to apply it

Default to personalization — it is the corpus's dominant, low-friction frame and works for almost any app. Reach for the deals/offers angle (24% of apps) only when it is true: a retail or savings product where 'better deals' is a concrete, believable payoff. Combining both, as Back Market does, is a viable pattern for commerce apps [2].

## Caveats

Based on 42 apps with descriptions; framing is per-app regex matching on captured copy, not measured opt-in lift [1]. An app can use both frames, so shares sum above the app count. Named examples are illustrative, not proof of superiority.

## The numbers

| Stat | Computed from |
| --- | --- |
| personalization 23/42 (55%), deals/offers 10/42 (24%) | att_wording_patterns: per-company bool_or of personalization and deals regexes over ATT screen set |
| Named examples: Back Market (deals + analytics + ads), Chewy (personalizes items/offers/ads) | qualitative: backmarket, chewy ATT explainers |

## Methodology

Universe: 42 apps with a described ATT screen (of 807), July 2026. Framing via per-app vision-description regexes; frames overlap, and shares describe observed copy, not opt-in lift.

## Sources & citations

- [1] Lazyweb Research analysis of 42 apps (ATT-with-descriptions set, 807-app corpus), July 2026. Personalization and deals framing via vision-description regexes; frames not mutually exclusive.
- [2] Lazyweb Research qualitative review (807-app corpus), July 2026. Back Market and Chewy cited as named ATT-framing examples.

## Related questions

- [How Do Apps Word ATT Tracking Prompts?](https://www.lazyweb.com/research/how-apps-word-att-tracking-prompts)
- [When Do Apps Fire the ATT Prompt in Onboarding?](https://www.lazyweb.com/research/when-apps-fire-att-prompt-in-onboarding)
- [What Percentage of Apps Show a Custom Explainer Before the Native ATT Dialog?](https://www.lazyweb.com/research/att-custom-explainer-before-native-dialog)