The default retention for detailed event data is short and can usually be extended to the longer option in a few clicks. Change it now, since it does not apply retrospectively.

A default nobody chose

When a property is created, the retention period for detailed event data is set to the shorter of the available options by default.

Nobody selects it, nobody is asked about it, and it is several screens into the administration section.

Which means a great many properties have been quietly discarding detail after a couple of months, since the day they were created.

It is a few clicks to change and it does not work backwards, which is the combination that makes it worth doing today rather than when somebody notices.

What is actually affected

Worth being precise, because the setting sounds more alarming than it is.

It governs detailed, event-level data: the underlying records that let you break things down and build custom explorations.

The standard aggregated reports, such as visitors over time and traffic by source, are retained regardless and are not affected.

So a property left on the default still shows you a two-year trend line of visitors. What it cannot do is let you interrogate an unusual month from eighteen months ago in any depth.

That distinction matters, since panic about losing all your history is misplaced and complacency about losing the detail is also wrong.

Why the detail is the part you want later

The last is the whole argument. You cannot know in advance which detail you will want, and retention is decided before the question exists.

Change it, and check the reset option

The practical instruction, since there are two settings rather than one.

The retention period itself has a longer option, and for most businesses selecting it is the correct answer.

Alongside it is an option about whether the retention clock resets each time a visitor returns, which extends how long a returning visitor's record persists.

For a small business with returning customers, leaving that on is usually sensible, and it is worth a moment's thought rather than being ignored.

Both live in the data settings area under administration, and changing them takes under a minute once found.

Make the change on the day a property is created, alongside the internal traffic filter, since both are day-one settings that are painful to have missed.

A worked example

A business wanted to understand why the previous spring had been unusually busy, in order to plan for the coming one.

Their standard reports showed the traffic clearly enough, and every attempt to break it down by source, page, or device returned nothing for that period.

The detailed data had been discarded under the default retention setting months earlier.

They could see that something had happened and could not find out what.

They changed the setting immediately, which protected everything from that point forward and recovered nothing.

The useful part was the conclusion they drew: they started exporting a short monthly summary to a spreadsheet, so that whatever the retention policy did, they held a record of the questions they knew they would ask.

Export what you know you will want

The habit that makes retention settings less important.

A monthly export of a handful of figures, kept in a spreadsheet you control, survives any retention policy, any product change, and any account problem.

Visitors, sources, top pages, and conversions, one row per month, takes a few minutes and answers most future questions.

That is the same discipline as holding your own backups, applied to figures rather than files.

It also has the advantage of being readable by anybody, without an account or an interface, which matters more than it sounds when somebody asks about a period three years ago.

Retention is not only a technical setting

A brief note, since the option exists partly for reasons beyond convenience.

Holding personal data longer than you need is something privacy frameworks generally discourage, and analytics data about individual sessions is not exempt from that thinking.

For most small businesses the longer option is entirely reasonable and proportionate, and the decision is worth making deliberately rather than by default in either direction.

If you have a privacy policy describing how long you keep information, it is worth checking that what it says matches what your settings do.

This is a general description rather than advice on your obligations, which depend on where you operate and what you collect.

Check the other day-one settings

Since you are already in the administration section.

Confirm your time zone and currency are correct, because reports are grouped by day according to the time zone and a wrong one shifts everything.

Check whether internal traffic filtering is configured and active.

Check who has access, and remove anybody who no longer needs it.

And confirm the property is linked to Search Console and to any advertising account.

Five minutes covers all of them, and they are the settings that are cheap now and expensive to have missed.

The counter-case

The longer retention period is not automatically right for everybody.

A business that has never looked at detailed data and never will is choosing between two settings that make no difference to them, and the shorter option is the more conservative one for holding personal data.

There is also a risk in treating settings as the answer, when a monthly export in a spreadsheet is more durable than any configuration and less dependent on a product that keeps changing.

And no retention setting helps with the figures that were never collected, which for most small businesses is the larger gap.

Change the setting, start the monthly export, and rely on the second.

The five minutes

  1. Open data settings under administration.
  2. Select the longer retention option.
  3. Consider the reset-on-return setting.
  4. Confirm your time zone and currency.
  5. Check internal traffic filtering is active.
  6. Review who has access.
  7. Start a monthly export you control.

Step seven is the one that outlasts every setting, since a spreadsheet you own is not subject to anybody's default.

Why nothing transfers between properties is covered in your historical data is not coming with you.


Frequently asked questions

What is the default retention?

The shorter of the available options for detailed event data, applied automatically when a property is created. Nobody selects it and it is several screens into administration.

What does it actually affect?

Detailed event-level data used for custom explorations and breakdowns. Standard aggregated reports such as visitors over time are retained regardless.

Why does the detail matter?

Because you cannot know in advance which questions you will want to ask. Investigating an odd month or comparing seasons in depth both need the detail.

Does changing it recover old data?

No. It applies from the point of change onward, which is why it is worth doing on the day a property is created rather than when somebody notices.

What is the reset option?

A setting controlling whether the retention clock restarts when a visitor returns, which extends how long their record persists. For a business with returning customers it is usually sensible.

What is more durable than the setting?

A monthly export of visitors, sources, top pages, and conversions into a spreadsheet you control. It survives any retention policy, product change, or account problem.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Created a property and never opened the settings?

Change the retention period today. It cannot be applied backwards, and the default has been discarding detail since day one.

Start a Conversation