GA4 workflow

Review unusual changes in client key events

Use an event’s recent history to prioritise investigation during recurring analytics reviews.

A practical sequence

From inspection to a documented next action.

Choose the events

Select the key events that matter to the client and a suitable history window. Understand the expected traffic pattern and known campaign changes.

Read the finding

Run the anomaly check and inspect its explanation. Compare the flagged period with the event’s history, reporting freshness and traffic volume.

Investigate likely causes

Check traffic, consent changes and recent releases. Compare GTM/GA4 configuration and inspect browser requests before identifying a cause.

Repeat with a clear owner

Agree who reads the results and what warrants escalation. Premium supports emailed findings and scheduled checks within the local scheduler limits.

ODDVX key-event anomaly result: generate_lead flagged CRITICAL on a GA4 property, with a 7-day dry streak, a 100% drop in the trailing window, and the reasoning that the gap is longer than the event's normal dry-spell ceiling — Product interface example. Review the selected account scope and date range when interpreting your own results.

What the result meansAnomalies are not instant fault detection and do not identify the cause by themselves. Premium supports up to 10 scheduled runs per day while ODDVX is running and the computer is awake and online. Missed runs are skipped; this is not cloud monitoring.

Start free. Repeat with Premium.Free lets you work on one account, property or saved configuration per run, depending on the tool. Premium adds batches, CSV/Excel exports, report email and multiple Google accounts.

Start free

Use this workflow on one client account.

Start with Free for Windows. Review the scope and findings before expanding the run.

Run your first free audit More client workflows