As an illustration of how this usually surfaces: a client asks why their GA4 dashboard shows a fraction of the conversions their CRM logged for the same month. The agency opens the account and finds exactly one event marked as a key event: page_view, left over from whoever clicked through the setup wizard two years earlier and never touched it again.
That gap is not rare. It is the default state of most GA4 accounts, because the setup wizard gets a measurement ID onto the page and stops there. Everything that makes the data trustworthy, which events count as conversions, how long the data sticks around, whether search traffic shows up with any context, is left at factory settings unless someone goes back in and changes it. This google analytics 4 setup guide covers the part the wizard skips: the handful of settings that decide whether the account is actually useful six months from now.
TL;DR:
- GA4 does not track conversions out of the box. Events have to be manually marked as key events in Admin, confirmed by Google's own documentation.
- The default data retention setting is two months for standard properties, per Google's retention policy. Miss this at setup and a year-over-year report later has nothing to compare against.
- Linking Search Console and marking key events are two separate steps most tutorials bundle together, and skipping either one leaves a dashboard that looks complete but answers the wrong questions.
- A single-site setup is reasonable to do yourself. Multi-property accounts or anything feeding ad spend decisions is where a misconfigured setup gets expensive fast.
What the GA4 setup wizard actually gets you
Creating a property, adding a web data stream, and pasting the measurement ID onto the site is the part every tutorial covers well, and Google's own setup walkthrough is the most reliable version of it if this is the first time doing it for a given site.
That sequence gets basic traffic flowing into reports: page views, sessions, rough geography and device data. For a lot of small sites, that is treated as "done." It is not done, because none of that traffic data tells anyone whether the site is working. A page view is not a lead. A session is not a sale. The wizard hands over plumbing, not plumbing connected to anything that matters to the business.
The two-month retention trap nobody checks on day one
This is the setting that causes the most damage later, specifically because it is invisible for months. By default, a standard GA4 property retains user-level event data for two months before it starts dropping it, per Google's documented retention windows, which allow standard properties to extend that window to fourteen months but do not apply the longer setting automatically.
Nobody notices this at setup, because there's no data to lose yet in month one. The problem shows up eleven months later when someone asks for a year-over-year comparison on a report, and the exploration report comes back empty for everything past two months back. At that point the only fix is waiting, there is no way to retroactively extend retention on data that already aged out.
Changing it takes one click, in Admin under Data Settings, Data Retention. Do it in the same sitting as the initial setup, not after someone asks for a report that needs it.
Key events: the setting that decides whether anything is a "conversion"
GA4 automatically collects a set of events, page_view, session_start, first_visit, and a few others, but none of these tell anyone whether the site did its job. A conversion in GA4 only exists once a specific event is manually flagged as a key event, confirmed directly in Google's key events documentation.
That means a form submission, a phone click, a scheduled call, or a completed purchase sits in the Events report as raw data until someone goes into Admin, Events, and flips the toggle next to it. Skip that step and the conversions report in GA4 stays empty or tracks the wrong thing, which is exactly how the mismatch from the opening happens: whatever got marked a key event back when the account was first set up is the only thing GA4 will ever report as a conversion, regardless of what the business actually cares about today.
Search Console: the context GA4 cannot generate by itself
GA4 tracks what happens after someone lands on the site. It has no visibility into what they searched to get there unless Search Console is linked in Admin, under Product Links. Once linked, organic query and ranking data appears inside GA4's Acquisition reports instead of living in a separate, disconnected tool.
This step gets skipped constantly because it is not required for GA4 to function, the dashboards all look complete without it. The cost shows up when someone asks which search terms actually drive the leads GA4 is now tracking as key events, and the honest answer without this link is "we'd have to go check a different tool and manually cross-reference it."
Connecting clean data to decisions instead of a dashboard nobody opens
Once key events are marked and retention is fixed, the GA4 property is finally reporting something real: actual conversions, tied to actual acquisition channels, retained long enough to compare quarter over quarter. That is the baseline our data analytics consulting team builds from when we take over an account audit, because fixing these three settings before building a single dashboard saves weeks of chasing numbers that don't reconcile with the CRM.
The next failure point is usually not GA4 itself, it's what happens to the data after. A property that reports clean conversions but still requires someone to log in and manually check it every Monday is barely an improvement over the broken version. Piping GA4's key events into an automated alert, a weekly digest, or a workflow automation that flags a conversion drop the day it happens is what turns a setup project into a system someone actually uses past month two.
DIY or hire it out
A single site with two or three conversion actions, a contact form, a phone click, maybe a newsletter signup, is a reasonable project to do without help. Following Google's own documentation closely and spending the extra hour on retention and key events covers most of what matters.
The math changes once there's more than one property, ecommerce purchase values that need to flow into Google Ads bidding, or any setup where a wrong number changes how ad budget gets allocated. As an illustration, a business spending a few thousand dollars a month on ads based on a conversion count that's actually under-reporting by two-thirds, because only one of three lead forms got marked as a key event, is optimizing that spend against the wrong number every single day the mistake goes uncaught. That is example math to illustrate the stakes, not a quote, but it's the shape of what an agency audit usually catches.
Key takeaways
- GA4 does not report conversions out of the box. Nothing counts until someone manually marks it as a key event in Admin, and that list needs revisiting every time a new form, booking flow, or product line goes live.
- Standard properties default to two months of event-level retention. Extend it to fourteen months on day one, in Admin under Data Settings, because there is no way to recover retention on data that already aged out.
- Linking Search Console puts organic query data inside GA4's own acquisition reports instead of a separate tool nobody cross-references.
- A single site with a short, stable conversion list is fine to set up yourself. Multi-property accounts or anything feeding ad spend decisions is where a quiet misconfiguration gets expensive.
Tell our analytics team what's currently connected and what isn't, and we'll tell you exactly which of these settings are already wrong in your account.
