Protect Your GA4 HistoryTwo settings, 10 minutesTwo settings, 10 minutes

GA4 Forgets. Stop It. Short guide to the two GA4 settings (data retention and BigQuery export) that protect your history, in about 10 minutes.

history you can't get back

What you get (+1 bonus)

Retention, from 2 to 14 months.
GA4 deletes the detail behind your explorations after 2 months by default. The guide shows where to raise it to 14, what that protects and what it can't bring back.
Your own copy of every event.
The BigQuery export, linked step by step: the roles you need, Daily or streaming, and why it copies every event into your own Cloud project only from the day you switch it on.
Sandbox or billing, explained.
Why sandbox tables expire after 60 days, what BigQuery's monthly free tier covers on a billed project, and why queries are the cost that can surprise you.
A scored 10-minute checklist.
Ten lines from confirming your Editor access to setting a budget alert, scored out of 10. Start with line 2, raising retention, which takes about a minute.
Two examples, shop and lead-gen.
A WooCommerce fashion store planning Black Friday and a private clinic planning its spring booking peak show what each setting keeps and what's already gone. Both are illustrative.
+1 bonus
An AI skill for Claude, ChatGPT, Gemini or Copilot
that checks both settings, says what detail is already gone, sizes the BigQuery export from your event counts and writes the setup steps, changing nothing itself.

Free · about 15 seconds

Who it's for, and who it's not for

A small business owner at a desk plans the next busy season, with a wall planner showing late November and next spring circled.

Who it's for

Owners and marketers of online shops and lead-gen businesses who want to compare this year's Black Friday or busy season with last year's, in detail.
Agencies and freelancers who run GA4 for clients and want a short, checkable standard for data retention and the BigQuery export.
Anyone with Editor access to a GA4 property who has never checked the retention setting. No code is needed, and one box is for whoever implements it.

Who it's not for

Properties that already keep 14 months of data and run a BigQuery export on a billing-enabled Cloud project. You're covered.
Anyone hoping to recover data GA4 has already deleted. Neither setting can rescue the past; both protect everything from the day you switch them on.

What's inside

PDF · About 10 min read

Honest note

BigQuery keeps your tracking's mistakes for years, from a purchase event that fires twice to a booking form that never sends a lead event, and a BigQuery table doesn't check itself, so a paused export or a tag change that halves your events can go unnoticed. The storage figures are an illustrative example, and the guide quotes no rates because they change and differ by region. If careless queries on a billed project worry you, set the budget alert or hand the setup to whoever implements your tracking.

Free · about 15 seconds