First detect, then understand
Monitoring answers the question “did something change?”. Tracking diagnosis goes a step further and helps with “why?”. As soon as Conversion Sentinel detects a notable deviation – such as a drop in purchases or a sudden direct-traffic spike – the search for the cause begins, which otherwise takes a lot of manual work.
Tracking problem or genuine performance?
Fewer conversions can have many reasons: campaigns, seasonality, consent, website changes, a broken trigger or a missing dataLayer value. The diagnosis helps put these possibilities in context. If traffic stays stable while a single conversion event collapses, that points more to a tracking problem than to a drop in demand.
Which signals are considered
For its assessment, Sentinel connects available signals: the monitored GA4 metrics, detectable changes in Google Tag Manager and hints from the dataLayer. From this it produces a transparent assessment of possible causes – deliberately phrased cautiously as a hint and recommendation, not a certainty.
From diagnosis to fix
If everything points to a GTM problem, you don't have to stop at the analysis. With the GTM Builder the recommended change can be prepared directly and set up in a new GTM workspace. You review and test it and only publish once everything fits. That turns “something's off here” into a concrete, controlled next step.
Diagnosis as part of monitoring
Tracking diagnosis works hand in hand with Conversion Tracking Monitoring and GA4 Monitoring. Monitoring detects the deviation, diagnosis helps with the cause. You'll find more background on the topic in the Data Flakes knowledge on tracking failures.