How artifacts are verified — and how staleness is shown
11 artifacts, 2 archived. The rule that runs this library: nothing stale is ever shown as current. Every artifact carries the date it was last checked, the sources it was checked against, and the date it will be checked again.
verified_on · checked against · next re-check · status · archived with a banner, never deleted
The stamps
- verified_on — the day the desk last opened the artifact and confirmed it against its sources (Google's release notes, help pages, API references — linked on the page).
- next re-check — quarterly at most; sooner when the change log records something that touches the artifact.
- status — current or archived. Archived artifacts stay online with a banner, dated, with the reason and the replacement where one exists.
What triggers a re-check
- A logged change whose product and topic match the artifact's "breaks on" list.
- The quarterly sweep (a dated reminder on the desk).
- A reader's report to team@datameasured.com — fixed or archived within a week, noted on the page.
What an artifact is
Something you can paste into your stack today: a GTM or gtag snippet, a BigQuery query against the GA4 export, a CSV template with the exact columns an import expects, a checklist written by menu path (never by screenshot), a reconciliation sheet. Each says what it does, what's inside, how to install it, and which changes can break it.
What this is not
- Not a scanner or a paid tool — the diagnoser is one artifact among the others.
- No packs, no agency tier at launch; decided later by demand. A consult-the-desk line is the only ask.
- No affiliate links. If one is ever added it is marked.