Skip to content

Recovery: GA4

Your GA4 data has a gap or dropped, and nobody knows why.

GA4 data loss almost always traces to one of a few causes: a retention setting quietly capping how far back you can look, a filter applied to the wrong traffic, or a property change that broke the connection between your site and the account. We check each one.

  • Property audit before any change
  • Written cause before we touch a setting
  • No cost to see the scope

Evidence, then action

How we find what changed and when

The evidence we pull first

We check the property's data retention setting, the data streams connected to it, any filters applied under Admin, and the change history where GA4 shows one, to see exactly when the setup last changed.

The triage order

First we check whether this is a true data loss or a retention setting limiting how far back you can query, since GA4 defaults some reports to a shorter window than people expect. Next we check filters and internal traffic rules, then the measurement ID on the site itself, then cross domain settings if more than one site feeds the property.

What usually fixes it

Correcting the retention setting, removing a filter that was excluding real traffic by mistake, fixing a measurement ID that points at the wrong property, and reconnecting a data stream that silently stopped sending data solves most cases that are not simply gone for good.

What we cannot promise

We cannot promise to bring back data that GA4 never actually collected, since a real gap in collection cannot be reconstructed after the fact. We can promise a clear answer on whether your case is a setting we can fix or data that is genuinely gone.

The decision tree we run

If historical reports look shorter than expected

we check the data retention setting under Admin, since GA4 can be set to hold event level data for as little as two months even though summary data lasts longer.

If one channel or source disappeared from reports

we check filters and any internal traffic definition, since a filter meant to exclude your own team's visits can be written broadly enough to exclude real customers by accident.

If data stopped on a specific date with no property change logged

we check the measurement ID in the site's code, since a code deploy that reverted an old tag or removed a snippet will not show up in GA4's own change history.

If data is missing for only one of several connected sites

we check that site's specific data stream and cross domain configuration, since a shared property with several domains can lose one stream while the others keep reporting normally.

How the engagement runs

01

Property and stream audit

We review the retention setting, filters, and every data stream connected to the property to map out what should be collecting data.

02

A written account of the cause

You get a plain explanation of what happened, when it happened, and whether it is a setting we can fix or a genuine gap in the data.

03

Fix, then set up guardrails

We correct what is fixable and add a simple check so a future change to the site or the property gets caught faster next time.

GA4 data loss questions

Find out what happened to your GA4 data

Send us admin access to the property. We will map every setting that could explain the gap and send a written cause within one business day.

Keep exploring:

Do I still need GTM if I already have GA4Why Google Ads and GA4 report different numbersRecovery: GTM broken after a migrationRecovery: tracking broken after a redesign