feedsmerchant-centermeasurement

Merchant Center reporting changes on August 24, 2026: how to protect your baselines

Merchant Center changed YouTube and ads product reporting on August 24, 2026. Preserve old extracts and separate definition breaks from performance changes.

The short version

Google Merchant Center changed product-performance reporting on August 24, 2026. The update moved some YouTube traffic out of Organic, restated closed historical dates, and expanded ads product reporting.

Preserve any extract pulled before the change, record the definitions used by every report, and split comparisons at August 24. If no pre-change snapshot exists, do not manufacture a continuous baseline from exports pulled under different definitions.

What changed on August 24

Merchant Center now reports YouTube affiliate interactions under a separate Youtube affiliate traffic value instead of Organic. Products that are not eligible for affiliate commission remain under Organic.

Google also aligned YouTube organic click and impression definitions with YouTube reporting standards. Both YouTube changes were applied retroactively to Merchant Center data from July 1, 2026. An extract pulled after the rollout can therefore disagree with an earlier extract for the same closed dates.

Ads product-level reporting expanded across all ads channels and formats. Google specifically includes every Performance Max network plus Video, App and Demand Gen. That wider scope can create a one-time increase in impressions, clicks and related metrics.

Google lists only the YouTube affiliate split and YouTube organic-definition update as retroactive. The ads reporting expansion is not listed among the historical restatements.

Preserve the evidence you still have

  1. Keep pre-change extracts immutable. Preserve product-performance files pulled through August 23, including traffic source, interaction type and network dimensions.
  2. Record each extract's definitions. Keep the query, filters, dimensions, timezone and pull date beside the file. A metric name alone does not preserve comparability.
  3. Annotate reports at August 24. Mark the definition break in dashboards used for feed, merchandising and campaign decisions.
  4. Separate YouTube affiliate from Organic. Update logic that still treats all Organic traffic as free-listing performance.
  5. Build a like-for-like ads view. Where possible, restrict both periods to identical networks and formats so wider reporting coverage is not mistaken for campaign growth.

If no pre-change export exists, document that limitation. A new extract of July data may already contain Google's restatement and cannot recreate what an earlier report showed.

How to read post-change reports

A drop in Organic traffic may be reclassification, not lost demand. Check whether the new YouTube affiliate row absorbed the difference and whether July 1 onward history was restated.

A jump in ads impressions or clicks may be broader product-level coverage, not improved serving. Compare identical networks and formats before attributing the step to bids, budgets, feed quality or merchandising.

Do not use a time series crossing August 24 to diagnose a feed change until both periods use the same reporting definitions. Split the series at the discontinuity or re-cut both windows like for like.

Verify your reporting migration

For one closed week before and one closed week after August 24:

  • save the pull time, timezone, dimensions and filters;
  • compare Organic plus Youtube affiliate with the old Organic definition where an earlier extract exists;
  • isolate identical ad networks and formats;
  • explain any remaining discontinuity before changing feeds, bids or budgets;
  • keep the original extracts beside the reconciled report.

The migration is complete when operators can identify the definition used by each series and no dashboard treats a reporting-coverage change as a business-performance change.

Sources