INDEPENDENT MINDS. SHARED AMBITION.
Back to the newsfeed
Measurement2 min read

Measurement · Status at source date: Update

Tag Manager counts back-forward-cache page views, a BigQuery export stall and a Search Console AI-report bug

Written by Paid Media Collective
IN BRIEF

Three smaller items for measurement teams.

Tag Manager counts back-forward-cache page views, a BigQuery export stall and a Search Console AI-report bug ; source illustration
LinkedInView full-size image

What changed

For you, this means distinguishing Google’s confirmed Search Console logging incident from a single-property BigQuery observation, and annotating only the dates and systems actually affected.

- Tag Manager, 9 November release note: web tags subscribed to "page view on history change" now record a page view when a page is restored from the browser's back/forward cache. - GA4 to BigQuery: Matteo Zambon reports a property whose daily export stalled at 10 November while intraday tables kept arriving; no Google incident was logged. Google’s three-day late-event update window is not a guaranteed 72-hour export-delivery SLA; the root cause and current resolution remain unverified. - Search Console: Google confirmed a logging error that lowered impressions in the Generative AI performance report for 9–11 November; it affects logging only.

The three items affect different parts of the measurement chain. Back-forward-cache handling concerns page-view collection, a BigQuery export stall concerns data delivery, and an AI-report bug concerns the presentation of information in Search Console. A single reporting discrepancy may involve only one of them.

For the cache-related change, verify the events generated when a visitor returns through browser navigation. Compare the observed request behaviour with the site's intended page-view definition. A change in recorded page views should not automatically be interpreted as a change in the number of people visiting the site.

For a stalled export, inspect the relevant tables and dates before running downstream reports. Preserve the last successful data and make missing periods explicit. A dashboard that refreshes successfully can still be based on an incomplete export if the pipeline does not check the expected records.

For the Search Console issue, distinguish a display or report-generation problem from a change in search traffic. Keep the platform notice alongside the affected report and avoid rewriting campaign or organic-search strategy from a temporary interface anomaly. These are separate operational checks, with different owners and evidence, rather than one broad claim that all Google measurement changed at once.

Sources & contributor credit

  1. Original sourceGoogle Tag Manager release notes

  2. Supporting sourceLinkedIn

  3. Supporting sourceSearch Engine Roundtable

Original creator unverified

Credits reflect the editor's latest changes. Original authorship has not been independently verified for this version.

Attribution evidence and limitations

Full attribution review pending.

A source link alone does not establish original authorship.

Original image and video creators have not yet been verified.

FOLLOW THE PEOPLE BEHIND THIS UPDATE
Published on this site
Article updated

This update reflects the dated source reporting. Availability may have changed. Further coverage of this same development will be added to this page.

Explore the source reporting