App Store / Google Play · 清单验收 · 不承诺过审Telegram @hagee66

上架通

GOEE LISTING LEDGER

№ ENgoee.cc
账号归你 · 邀请协作


2026-04-13

ATT and the tracking prompt: timing and ad SDK alignment

App Tracking Transparency timing, copy, consistency with privacy label Tracking; behavior after users deny tracking. Telegram @hagee66.

This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66

iOS apps with ads, attribution, or cross-app measurement often walk a line between “request tracking” and respecting denial: prompt too early → all taps deny; too late → review says you never asked; nutrition label claims tracking without ATT; after deny, IDFA still read. Goee (goee.cc) treats ATT as NSUserTrackingUsageDescription + nutrition label + SDK init order. Overview privacy labels; ads privacy nutrition ads and Data Safety ads SDKs; purpose strings iOS permission strings. ATT and IDFA rules per official pages.

What this guide solves

  • ATT on cold start before value is shown.
  • No ATT framework but collectible cross-app identifiers.
  • After deny, ad SDK still initializes as if opted in.
  • Nutrition label “tracking” contradicts forms/notes.
  • Pre-prompt scares or bribes “you must allow.”
  • iPad vs iPhone behavior mismatch.

Who should read

Role Focus
iOS ATTrackingManager timing
Growth Honest pre-prompt copy
Ad ops Mediation no-IDFA config
Listing Notes with test path

Required when first adding AdMob, AppsFlyer, Adjust, etc., or changing tracking disclosure.

Core practice

When to request

Timing Quality
First second of cold start Poor
After “support the app” education OK
Moment before first personalized ad Common recommendation
Settings “ad preferences” → system Secondary entry

Short pre-prompt before system dialog is OK; “Continue” then requestTrackingAuthorization. Do not mimic system Settings UI.

SDK alignment

  1. Which SDKs may send IDFA after ATT denied—upgrade or disable modules.
  2. SKAdNetwork IDs in Info.plist per ad network docs.
  3. Nutrition label tracking answers match real processing.
  4. Test: deny ATT → packet capture should not show plaintext IDFA (per your disclosure).

After deny

Capability Guidance
Ads Contextual or non-personalized fill
Attribution SKAN / network privacy paths
Analytics In-app events without cross-app IDs
UI Do not nag to reopen ATT

Copy-paste templates

Pre-prompt skeleton

Title: About ads and privacy
Body: Ads support free features. You may allow identifiers for more relevant ads, or decline and still use the app with less relevant ads.
Primary: Continue → [then ATT]
Secondary: Not now

Test log

Build:
A — Allow: ad requests use SKAdNetwork, no crash
B — Deny: 3 launches, no forced re-prompt
C — Limit Ad Tracking (system) same as B
Nutrition tracking fields: checked
Notes written: Y

Review notes excerpt

ATT is requested before the first personalized ad on Home feed.
To test deny: Settings → Privacy → Tracking → off for this app, relaunch.
NSUserTrackingUsageDescription: "[exact string in build]".

Common mistakes

  1. IDFV as “no tracking” while doing ad targeting externally.
  2. Label says no; ad SDK full on.
  3. Kids app with tracking-required networks.
  4. Notes tell reviewer to flip global tracking without in-app path.
  5. ATT only in TestFlight, missing in App Store build.
  6. EU DMA / consent flows mixed with ATT—legal owns separation.

FAQ

No ads—still ATT?
If no cross-app tracking and SDKs never touch IDFA, maybe not—inventory decides.

Pre-prompt required?
No, but often improves opt-in; must be truthful.

Opt-in crashed—force re-prompt?
Repeated prompts risk policy issues; improve value prop and non-personalized fill.

Relation to UMP (Google consent)?
May run in parallel in EU; roles per official docs.

Goee configures SDKs?
Checklist help—no approval promise.

SKAdNetwork and postbacks

Even when ATT denied, SKAN may aggregate conversions. Update SKAdNetworkItems per latest SDK list—stale config is common debt. Product: reporting latency/granularity changed—do not promise IDFA-era real-time sales metrics.

Kids and parental controls

Kids or kid-attractive apps face tighter ad/tracking rules; programs per official pages. Do not use adult gate to show adult ad stream to review.

Retest matrix

Setting Expected
Allow tracking ATT before first ad; authorized
Deny tracking No IDFA targeting; app usable
Limit Ad Tracking Like deny; no crash
Reinstall No triple ATT in first seconds

Re-run on iOS SDK or mediation upgrades.

Execution rhythm

Ad SDK upgrades often change ATT behavior—same week run allow/deny paths and update nutrition label. Do not flip “force ATT” experiments before big promos. Review with privacy nutrition ads. EU CMP order is legal, not guessed here.

Metrics without coercing review

Track IDFA opt-in, but do not deceptive-force Settings for KPIs—hurts trust, reviews, and may trigger policy questions. Separate dashboards from compliance checklist.

No ads but attribution SDK for acquisition: still inventory tracking definition and label honesty—“channel stats only” is not automatic exemption. Test with Limit Ad Tracking on. Feature flags: ads.personalized.enabled—no hidden gestures.

Joint acceptance with privacy label

On submit day, print nutrition label PDF beside NSUserTrackingUsageDescription—both acknowledge ad-related identifiers? If label says no tracking but cross-app ad SDK exists, fix declaration or remove capability. Reuse privacy labels cross-check plus ATT allow/deny screen recordings in precheck archive.

Internal review and boundaries

Listing is delivery, not legal final. Policy changes—official pages. Defect vs wording: code vs notes. Telegram @hagee66 with build and checklist. No approval promise; no hidden features or anti-review tactics.

Check Goee Client
Path/notes Yes Demo account
Policy URL Yes DNS/certs
Forms vs package Verify SDK table
Legal No Counsel

Next steps

Align with data-safety-ads-sdks cross-platform. Telegram @hagee66. No approval promise—verify ATT timing, label, SDK trilogy.

Back to guide library · Apple listing · Google listing