Google announced on May 18, 2026 a new age-related compliance signal for publishers called the Tag for age treatment, or TFAT, which will replace the long-standing tagForChildDirectedTreatment (TFCD) and tagForUnderAgeOfConsent (TFUA) settings in upcoming versions of the Google Publisher Tag (GPT), the Google Mobile Ads (GMA) SDK, and the Interactive Media Ads (IMA) SDK.

The change, posted to the Google AdSense Help announcements channel, consolidates two legacy signals into one unified API. It also introduces a third, previously unavailable, age category aimed specifically at users between the digital age of consent and 18 years old. According to the announcement, TFAT was designed to help publishers "navigate evolving global age-related regulations (such as US State App Store Bills, GDPR, and COPPA)" and provide "a unified way to manage ad request protections for different age groups."

The new tag carries three permitted values: CHILD, TEEN and UNSPECIFIED. Each maps to a specific ad-serving treatment that publishers must now configure manually in their tag implementations.

How TFAT replaces TFCD and TFUA

For more than a decade, publishers have managed compliance for younger audiences using two parallel settings. The first, tagForChildDirectedTreatment, was tied primarily to the United States Children's Online Privacy Protection Act. The second, tagForUnderAgeOfConsent, was used for publishers covered by the European Union's General Data Protection Regulation and addressed users under the local digital age of consent, which varies between 13 and 16 across member states.

Both signals operated as boolean values. A publisher would either set them to true, false, or leave them undefined. That binary model created friction when publishers tried to apply different protections to different audience segments within the same property, particularly when content reached children, teens, and adults through the same ad units.

Under TFAT, the structure changes. According to the announcement, the CHILD value "functionally replaces TFCD/TFUA=True", meaning publishers signalling child-directed treatment under the previous tags will move to the new CHILD value with equivalent ad-serving consequences. The UNSPECIFIED value mirrors the prior default state, equivalent to TFCD or TFUA being set to No or left undefined.

The TEEN value is the substantive addition. Publishers can now pass an explicit signal indicating that an ad request targets a user covered by teen-specific ad-serving protections, rather than treating the request as either fully child-directed or fully unrestricted. Google's announcement describes this as a tier that "applies to specific ad-serving protections for teens", though it did not publish the full list of category restrictions associated with the new value in the help center post.

The behaviour of UNSPECIFIED is also clarified in the announcement. Passing UNSPECIFIED, according to the documentation, "does not override user privacy consent strings (TCF/GPP) or other indications of sensitive users or content." Google added that the system "will still apply the most conservative restriction present." In practical terms, this means a publisher leaving TFAT unspecified is not signalling that the request is unrestricted - the platform continues to honour any other regulatory or consent-based signal received in the same ad request.

Why a TEEN tier appears now

Google's existing advertising policies have distinguished between users under the digital age of consent and users between that age and 18 since at least January 2025, when the company consolidated its protections for minors into a single policy hub. According to PPC Land's coverage at the time, the consolidated Ad-serving protections for teens policy restricted categories including adult content, alcohol, tobacco, recreational drugs, body modification, weight loss, dating services, and gambling for users above the digital age of consent but under 18.

Until now, however, publishers had no clean tagging mechanism to signal teen-specific status. The choice was binary: either treat a request as child-directed under TFCD or TFUA, or leave it untagged and rely on Google's own inference from content classification, account signals, and other contextual data. In July 2025, Google began deploying machine learning age detection in the United States to identify likely minors based on search patterns and content engagement, automatically disabling personalisation and restricting sensitive categories when the model flagged a user as potentially under 18.

TFAT moves part of that determination back into the publisher's hands. Where a publisher already knows - through account registration data, age gates, or other first-party signals - that a user falls into the teen band, the new value provides an explicit channel for transmitting that information to Google's ad serving systems without conflating it with child-directed treatment.

The announcement explicitly names three categories of regulation driving the redesign: US State App Store Bills, GDPR, and COPPA. Each has shifted significantly in the months preceding the May 18 update.

In the United States, the COPPA rule received its most substantial revision in over a decade. The amended COPPA rule took effect on June 23, 2025, introducing separate consent requirements for third-party data sharing involving children's data and an expanded definition of child-directed services. The compliance deadline for full implementation falls on April 22, 2026. Enforcement has accelerated alongside the rule change. The Federal Trade Commission sued TikTok in August 2024, and Disney agreed in September 2025 to pay $10 million for failing to designate child-directed content as Made for Kids on YouTube, an enforcement action that demonstrated how content designation systems intended to protect children can fail when companies prioritise operational efficiency over individual content assessment.

In February 2026, the FTC issued a policy statement granting age-verification technology a conditional enforcement shield under COPPA, offering mixed-audience and general-audience operators conditional protection when collecting data solely for age-verification purposes. That development encouraged broader adoption of age determination mechanisms across the ad-supported internet.

On the state level, app store age verification laws have multiplied. Utah, Louisiana, and Texas have each introduced legislation imposing age verification obligations on platforms or app stores, with varying scope. The Texas Securing Children Online through Parental Empowerment Act was paused by a federal court injunction in late 2025, but other state statutes remain in force or are scheduled to take effect.

In Europe, the regulatory environment has tightened in parallel. Germany's independent data protection authorities issued a resolution on November 20, 2025 calling for amendments to the GDPR that would prohibit children's consent to data processing for advertising purposes and for the creation of personality or user profiles. The proposed Article 8 amendment would insert binding language stating that the processing of a child's personal data for advertising purposes and for the creation of personality and user profiles is not permitted.

Article 28(2) of the Digital Services Act already prohibits displaying personalised advertising to children on online platforms in the EU. The combined effect of DSA enforcement, GDPR reinterpretation, and the EU age verification deployment scheduled through 2026 has put pressure on advertising platforms to provide more granular technical controls for age-related ad serving.

Technical implementation and migration path

For publishers, the practical consequence of the announcement is a required migration. Google's note states that the legacy TFCD and TFUA settings "will be deprecated in future GPT or SDK versions that support TFAT." The announcement does not specify a hard cutoff date, but it makes clear that publishers running the new versions of GPT, GMA SDK or IMA SDK will need to switch.

Publishers running tag-based web inventory through Google Publisher Tag will need to replace any existing setForChildDirectedTreatment or setForUnderAgeOfConsent calls in their tag code with the new age treatment API once the corresponding GPT version is released. Mobile applications using the Google Mobile Ads SDK for AdMob inventory or the IMA SDK for video ad serving will need equivalent updates in their app builds.

The behaviour around the UNSPECIFIED default carries operational significance. Publishers that do not actively migrate their tags before the deprecated settings are removed will fall back to UNSPECIFIED behaviour. According to the announcement, that fallback does not strip user-level protections that come from other signals - the TCF string under the Transparency and Consent Framework, the Global Privacy Platform (GPP) string, or content-level classifications continue to be honoured. However, publishers who currently rely on TFCD or TFUA as their primary mechanism for signalling child-directed treatment may see ad requests treated less restrictively if the migration is missed.

The interaction with the Transparency and Consent Framework is notable in the timing. Google's TCF v2.3 migration deadline was set for February 28, 2026, and the framework became mandatory on March 1, 2026, with non-compliant publishers risking ad requests defaulting to limited ads or being dropped entirely. The TFAT rollout layers on top of an already active TCF v2.3 environment, meaning publishers in the European Economic Area, the UK and Switzerland operate under both consent string requirements and age treatment tagging requirements simultaneously.

The Global Privacy Platform string, referenced alongside TCF in the announcement, governs consent signals in jurisdictions including the United States and is the technical mechanism through which state-level privacy laws are propagated into the ad tech supply chain. By referencing both TCF and GPP, Google is signalling that TFAT operates as a complementary layer rather than as a substitute for consent string mechanisms.

What happens for publishers who do not act

The announcement is explicit about the requirement: "Technical updates are needed to replace the deprecated tags with the new age treatment API in upcoming web (GPT) and app (GMA and IMA SDK) releases to facilitate compliance efforts and maintain access to the latest features."

Two consequences follow from that statement. First, compliance with the underlying regulations remains the publisher's legal responsibility, and the older tags will not be supported indefinitely. Second, publishers who do not migrate may lose access to feature updates that depend on the new tag API. Google does not specify which features those might be, but historically tag migrations of this kind have gated access to new format support, new measurement signals, and new monetisation features.

The change arrives in a period where publishers are already managing multiple parallel migrations. In addition to TCF v2.3, Google moved Tag Manager inside Ads Data Manager in May 2026, and released version 1.6 of the Data Manager API on May 7, 2026 with expanded ingestion for store sales and Analytics events. The TFAT announcement adds another item to the technical migration backlog for ad operations teams.

Marketing community implications

For advertisers buying through Google's stack - Display & Video 360, Google Ads, and YouTube reservation channels - TFAT changes do not require direct action. The signal is set by publishers on the sell side and consumed by Google's ad serving infrastructure to determine which creatives and which auction participants are eligible.

The downstream effect is on inventory composition. Publishers using the new TEEN value to signal teen-specific requests will trigger the restricted category list that already applies under Google's Ad-serving protections for teens policy. Advertisers in restricted verticals - alcohol, gambling, body modification, weight loss, dating, and others - will see reduced eligibility on inventory tagged as TEEN, even where the user is above the digital age of consent.

For ad tech intermediaries participating in Google's open auction and Open Bidding programmes, the new signal becomes another data point in the bid request. Authorised Buyers, Open Bidding partners, and SDK Bidders will receive ad requests that carry TFAT values in addition to the existing TCF and GPP consent strings. Bidders that maintain category-level filtering logic on their side will need to incorporate the new value into their decisioning to avoid bidding on restricted inventory.

For publishers running mixed-audience properties - a category that has been the subject of significant FTC attention under the amended COPPA rule - the introduction of TFAT offers a more granular way to signal audience characteristics on a per-request basis. Properties that were previously treating all requests as either child-directed or general can now distinguish three states based on first-party knowledge of the user.

Timeline

Summary

Who: Google, through its AdSense Help announcements channel, addressing publishers using Google Publisher Tag, the Google Mobile Ads SDK, and the IMA SDK. The change affects all participants in Google's advertising ecosystem, including AdSense and Ad Manager publishers, AdMob app developers, and ad tech intermediaries connected through Authorized Buyers and Open Bidding programmes.

What: The introduction of the Tag for age treatment (TFAT), a new unified signal that replaces the legacy tagForChildDirectedTreatment (TFCD) and tagForUnderAgeOfConsent (TFUA) settings. TFAT carries three permitted values: CHILD (functionally replacing TFCD/TFUA=True), TEEN (a new tier signalling teen-specific ad-serving protections), and UNSPECIFIED (the default state, equivalent to TFCD/TFUA=No, which does not override consent strings or other regulatory signals).

When: Google posted the announcement on May 18, 2026 in the AdSense Help announcements section. The legacy TFCD and TFUA settings will be deprecated in future versions of GPT, GMA SDK, and IMA SDK that support TFAT. No specific deprecation date was given.

Where: The change applies globally to publishers using Google's web and app advertising tags. The underlying regulatory drivers cited by Google include US State App Store Bills, the EU General Data Protection Regulation, and the US Children's Online Privacy Protection Act.

Why: The announcement frames TFAT as a response to evolving global age-related regulations. The unified API consolidates two legacy boolean settings into a tiered model that distinguishes between children, teens, and unspecified users, providing publishers with a more granular technical mechanism to signal age-based ad serving treatment as enforcement intensifies under COPPA, GDPR, the Digital Services Act, and emerging US state app store legislation.

Share this article
The link has been copied!