Google Replaces AdSense Age Tags With New TFAT Signal: What Publishers Must Do Now

Google has officially introduced a new AdSense compliance signal called Tag for Age Treatment (TFAT), replacing the older age-related ad settings that publishers have relied on for years. The announcement, published on May 18, 2026, marks a significant shift in how ad platforms handle age-based ad protections, and it requires action from every publisher running AdSense on their website or app.

What Is TFAT and Why Does It Matter?

TFAT is Google's unified solution to a growing patchwork of global age-related privacy laws. Regulations like the EU's GDPR, the US children's privacy law COPPA, and newer US State App Store Bills have created compliance pressure on publishers to correctly identify and restrict ads served to children and teenagers.

Previously, publishers used two separate tags to handle this:

1. tagForChildDirectedTreatment (TFCD) - flagged content directed at children.
2. tagForUnderAgeOfConsent (TFUA) - flagged users under the age of consent in relevant regions.

TFAT replaces both with a single, cleaner API signal that covers more age groups and is built to scale with future regulations.

The Three TFAT Values Explained

TFAT introduces three settings publishers can pass in their ad requests:

1. CHILD - Functionally replaces TFCD and TFUA when set to true. Use this when your content is directed at children.
2. TEEN (New) - A brand-new category. This applies specific ad-serving protections for teenage users, a group previously not explicitly covered by a dedicated signal.
3. UNSPECIFIED - The default state, equivalent to not setting TFCD or TFUA. Importantly, passing UNSPECIFIED does not override existing user privacy consent strings such as TCF or GPP; Google will still apply the most conservative restriction available.

What Action Do Publishers Need to Take?

Google has made clear that technical updates are required. Publishers must replace the deprecated TFCD and TFUA tags with the new TFAT parameter in:

1. Google Publisher Tag (GPT) - for web-based AdSense implementations.
2. Google Mobile Ads SDK (GMA) and IMA SDK - for mobile app publishers.

These updates will be rolled out in upcoming versions of GPT and the respective SDKs. Google has not yet announced a specific deprecation deadline, but publishers are advised to migrate early to avoid losing access to new AdSense features.

What Happens If You Do Nothing?

Publishers who do not migrate from the legacy tags risk falling out of compliance with age-related regulations and may lose access to features in future GPT and SDK releases. For bloggers and site owners monetising content that could reach younger audiences, this is not optional housekeeping, it is a regulatory requirement.

Key Takeaway for Ghanaian Publishers

If you run a website or app monetised with Google AdSense, now is the time to review your ad tag implementation. Whether you manage your tags directly or through a CMS plugin, check with your developer or ad management partner to ensure your setup is ready for TFAT before the legacy tags are formally deprecated.

For full technical details, visit the official Google AdSense Help announcement.