Google replaces TFCD/TFUA with TFAT age treatment tag
Google AdSense Help announcement dated 18 May 2026 introduces Tag for age treatment (TFAT) with CHILD/TEEN/UNSPECIFIED values, replacing TFCD and TFUA.
On 18 May 2026 Google published New signal for age-related compliance: Tag for age treatment (TFAT). The announcement frames TFAT as a unified way to manage ad-request protections for different age groups amid US state app-store bills, GDPR and COPPA. TFAT replaces legacy tagForChildDirectedTreatment (TFCD) and tagForUnderAgeOfConsent (TFUA), which will be deprecated in future GPT or SDK versions that support TFAT.
Values
- CHILD — functionally replaces TFCD/TFUA=True
- TEEN — new tier for teen-specific ad-serving protections
- UNSPECIFIED — default, equivalent to TFCD/TFUA=No or UNSPECIFIED; does not override TCF/GPP or other sensitive-user signals; Google still applies the most conservative restriction present
Publisher action is required to migrate web (GPT) and app (GMA and IMA SDK) integrations. Ad Manager help likewise states TFCD/TFUA are deprecated in favour of TFAT, and that if both legacy and TFAT settings are passed Google applies the most conservative treatment.
Operator action
| Field | Evidence |
|---|---|
| Announcement | 2026-05-18 |
| Replaces | TFCD and TFUA |
| Values | CHILD / TEEN / UNSPECIFIED |
| Surfaces named | GPT; GMA SDK; IMA SDK |
| UA implication | Mediation and demand partners must pass the new age-treatment signal on game inventory |
Confirm SDK/GPT minimum versions in your mediation stack before cutting over. Pair with Declared Age Range / state age-assurance workstreams so CHILD vs TEEN mapping matches product policy.
