Posts on Telemetry.
6 posts tagged "Telemetry".
The GSC and GA crons failed silently for two weeks. That's a telemetry blindspot, not a cron problem.
The nightly GSC and GA telemetry crons for UK Calculators had been dying every night since 20 June. On 4 July a Saturday morning review found the gap — fourteen days of dark data, no alerts, clean-looking logs. The fix took an afternoon. The monitoring lesson took longer.
Behaviour events in the nightly digest: the existing GA4 read-only token already covered them
Adding user-behaviour events to the nightly digest on 25 July required no new authorisation scopes and no site changes. The GA4 read-only token already covers eventName and eventCount under analytics.readonly. The cheapest behaviour telemetry wedge: Layer 1 default events, surfaced by extending an existing query.
Two weeks of silent cron failures. One Saturday-morning digest read.
Nightly GSC and GA data pulls had been silently killed by launchd TCC every night since 20 June. No alert, no log noise anywhere I was watching. Fourteen nights of missing numbers, surfaced by the telemetry digest during a routine Saturday-morning review.
Fourteen nights of missing telemetry: the four-part skeleton every new skill now inherits
The GSC and GA nightly crons had been logging clean exits and producing nothing for a fortnight. Found out on a Saturday. The fix was straightforward; what it exposed was a pattern gap: three telemetry reads with no single surface for their output. The skeleton that closed that is now the template every new read inherits.
Four fixes to pass AdSense: Google scores the estate, not the page
The UK Calculators readiness audit scored 7 of 8 green before submission. Eight days later, AdSense rejected the site on content quality. Closing the gap to re-submission required four separate fixes — telemetry, thin surfaces, media diversity, and hub listings — because Google scores the estate as a portfolio, not page by page.