Troubleshooting

The audit result looks incomplete or wrong - how do I report it?

Three quick checks before reporting (evidence, scan freshness, the session) and how to write a report we can act on fast - plus what happens with it on our side.

2 min read

Automated verification is repeatable, but not infallible - GA4 configurations can be unusual, and we'd rather hear about a discrepancy from you than not at all. Here's how to report a suspected error so we can react quickly.

Before reporting - 3 quick checks

1.Check the evidence on the checkpoint - every error and warning shows the concrete numbers/facts the verdict was based on (e.g. "coupon = (not set) in 100% of 1,843 transactions"). Often it's not the report that's wrong - it's reality that surprises. Evidence data can be reproduced in GA4 reports.
2.Make sure you're looking at a fresh scan - a report is a snapshot; if you've changed things since, rescan first (why).
3.Check whether the audit ran on an expired session - incomplete results and serial "no access" are the token's symptom (what then).

How to report

Write to contact@ga4audit.io (from the account's address). An ideal report includes:

the project name / website address and the audit date concerned,
the checkpoint identifier (e.g. "4.6") and why you believe the result is wrong,
what GA4 shows on your side (a screenshot of the GA4 report helps a lot),
context of anything unusual: server-side tagging, custom consent, a proxy/WAF.

You don't need to grant us GA4 access - our side's evidence lives in the scan logs.

What happens with your report

We verify the discrepancy at the source: the checkpoint's logic vs. your configuration. The outcome is one of three: (a) an explanation of why the verdict is correct after all (most often), (b) a fix to the checkpoint's logic - benefiting all users, (c) marking your case as requiring manual verification. In every variant, you get an answer.

Discrepancy reports are among the most valuable product signals we receive - thank you for every one.

Related articles:

More in Troubleshooting

Didn't find your answer?

Write to us - we respond fast, implementation questions included.

Write to us