Verify Your Setup
TapMind trust and compliance information for publishers' engineers.
Verifying your setup (inspection mode)
Ask your account manager to raise the inspection level for a test device (it reverts automatically after seven days). Then:
Level 1 — debug log. Each ad request logs one line, for example:
TapMind Privacy · state=present cmp=300 gdpr=1 gpp_sid=7_8 usp=- pub=gdpr:1 att=- age=0 permit=ifa:1/strip:0/v:2026.09.1 tier=L3 gate=pass(7)state is absent / pending / present; cmp is your CMP's IAB ID; gate shows whether the advertising identifier was attached and, if not, which check failed (1 feature not enabled for the app · 2 TapMind policy for this country · 3–4 child or Families flag · 5a TCF purpose 1 not consented · 5b TapMind vendor bit absent · 6 platform read unavailable · 7 user limited ad tracking).
Level 2 — getPrivacyState(). Returns the same fields as a struct plus the IAB keys found and, once TapMind is registered, whether TapMind's vendor bit is present in your CMP's consent string — the "is TapMind listed in my CMP?" check.
Troubleshooting
Scroll horizontally to view all columns on smaller screens.
| Symptom | Likely cause |
|---|---|
| Ads serve but are never personalised | Read gate and permit: feature not enabled, country policy, or no consent signal |
| state=pending on every request | Your CMP is not resolving before the first ad request; check its initialisation order |
| gate=fail(5b) | TapMind is not in your CMP's vendor list; add it |
| age=1 unexpectedly | A child-directed or under-age flag is set on Google Mobile Ads' RequestConfiguration, or via the consent API |
The log never contains the advertising identifier or consent strings.