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

上架通

GOEE LISTING LEDGER

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


2026-02-24

Ad SDKs and Data Safety: map fields to vendor docs

After AdMob, mediation, or MMP SDKs, Play Data safety often misses device IDs and interaction data. Build a vendor-to-form mapping table. Telegram @hagee66.

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

After AdMob, international networks, Meta Audience Network, or MMP attribution SDKs, Play Console Data safety often shows “SDK in the APK, no matching data types in the form.” Collection is scattered across the SDK, mediation adapters, analytics coupling, and device advertising ID. In review and user reports, declarations that don’t match real behavior are harder to defend than crashes. This guide shows how to map vendor documentation to Play fields and align with SDK disclosure and privacy labels on both stores. Form fields and enums change—follow Play Console and each SDK’s current docs. Correct filing does not guarantee approval. Goee: goee.cc · Telegram @hagee66.

What this guide solves

  • Only “Advertising or marketing” is checked; device ID, coarse location, or in-app interaction details are missing.
  • Five mediation networks are live; Data safety names only the first.
  • Attribution and ad SDKs double-report or leave gaps.
  • Personalized ads are off but SDKs still init; the form says “no collection.”
  • iOS nutrition labels and Android Data safety tell different stories for the same SDK.

Who should read

Role Job
Android engineering Ad/attribution packages in the dependency tree
Growth / ad ops Waterfall or bidding networks actually enabled
Listing execution Fill Data safety; check store copy
iOS counterpart Cross-check ads privacy labels

Base inventory: SDK disclosure checklist; ATT: ATT prompt.

Core approach

Step 1: Lock SDKs that truly run in release

Not “appeared in Gradle once”—this release build initializes and may send requests:

  1. Export release dependency tree or SBOM.
  2. Code review: what runs in Application.onCreate or first screen.
  3. List each mediation adapter—one missing row is one leak.
  4. Record versions so the map traces “1.3.0 (412) used what.”

Step 2: Read vendor Data safety / privacy sections

Official docs usually list:

  • Data types collected
  • Purposes (ads, analytics, fraud, etc.)
  • Whether linked to identifiable users
  • Tracking (on iOS, also ATT)

Do not rely on third-party blogs. Archive links in the mapping table.

Step 3: Build “SDK → Play field” map

Play uses fixed data types and purpose enums:

Column Content
SDK name + version e.g. Ads SDK 23.x
Vendor doc URL Archive date
Types (vendor wording) Short quote
Play Data safety item Official enum
Purpose Ads, analytics, etc.
Shared with third parties Per doc and contract
Optional / user control CMP, personalization toggle
Verified by Eng + listing co-sign

When several SDKs collect the same type, merge disclosure in the form; keep source SDK list in the map.

Step 4: Sample behavior in the build

  • Packet capture or SDK debug mode (if offered).
  • Fresh install: after opting out of personalized ads (if any), are IDs still sent—match declaration.
  • Kids/family products: should ad SDKs be off—see kids category guides.

Step 5: Cross-check iOS privacy labels

Maintain one data type × platform form master sheet. Same product on both stores—avoid iOS “used for tracking” vs Android “not tracking.” Apple: ads nutrition labels and privacy labels overview.

Often-missed types (conceptual)

Common gaps in ad apps—confirm with vendor docs and device tests:

  • Advertising ID / device or other IDs
  • Coarse location, IP-inferred place
  • App interactions, diagnostics (crashes carried by ad SDK)
  • Performance data (some SDKs)
  • Financial info (only if SDK touches; pure display often does not)

“Does not collect personal data” is rare with mainstream ad SDKs; don’t default-check it.

Update cadence

  • Each major ad SDK upgrade → reread privacy release notes → update form.
  • Each new mediation network → treat as new SDK.
  • Note Data safety edit date in the same release memo as the store release.

Copy-paste templates

Ad SDK mapping (CSV header)

sdk_name,version,mediation_adapter,doc_url,doc_date,data_collected_vendor,play_data_type,purpose,shared,sdk_init_in_release,verified_by,notes

Data Safety change ticket

【Data Safety change】
App:
versionCode:
Reason: new SDK / upgrade / ads off / new permission
New data types (Play enums):
Removed or narrowed (if any):
User controls (personalization / CMP):
Privacy policy section:
iOS label updated: yes / no / n/a
Review (engineering):
Review (listing):
Upload date:

Pre-release ad declaration checklist

□ Dependency tree matches mapping SDK list
□ No mediation subnet missing
□ Vendor doc links reviewed within 90 days
□ On-device sample matches advertising ID declaration
□ Privacy policy mentions ads and third parties
□ No fight with iOS nutrition label

Common mistakes

  1. Disclose AdMob only, not adapters.
  2. Form copied from last quarter; SDK bumped three versions.
  3. “No collection” but AD_ID permission declared.
  4. Test track has no ads, production does—form follows test.
  5. MMP treated as analytics only, ad purpose omitted.
  6. One aggregation row hides many ADKs.
  7. CMP banner assumed to replace Data safety updates.

Q&A

Tiny banner still needs full table?
If release initializes and may request ads, disclose per docs; size doesn’t exempt.

Ads off in CN, on internationally—how to file?
Follow actual countries and build behavior; if one global build inits SDKs, disclose conservatively.

After Google UMP/CMP—what changes?
Document user choice; form changes only if data really stops—verify on device.

Split from privacy policy for stores?
Policy is user narrative; Data safety is structured Console fields—they must agree.

Can Goee file and guarantee approval?
No. We can help align mapping; review is up to Google.

House ads only?
If truly static self-owned with no third-party SDK, may simplify; if ad SDK renders, file as usual.

Next steps

  1. Export list from SDK disclosure checklist; add ads sub-sheet.
  2. Fill first mapping CSV; dual sign-off.
  3. Read ads privacy labels for cross-store table.
  4. Next ad SDK upgrade → change ticket process.
  5. Bundle with Google Play materials and precheck.

Related reading

Back to guide library · Google listing · Telegram @hagee66