Google Analytics Consulting: The GA4 Settings That Decide What Your Reports Show

Updated November 2026 · Written and maintained by the Progression Agency strategy team

A form fill that was never marked as a key event leaves a quarter of leads uncounted, and marking it today does not fix last quarter: Google Analytics applies key events from the moment they are marked. Most reporting arguments start with settings like that one, chosen once and forgotten. Google Analytics consulting checks those settings first: how long the property keeps detailed data, which events count, how consent is handled and what the Tag Manager container is really firing. Progression’s team is based in New York, audits properties for US businesses remotely, and meets your team on site to walk through the findings when you ask.

A quarter of leads that never counted

A hypothetical clinic’s booking form event fired on every submission all quarter. Nobody had marked it as a key event, so the report shows no conversions from email.

The fix takes a minute: mark the event. It counts from that moment on, and the quarter stays as it was. Some settings in Google Analytics 4 (GA4) cannot be fixed backward, which is why they are checked first.

Why can a setting not be fixed backward?

Because the property records what it was set to collect at the time. A key event, a retention period or a consent choice shapes data going forward and, in the case of retention, can delete data that no setting change brings back.

What Google Analytics consulting checks in a GA4 property

The audit goes through a short list of settings, each with a reason it matters, a failure that follows when it is ignored and a fix. Where Google’s help pages state a fact, the table states it as they do. Where they do not, the cell carries plain advice only.

Data retention: 2 or 14 months for detailed reports

For Google Analytics properties, user-level data retention can be set to 2 months or 14 months, and the same period applies to key events data. Other event data can also be set to 2 or 14 months, or to 26, 38 or 50 months on Analytics 360. Age, gender and interest data always keep a two month period.

The setting affects explorations and funnel reports, not standard aggregated reports. See Google’s data retention page for the exact wording.

Key events count from the day they are marked

A key event is an event marked as important. Marking one changes reports from that time and does not change historic data, and it can take up to 24 hours to appear in standard reports. Key events can be used to create Google Ads conversions.

• Write down every key event and the reason it counts.
• Mark an event before the campaign that depends on it starts.
• Check that the event shows in reports after 24 hours.
• Keep the list short enough that each one still means something.

Consent mode with the banner you already have

Consent mode communicates a visitor’s cookie or app identifier consent status to Google so tags adjust their behavior. It does not provide a consent banner. It works with the business’s consent management platform or custom banner.

When consent is denied, tags do not store cookies and send cookieless pings instead, and Google Analytics fills gaps with conversion modeling and behavioral modeling. Tags without built-in consent checks can get checks in Tag Manager under Advanced, then Consent Settings. See Google’s consent mode page for the full description.

The plain advice: consent mode is set up with the banner, not instead of it. Questions about what the law requires of your banner go to counsel, and nothing on this page is legal advice.

What changes in the numbers when consent is denied?

Cookieless pings carry a minimum of information, and Google Analytics models some of the gap. Reports mix measured and modeled data, so a banner change can move totals.

Google Tag Manager consulting for a crowded container

A container that has grown for years holds tags nobody remembers adding. The work is an inventory: every tag, trigger and variable gets an owner and a reason, and anything without both is paused, then removed.

A Google Tag Manager consultant also sets naming rules and a routine of workspaces and approvals, so the next change is reviewed before it goes live.

• List every tag, trigger and variable.
• Record an owner and a reason for each.
• Pause what has neither, watch for a week, then remove it.
• Adopt one naming rule and one approval step.

What a Google Tag Manager specialist hands over

A container inventory, a naming rule, a short approval routine and a clean, versioned container the team can publish from with confidence.

Google Analytics 4 consulting services for apps and sites together

One property can hold web and app streams. Google Analytics marks purchase on web and app by default, and first_open and in_app_purchase on app. The plain advice: event names are agreed across the web and app teams before launch.

• Agree event names once, across both teams.
• Check which key events each stream gets by default.
• Test a purchase and a first open on real devices.
• Record which stream each report reads from.

A mismatch of names across streams is the most common reason a combined report looks wrong, and it is cheap to prevent.

Why agree names before launch?

Because renaming events later splits history in two.

Pricing GA4 and Tag Manager work

Pricing for Google Analytics consulting services depends on scope, is subject to change and is set in the written proposal. Analytics 360 license fees are priced by Google.

• Ask how many streams and containers the scope covers.
• Ask what a settings audit includes and what it leaves out.
• Ask whether the container clean up is priced separately.
• Ask who keeps the settings record.

Retention changes you cannot take back

When data reaches the end of the retention period, it is deleted automatically on a monthly basis. If you reduce the period, any affected data is deleted during the next monthly process. If you increase it, the change applies to data you have already collected and have not yet deleted.

Google Analytics waits 24 hours before implementing a change, and during those 24 hours you can revert it and your data is unaffected. The plain advice: write down every setting change, with a date, in a change log the business keeps.

Who should be allowed to change retention?

Few people, and each change logged. A change by someone who did not know the consequence cannot be undone.

Handing the property back to your team

The audit ends with records your own team can maintain. The method is proprietary and kept for clients, and the records are yours.

• A settings record with values and dates.
• A key event list with reasons.
• A container inventory with owners.
• Consent setup notes.
• An access list.

Who updates the records?

Whoever changes a setting, on the day they change it. A record updated quarterly is a record that is wrong most of the time.

When the problem is not Google Analytics

Sometimes the property is fine and the cause is elsewhere. If leads are logged in the CRM but not in GA4, the fix may be a form or redirect issue on the site. If paid traffic looks wrong, the ad account may be the issue.

• Leads in the CRM but not in the property: check the form and redirect.
• Paid traffic that looks wrong: check the ad account.
• Totals that disagree between tools: check how each defines a conversion.
• A drop after a site release: check the tags that moved.

For the ad account side, see Google Ads audit, and for wider measurement, marketing analytics agency. For testing what the numbers say, conversion rate optimization agency.

How do you know which it is?

By testing one visit end to end: submit a form, watch the event fire, see it in the property and trace it to the CRM.

A test visit, from click to report

The quickest way to find a measurement fault is a single visit followed all the way through. It shows where a lead disappears.

1. Open the site in a clean browser.
2. Accept or decline consent, and note which.
3. Submit the form or complete the action.
4. Watch the event appear in the realtime report.
5. Check the key event after 24 hours.
6. Find the lead in the CRM.

Each step has a person who owns it, and the step where the trail ends names the owner.

What if the realtime report shows nothing?

Then the tag did not fire, and the container is the first place to look.

Naming events so two teams agree

Event names are the vocabulary of a property. When two people name the same action two ways, reports split it in half and nobody notices.

The record lives with the settings record, so the property and its vocabulary move together.

Should old events be renamed?

Rarely. Renaming splits history, so old names usually stay and new events follow the rule.

Access: who can change the property

A property outlives the people who set it up. Former staff and former agencies often keep administrator access for years.

• List everyone with access and what level.
• Remove people who no longer work with you.
• Give each person the lowest level that does the job.
• Review the list twice a year.

A read access audit is enough to find these problems. Changes are made with the access level your team chooses.

Why not give the agency admin access permanently?

Because access that is not needed is a risk without a benefit. Grant it for a task and review it after.

Frequently asked questions