Why is Yahoo blocking the AMP Client ID API and how does it affect your analytics?

What is the AMP Client ID API and why does it exist?

The AMP Client ID API is a technical mechanism designed to address a fundamental problem: when a user accesses your AMP page from a search engine, they are actually loading a cached version on Google's servers, not directly from your domain. This peculiarity makes traditional tracking through first-party cookies impossible.

The API allows for the creation of a persistent unique identifier that tracks the visitor between the AMP version (served from the cache) and your standard site. Without it, you lose the continuity of sessions: the same user who clicks first on an AMP result and then visits another page on your site will appear as two distinct visitors in your analytics.

What specific issues does Yahoo present?

Yahoo uses the Google AMP cache to serve accelerated pages in its search results but has not implemented support for the AMP Client ID API. The technical reason remains unclear—Google does not specify if this is a voluntary limitation by Yahoo or an infrastructure constraint.

The practical outcome is harsh: all Yahoo traffic to your AMP pages becomes impossible to track correctly with standard tools. You lose not only the reconciliation of sessions but also the ability to accurately measure conversions, actual time spent, or complete user journeys for this traffic segment.

How many sites are actually affected?

This question is legitimate. In Europe and most Western markets, Yahoo now accounts for less than 2% of organic searches. Significant Yahoo traffic focuses on specific Asian markets (Taiwan, Hong Kong, Japan) and a few specific verticals in the United States.

If your site generates less than 5% of its SEO traffic via Yahoo, the analytical impact remains negligible. However, for publishers with a substantial Asian audience or certain American news sites, the loss of tracking on this segment can represent tens of thousands of monthly sessions without reliable data.

• The AMP Client ID API reconciles sessions between cached AMP pages and the standard site
• Yahoo uses Google’s AMP cache but does not support this API, breaking tracking
• The impact directly depends on your Yahoo traffic share (negligible for most, critical for certain geographies)
• No clean technical solution: either alternative methods or abandonment of AMP for Yahoo
• Google does not specify if this limitation is temporary or permanent

Does this limitation reveal tensions between Yahoo and Google?

Google's wording remains cautiously technical, but the situation hints at political undertones. Yahoo is a direct competitor in search, even if weakened. The fact that this engine uses Google’s AMP infrastructure while refusing (or being unable) to implement a standard tracking API raises questions.

Two field hypotheses: either Yahoo is voluntarily blocking it for reasons of strategic differentiation and data control, or Google is limiting access to certain advanced features of its cache for third-party actors. No public documentation provides clarification. [To verify] through direct tests with controlled Yahoo traffic.

Is the impact on conversions as dramatic as on analytics?

Let's be honest: losing user tracking does not prevent conversions from actually happening. A Yahoo visitor who makes a purchase on your site after clicking an AMP page still converts. The problem is that you cannot correctly attribute it to the Yahoo source in your traditional analytics tools.

The real loss lies in post-attribution optimization. It becomes impossible to finely analyze Yahoo journeys, identify the AMP content that converts best from this engine, or calculate an accurate ROI on your specific Yahoo SEO efforts. For paid Yahoo campaigns (if you run them), it becomes quite problematic regarding acquisition cost tracking.

Should you disable AMP for Yahoo traffic?

The answer entirely depends on your actual Yahoo volume and your ability to operate with partial data. If Yahoo accounts for less than 3% of your overall SEO traffic, maintaining AMP to enjoy Google's benefits (speed, position in the carousel, etc.) is likely the right choice.

Beyond 10% Yahoo traffic, the question deserves calculation. Some publishers have opted for conditional serving: detecting the Yahoo user-agent and serving the classic HTML version instead of AMP. Technically feasible, but it adds a layer of complexity and potentially slower loading times for these users. Is it worth it? Test, measure the impact specifically on Yahoo engagement before generalizing.

How can you accurately measure your exposure to the problem?

The first step is to quantify the actual share of Yahoo in your organic traffic sources. In Google Analytics, segment your sessions by source/medium for the past 90 days. Filter for AMP sessions only (dimension “AMP Client ID” or URL containing “/amp/”).

Then cross-reference with the referring source. If you find less than 2% of AMP sessions coming from Yahoo, the problem remains theoretical. Between 5 and 15%, you have a significant analytical blind spot. Beyond 20%, you lose a critical optimization capability and need to take action.

What concrete workarounds exist?

Option 1: implement a server-side tracking that does not rely on the AMP Client ID API. This requires logging hits at the server level with persistent session identifiers in URL parameters or via device fingerprinting. More complex, but it circumvents the Yahoo limitation.

Option 2: use custom UTM parameters dynamically injected into AMP links specifically served to Yahoo. Detect the Yahoo referrer server-side, and add a “?source=yahoo_amp” parameter to your AMP internal links. You at least gain source attribution, even if user reconciliation remains broken.

Should you abandon AMP for clean tracking?

This is the major strategic question. AMP is gradually losing its relevance since Core Web Vitals allows for achieving the same ranking benefits with optimized traditional HTML pages. If your tech stack can achieve Lighthouse scores > 90 without AMP, you might consider a gradual exit.

However, be careful: some Google carousels (news, recipes, etc.) still massively favor AMP in certain regions. Test the impact on your Search Console impressions and clicks before globally disabling. An A/B test on a non-critical content segment allows you to assess the consequences without major risk.

• Audit your share of organic Yahoo traffic over 90 days (GA4 or standard Analytics)
• Specifically segment AMP sessions coming from Yahoo to quantify the blind spot
• If > 5% of traffic, implement server-side tracking or specific Yahoo UTM parameters
• Evaluate the technical feasibility of conditional serving (classic HTML for Yahoo, AMP for Google)
• Test the impact of a gradual AMP deactivation on a sample of non-critical content
• Document the limits of your Yahoo data in your executive reports to avoid over-interpretation