SERVICE FILE · GA4 AUDIT · FILED BY BARIS ASA, LONDON · REVIEWED
GA4 audit consultant, London, UK.
Baris Asa is a London tracking specialist who audits Google Analytics 4 (GA4) properties for ecommerce brands and the agencies behind them. Every setting in GA4 Admin is read against how the business actually sells: data streams, key events, the Google Ads link, filters, referrals, cross-domain and retention. You get back a written list of what's wrong, the evidence, and the fix.
The short answer: hire someone who reads the settings themselves, changes nothing without your OK, and tells you which fixes only work from today.
The five-minute Admin check · What gets checked · For agencies
Who audits a GA4 property, and what you should get back
GA4 records whatever the tags send it. The property's settings decide what it keeps, for how long, what counts as a result and which channel gets the credit. Most of them are set once, when the property is created, and never read again. Then the business changes: a new payment provider, a second domain, an agency that starred its own events as key events.
A GA4 audit reads those settings one by one and sets each against how the store sells now. I do it myself, in the property, with nothing changed until you've read the findings. If your question is bigger, whether every sale gets from the page to GA4, Google Ads and Meta intact, that's a tracking audit, which covers GTM and consent too.
The five-minute Admin check
Open your GA4 property, go to Admin, and look at five things.
- Data collection and modification › Data retention. Event data on 2 months means explorations and funnels can't look back past two months. Standard properties can choose 2 or 14.
- Data collection and modification › Data filters. An internal traffic filter still in Testing doesn't exclude anything. No filter at all means the office and the agency count as customers (F-602).
- Data display › Events. Count the starred key events (standard properties allow up to 30). If add_to_cart or page_view is starred on a shop, key event totals mean little (F-104).
- Data streams › your web stream › Configure tag settings › Show all › List unwanted referrals. If your payment provider isn't listed and customers leave your site to pay, expect sales credited to it (F-205).
- Product links › Google Ads links. No link means Google Ads can't import GA4 key events (F-403).
Two or more of those look wrong? Email me what you found.
What a GA4 audit covers, setting by setting
Twelve areas, all inside the GA4 property and its links. Each finding is filed against a code in the fault index where one exists.
| Area | What gets checked | What goes wrong |
|---|---|---|
| Data streams | One web stream per site, the same measurement ID on every page, and enhanced measurement events set against what GTM already sends. | A page_view or form_submit sent by both doubles the count. |
| Key events | Which events are starred as key events, against what the business counts as a result. | A non-sale marked as a key event inflates the total (F-104). |
| Google Ads link | That the link exists, to the right accounts, and which key events Ads imports. | Without the link, Ads can't import GA4 key events (F-403). |
| Internal traffic and data filters | Whether internal traffic is defined, and whether the filter is Active or still in Testing. | Office, agency and developer visits counted as customers (F-602). |
| Unwanted referrals and cross-domain | Payment providers in the unwanted referrals list, and every domain in the journey in the cross-domain list. | Sales credited to paypal.com or split into two sessions (F-205). |
| Custom definitions | Every parameter the tags send, checked against what is registered as a custom dimension or metric. | Sent but never registered means never reported (F-601). |
| Data retention | The retention period for event data and user data. | It decides how far back explorations and funnels can look. |
| Attribution settings | The reporting attribution model and the key event lookback windows. | They change which channel gets the credit in GA4 reports. |
| Personal data | Email addresses or names in page URLs and event parameters, and whether data redaction is on. | Google's terms forbid sending it, and it splits page reports (F-603). |
| Access and change history | Who holds which role, and what changed in the last two years, by whom. | Former staff and agencies often still hold Admin. |
| Time zone and currency | Set to the time zone and currency the business reports in. | Day totals that don't line up with the store's days. |
| Thresholds and (other) | Which reports withhold rows or group them as (other), explained before anyone reads a gap as lost sales. | Missing rows read as missing sales (R-502). |
What you get back
- A findings list, in priority order. Each finding names the Admin setting, shows the evidence (a screenshot or an exploration), links the fault code, and gives the fix.
- Past or future, per finding. Whether the fix corrects data already collected or only new data, and which date ranges to treat with care.
- The settings as found. A record of every setting on the day of the audit, so later changes can be checked against it.
- Who has access. Every user and their role, with the ones nobody recognises marked.
Your team or agency can act on the list without me. If you want me to make the changes, that's quoted separately.
What a settings fix can and can't change
- Data filters. Once a filter is Active, Google says the effect is permanent: matching data is never processed. That's why a filter is tested first.
- Data retention. It only affects explorations and funnel reports, not standard reports. Raising it keeps data not yet deleted; data already deleted stays gone.
- Key event lookback window. Changes apply going forward.
- Reporting attribution model. One exception: Google applies a change to past data as well as new.
Example: an inherited property (illustrative, not a client)
- A store moves to a new agency. GA4 shows a healthy conversion rate. The audit finds add_to_cart starred as a key event, a filter for the old agency's office left in Testing, and the card payment provider's domain missing from unwanted referrals.
- The findings: unstar add_to_cart, which applies to new data, and quote rates from purchase alone until then; activate the filter after checking it in an exploration; add the payment domain, then watch referral sales drop over the following weeks.
Also called: GA4 audit, Google Analytics 4 audit, GA4 property audit, GA4 health check, GA4 configuration review, analytics audit.
Is this the help you need?
Probably, if
- you've inherited a GA4 property and don't know who set it up, or why;
- the team has stopped quoting GA4 numbers in meetings;
- you're about to change agency, platform or domain and want the settings on record first;
- Google Ads bids on GA4 key events and nobody has checked which ones.
Probably not yet, if
- you need to know whether each sale reaches GA4, Google Ads and Meta at all: that's a tracking audit;
- you know GA4 is wrong and want someone to fix and run it: that's GA4 consulting;
- the totals don't match the store and you want to know why: that's reconciliation.
Questions to ask anyone auditing your GA4
- 01 Will you read the settings, or run a tool?
Automated checkers read what the API exposes. Whether a key event matches what the business counts, or whether the payment provider is in the referral list, takes a person who knows how the store sells.
- 02 Will you change anything without asking?
Some GA4 settings can't be undone: an active data filter discards what it matches for good. Nothing should change until you've read the finding and said yes.
- 03 Which fixes only work from today?
You should be told, per finding, whether the fix also corrects past data or only new data, and which date ranges to treat with care.
Who you'd be working with
I'm Baris Asa. I've spent eight years setting up and fixing tracking for ecommerce brands and the agencies behind them. Measurement only: I don't run your campaigns. The faults I look for are public: 19 documented in the fault index. The ones a GA4 audit turns up most: F-104 (key events mis-set), F-602 (internal traffic counted), F-601 (parameters never registered) and F-603 (email addresses in GA4). I've given five talks on this work, including HeroConf, PPC Live and Search 'n Stuff.
GA4 audits for UK agencies
I audit GA4 for UK agencies, named or white-label, inside the client's own property. Agencies usually call when they take on a client whose GA4 nobody explained, or before a pitch that rests on the client's numbers.
- What you receive. The findings list in a format your team edits, with your agency's name on the report.
- Who holds what. Campaigns and the client relationship stay with you. The property stays in the client's name.
- Terms. An NDA if you need one. Client contact only if you ask.
How agency work is arranged and billed: white-label tracking for agencies.
Questions about GA4 audits
- Who can audit my GA4 property in the UK?
- A specialist who reads every setting in GA4 Admin against how your business actually sells, and writes down each fault with its evidence and fix. I'm Baris Asa, a London tracking consultant. I audit GA4 properties for UK ecommerce brands, and for agencies white-label, and do the work myself.
- What does a GA4 audit check?
- The property's own settings: data streams and enhanced measurement, key events, the Google Ads link, internal traffic and data filters, unwanted referrals and cross-domain, custom definitions, data retention, attribution settings, personal data and redaction, user access and change history, time zone and currency, and thresholds.
- What do I get back from a GA4 audit?
- A written list of findings. Each one names the Admin setting, shows the evidence, links the fault code in the Synctag fault index where there is one, gives the fix, and says whether the fix also corrects past data or only new data. The list is in priority order, so the first fixes are the ones that change the numbers most.
- Is a GA4 audit the same as a tracking audit?
- No. A GA4 audit looks at the property. A tracking audit follows each sale from the tag on the page to the number in GA4, Google Ads and Meta, so it also covers GTM, the dataLayer and consent, and checks totals against the store's orders. If your question is whether the whole set-up works, start there: synctag.co.uk/services/tracking-audit.
- Do you work with agencies, inside our clients' GA4?
- Yes, for UK agencies, named or white-label, inside the client's own property. It suits a client you've just taken on, or one whose GA4 numbers your team has stopped quoting. Terms: synctag.co.uk/white-label.
- What access is needed, and how long does it take?
- Editor on the GA4 property, because Google only shows change history to Editors, and view access to the linked Google Ads account. Nothing is changed during the audit itself. How long depends on the number of properties and streams, and is agreed, with a start date, on the scoping call.
- Will fixing GA4 settings correct my old data?
- Mostly not. Data filters, the key event lookback window and most settings act on data from the day they change. A change to the reporting attribution model is one exception: Google applies it to past data too. Raising data retention keeps what hasn't yet been deleted; anything already deleted stays gone.
- How is a GA4 audit priced?
- No published rates. Brands get a fixed quote after a short scoping call. What sets the scope: how many properties and data streams, how many domains are in the journey, and whether the Google Ads link is in play. Repairs are quoted separately, and only if you want them. Agencies work to an hour estimate and a timesheet: see synctag.co.uk/white-label.
Sources, read 7 Nov 2026: GA4: data retention · GA4: mark events as key events · GA4: filter out internal traffic · GA4: identify unwanted referrals · GA4: set up cross-domain measurement · GA4: link to Google Ads · GA4: data redaction · GA4: attribution settings · GA4: enhanced measurement · GA4: change history · GA4: data thresholds.
Related services
- Tracking audit: the whole chain checked: GTM, GA4, Google Ads, Meta and consent, against the store's orders.
- GA4 consultant: who sets up, repairs and looks after the GA4 property.
- GA4 reconciliation: why GA4, the store and the ad platforms report different totals.
- GA4 ecommerce tracking: purchase events built and sent correctly, off Shopify.
- Google Tag Manager consultant: who builds, cleans up or looks after the GTM container.
- Tracking plan and documentation: who writes down what the tracking does, so someone else can run it.
- Ecommerce attribution tracking: sales credited to direct, PayPal or Unassigned.
- Consent Mode v2: who sets up and repairs Consent Mode v2.
- Google Ads conversion tracking: online sales counted once, at the right value.
- Looker Studio reporting: a report the team trusts, built on checked data.
- White-label for agencies: tracking work under your agency's name.
- How I work: how a job is scoped and run.
Email what
you found.
The site, how many GA4 properties and streams, what the five-minute check showed, and why now (new agency, new platform, numbers nobody trusts). I'll tell you what the audit would cover. I reply myself.
Example example.co.uk · 1 property, 2 domains · filter in Testing · agency changed in May
[email protected]