Every marketing platform keeps your history for a fixed window and then drops it, and the window keeps moving while you wait. Search Console shows 16 months and no more. GA4 explorations can be set as short as two months. Microsoft Clarity deletes most session recordings after 30 days. This table gives the documented window for 44 datasets on 20 platforms, read from each vendor's own documentation on September 25, 2026, and the export that preserves each one.
The finding that matters most sits in three vendor sentences. The Search Console bulk export's first file contains the day of the export. Bing Webmaster Tools cannot show data from before a site was added. A GA4 BigQuery export paused for exceeding its daily limit does not reprocess the missed days. None of those three recovers any of it. Every week an analytics project waits for a login is a week of the oldest Search Console history gone, and a new user cannot get it back.
- 01The key exports start on the day you set them up and do not backfill.Search Console's bulk export and Bing Webmaster Tools say so in their own documentation, and GA4's BigQuery export documentation describes no backfill. The only way to reach pre-setup Search Console history is the API or the UI, and only inside the 16-month window.
- 02The shortest stored windows are days, not months.Cloudflare Security Analytics on Free and Pro plans keeps 7 days; Microsoft Advertising hourly geographic reports 14 days; Clarity recordings 30 days; BigQuery sandbox tables 60 days; GA4 demographics two months, always.
- 03Two 2026 changes shortened history on the largest ad platforms.Google Ads caps hourly, daily and weekly data at 37 months from June 1, 2026. Meta cut unique-count and hourly breakdowns to 13 months and frequency to 6 from January 12, 2026. Only one vendor-held dataset in the table is kept indefinitely: CrUX on BigQuery.
- 04The day-one checklist is five exports.Bulk export plus a 16-month API pull for Search Console; 14-month retention plus a billed BigQuery link for GA4; add the site to Bing; create YouTube Reporting jobs; favourite the Clarity recordings that matter.
01 — The findingThe exports that save history do not recover it
Google's guide to debugging traffic drops tells site owners to choose "Last 16 months" in the Performance report and, to keep more than that, to use the Search Analytics API or bulk data exports and store the data in their own systems. The bulk export help page then sets the limit: the first export happens up to 48 hours after configuration, and it includes data for the day of the export. For anything earlier, Google points back to the API or the reports.
Google, Search Console bulk export: "The first export includes data for the day of the export." Google, GA4 BigQuery export: "previous days' exports will not be reprocessed." Microsoft, Bing Webmaster Tools: "since data collection starts from the time you first add your website in Bing Webmaster Tools, you cannot see backdated data."
Put the three together and the sequence in a new engagement becomes clear. Access is requested; the oldest month of Search Console history expires while the request sits in someone's inbox; access arrives; the export is switched on and starts from that day. The 16 months visible at that moment are the most the project will ever have, and the API pull that captures them is the first job, not the last. Our client access checklist exists to shorten that wait.
02 — The tableThe table: 44 datasets, the documented window, and how to keep it
"Rolling" means the window moves forward daily or monthly, so the oldest data drops off continuously. "API lookback" means a query limit rather than deletion of the stored data; those rows are excluded from the shortest-windows ranking that follows. Quoted words are the vendor's; everything else is our paraphrase of the page as read on September 25, 2026.
| Platform | Dataset | Window as documented | How to preserve |
|---|---|---|---|
| Google Search Console | Performance report and Search Analytics API | 16 months; the date filter's maximum is "Last 16 months" and older rows drop out of the UI and API. Rolling. | Bulk data export to BigQuery from setup day, or scheduled API pulls stored in your own warehouse. |
| Google Search Console | Bulk data export to BigQuery | No backfill: "The first export includes data for the day of the export." Exported tables are kept forever unless you set an expiration; partition expiration must be 14 days or longer. | Set it up on day one of any engagement; use the API for pre-setup history. |
| Google Search Console | Page indexing report issue history | An issue lives until 90 days after its last instance is marked gone; the 404 list covers about the past month. Rolling. | Export the issue tables at kickoff. |
| Google Search Console | Core Web Vitals report | URL-group values reflect the last 28 days; validation runs a 28-day session. Rolling. | CrUX on BigQuery for monthly history. |
| Google Analytics 4 | Event-level data (Explorations, funnels) | Standard: 2 or 14 months; 360 adds 26, 38 and 50 months. Deleted monthly. Standard aggregated reports are unaffected. Rolling. | Set 14 months on day one; turn on the BigQuery export. |
| Google Analytics 4 | User-level data and key events | 2 or 14 months; optional reset on new activity. Rolling. | Same as event-level data. |
| Google Analytics 4 | Age, gender and interest data | Two months, always, regardless of setting. Rolling. | Export demographic cuts regularly via the Data API or BigQuery. |
| Google Analytics 4 | Google signals data | Maximum 26 months regardless of setting; a shorter setting takes precedence. Rolling. | A cap; not recoverable. |
| Google Analytics 4 | Large and XL properties | When a standard property becomes Large or a 360 property XL, event-level retention is cut to 2 months and older data is permanently deleted. Warning emails precede it. | Cut event volume or move to 360; keep the BigQuery export running. |
| Google Analytics 4 | BigQuery export | Starts after linking, flowing within 24 hours; standard properties get 1 million events a day on the daily export. Paused exports are not reprocessed; no backfill is described. | Link BigQuery at property creation; use streaming above 1 million events a day. |
| Google Cloud | BigQuery sandbox (free tier) | All tables, views and partitions expire after 60 days. Rolling. | Upgrade to billing and remove or extend the default expirations. |
| Universal Analytics | All properties, data and API | Shut down from the week of July 1, 2024; all data deleted. Fixed. | Too late unless already exported to BigQuery. |
| Google Ads | Hourly, daily and weekly reporting data | From June 1, 2026: 37 months. Monthly, quarterly and annual data: 11 years. Rolling. | Scheduled API or report exports at daily granularity. |
| Google Ads | Reach and frequency metrics | Three years. Rolling. | Export reach and frequency reports. |
| Google Ads | Change history (UI) | Past 2 years; older changes are unavailable. Rolling. | Download change history or log change events via the API. |
| Google Ads API | Click-level view (GCLID) | Queries reach back 90 days, one day per query. API lookback. | Daily API pull into your warehouse. |
| Google Ads API | Change event and change status | Change event: past 30 days, 10,000 rows maximum. Change status: past 90 days. API lookback; the UI keeps 2 years. | Daily or weekly API logging. |
| Google Business Profile | Performance metrics (legacy v4 API) | Maximum range 18 months from the request date. The v1 Performance API pages state no limit. | Download report in the UI, or Performance API pulls. |
| Google Business Profile | Search keyword impressions | Updated at the start of each month, up to 5 days late. No retention figure stated. | Monthly export of the monthly impressions endpoint. |
| Chrome UX Report | CrUX API | A 28-day rolling average, updated daily. | CrUX History API or BigQuery. |
| Chrome UX Report | CrUX History API | The previous 40 weeks, one collection period per week; 25 periods by default. The page intro still says six months. Rolling. | Store the weekly pulls, or use BigQuery. |
| Chrome UX Report | CrUX on BigQuery | The full dataset back to 2017; monthly tables on the second Tuesday of the following month. Kept. | The exception in this table: origin-level history survives. |
| YouTube | Reporting API bulk reports | Reports available for 60 days after generation; a new job backfills the prior 30 days, and those files last 30 days. Rolling. | Create reporting jobs early; download files as generated. |
| Bing Webmaster Tools | Search Performance | 16 months per the October 2024 vendor blog; the help page still says six months and that you cannot see backdated data from before the site was added. Rolling. | Add the site early; export CSV or use the API regularly. |
| Microsoft Advertising | Standard performance reports | Hourly: 6 months. Daily and above: 36 months. Rolling. | Scheduled Reporting API downloads. |
| Microsoft Advertising | Search term, goals, segments reports | Hourly: 1 month. Daily and above: 36 months. Rolling. | As above. |
| Microsoft Advertising | Geographic, user location, MMM reports | Hourly: 14 days. Daily and above: 36 months. Rolling. | As above. |
| Microsoft Advertising | Change history, call forwarding, share of voice | 6 months at every aggregation. Rolling. | Export change history regularly. |
| Microsoft Advertising | Asset performance; budget; click ID | Asset performance 30 days; budget 24 months daily; click-level data up to 180 days. Rolling. | As above. |
| Microsoft Clarity | Session recordings | 30 days; favourites and a random sample up to 9 months. Recordings cannot be downloaded. Rolling. | Favourite the recordings that matter. |
| Microsoft Clarity | Heatmaps | Up to 9 months. Rolling. | Screenshot or export key heatmaps. |
| Microsoft Clarity | Data Export API | The last 24, 48 or 72 hours; 10 requests per project per day. API lookback. | Daily scheduled pull. |
| Meta Ads | Ads Insights API and Ads Manager totals | Up to 37 months. Rolling. | Scheduled Insights API exports. |
| Meta Ads | Breakdowns: unique counts, hourly, frequency, reach | From January 12, 2026: unique-count and hourly breakdowns 13 months, frequency 6 months. Reach is not returned with breakdowns beyond 13 months in standard queries. Rolling. | Export breakdown reports monthly. |
| Facebook Pages | Page Insights (Graph API) | Last two years; 90 days viewable per request. Rolling. | Pull in 90-day chunks and store. |
| Media and account insights | Media metrics up to 2 years; account (user) metrics up to 90 days. Rolling. | Daily or weekly pull of account metrics. | |
| LinkedIn Marketing API | Ads reporting | Performance data 10 years; professional demographics 2 years; a 6-month daily retention period per the restrictions note. Rolling. | Export demographic pivots and daily data regularly. |
| Pinterest API v5 | Ad account analytics | Sync: 90 days back. Async reports: up to 914 days back, 186 days per report; product-item level 92 days; hourly 8 days. Rolling. | Scheduled async report jobs. |
| Pinterest API v5 | Organic account analytics | Start date cannot be more than 90 days back. API lookback. | Weekly API pull. |
| Amazon Ads API v3 | Sponsored ads campaign reports | Sponsored Products 95 days; Sponsored Brands 60; Sponsored Display 65; Sponsored TV and DSP 95. Maximum 31 days per report. Rolling. | Daily or weekly report pulls. |
| Cloudflare | Web Analytics | Previous six months; unsampled data for 7 days, then about a 10% sample. Rolling. | GraphQL Analytics API pulls. |
| Cloudflare | Security Analytics (zone) | Free and Pro: last 7 days. Business: 31 days. Enterprise: 90 days. Rolling. | Logpush on Enterprise, or GraphQL pulls. |
| Vercel | Web Analytics and Speed Insights | Web Analytics: Hobby 1 month, Pro 12 months, Plus and Enterprise 24 months; only the reporting window is guaranteed. Speed Insights ranges: 24 hours and 7 days free; with Speed Insights Plus, 30 days on Pro and 90 on Enterprise. | Upgrade the plan, or use Drains on Pro and above. |
| X Ads API | Analytics | No retention period stated. Sync queries allow 7 days per request, async up to 90; X advises storing data older than 30 days locally. | Fetch in 30-day windows and store. |
Two rows carry a conflict inside the vendor's own pages, and the table follows the more specific statement. Bing's October 2024 blog says 16 months while its help page still says six. The CrUX History API page's introduction says six months while its body says 40 weeks. Where a figure we were briefed with contradicted the documentation, the documentation won: Clarity heatmaps are kept up to nine months, not thirteen.
03 — The rankingShortest windows first
The chart ranks stored-data windows, not API lookbacks, and scales each bar to Google Ads' 37-month cap for daily data. The datasets most teams rely on for year-over-year work sit in the middle: 14 months for GA4 event data at the standard maximum, 16 for Search Console and Bing.
Days of history kept, selected datasets
Vendor documentation read September 25, 2026. Bars scaled to Google Ads daily data at 37 months (about 1,126 days).At the long end, four datasets outlast a typical client relationship: LinkedIn ads performance data for ten years, Google Ads monthly and larger rollups for eleven, GA4 360 at up to 50 months, and CrUX on BigQuery back to 2017. At the short end the 72-hour Clarity export API and Pinterest's 8-day hourly window are lookbacks rather than deletions, but they set the cadence of the job that stores them.
04 — The changesThree retention rules worth a calendar entry
Google Ads' data retention page states that from June 1, 2026 hourly, daily and weekly reporting data is available for 37 months, while monthly, quarterly and annual data is kept for 11 years, after which it is not accessible through the interface or the APIs. Reach and frequency metrics are kept three years and the change history two. A daily export is now the only way to hold daily granularity past 37 months.
Meta's developer blog of October 16, 2025 set the second change: from January 12, 2026, unique-count and hourly breakdowns in the Ads Insights API are limited to 13 months of history and frequency breakdowns to six, while totals continue to be available for up to 37 months. The third is not new in 2026 but belongs on the same calendar: GA4's rule for growing properties, stated on its retention page: when a standard property becomes Large, event-level retention is automatically cut to two months and older event data is permanently deleted. A property that grows into that threshold loses a year of exploration history unless the BigQuery export is already running; our GA4 BigQuery export reference covers the setup.
05 — The checklistExport this week: five jobs, in order
Search Console: bulk export, then a 16-month API pull
Configure the bulk data export to BigQuery so daily history accumulates from today. Then pull the full 16 months through the Search Analytics API, by date and dimension, and store it. The pull is the only copy of the months the export will never contain.
GA4: 14 months and a billed BigQuery project
Set event-level retention to 14 months; the change applies only to data not already deleted. Link BigQuery in a project with billing enabled, because sandbox tables expire after 60 days. Use streaming export above one million events a day.
Bing Webmaster Tools: add the site now
There is no backdated data. Add the property at kickoff even if Bing is not yet a priority, and schedule a CSV download or API pull inside the 16-month window.
YouTube and Clarity: jobs and favourites
Create YouTube Reporting API jobs early; a new job backfills only the prior 30 days and files last 60. In Clarity, favourite the recordings that matter, since non-favourites are deleted at 30 days and cannot be downloaded.
The fifth job is a scheduled pull for every rolling ad dataset in the table: Google Ads change events every 30 days, click-level rows every 90, Meta breakdowns monthly, Amazon campaign reports weekly. Our analytics practice runs that schedule as the first deliverable of an engagement, and our note on the Search Console link report covers one more export that should be in it.
A reference table built from official vendor documentation only. Quoted words are the vendor's; the window and preservation columns are our paraphrase.
- What was collected
- For 44 datasets on 20 platforms: the documented retention or lookback window, whether it rolls, what happens to older data, the export or setting that preserves it, and the page's revision date where shown.
- Sources
- Help centres, developer documentation and vendor product blogs only. Server-rendered pages were read directly; JavaScript-rendered pages were read through a rendering service. No third-party summaries or forums.
- As-of date
- Documentation read on September 25, 2026.
- Exclusions
- Dropped for lack of a documented window: Google Tag Manager version history, Looker Studio, Merchant Center performance reports, Search Console Insights and Crawl Stats, TikTok Ads Manager, X Ads retention. Not covered: Meta Pixel and Events Manager, YouTube Analytics, and session-replay tools other than Clarity. The GA4 default retention value is not printed because the page does not state it.
- Known limitations
- Google Help Center pages carry no revision date. Where a vendor's pages disagree, the table follows the more specific statement and says so. Plan tiers change; Vercel and Cloudflare windows are per plan as documented.
- Refresh
- Refreshed in place when a vendor changes a window; the Google Ads and Meta changes of 2026 are the model for what triggers one.
07 — ConclusionThe window is documented; the loss is a scheduling decision
Switch on the Search Console and GA4 exports before the access request is even complete, and pull the 16 months the exports will never contain
No platform in the table hides its window. The history disappears because the export was set up after the wait, not before it.