[DPS-XXXX] Event spec validation metrics

[Gleb Lobov (gleb-lobov)]

No description provided.

[github-actions]

Missing SEO metadata

The following markdown files are missing required metadata fields:

• release-notes/event-specification-validation-results-in-console/index.md: missing fields: keywords, sidebar_label

Required fields

The file metadata is important for SEO and marketing. All markdown files, except for those with filenames starting with _, should include:

• title: Full, descriptive page title
• sidebar_label: Short title for navigation sidebar (can be the same as the main title)
• description: One to two sentences summarizing the page contents
• keywords: Array of marketing/SEO keywords

Please add the missing metadata.

[claude]

Style review

Solid, well-structured addition overall: the new data-quality page follows description → categories → per-view sections, stays within four H2s, precedes every heading and table with prose, uses imperative sentence-case headings, links out to Fundamentals instead of re-explaining, and has descriptive alt text on every image. Frontmatter is complete on the docs page and matches release-notes/_README.md on the release note. All internal links and anchors in the diff resolve, and no external URLs were added.

A few things worth fixing.

1. Garden-path sentence and past tense in the category intro

docs/event-studio/tracking-plans/data-quality/index.md:16

Console sorts every event that the pipeline associated with a published event specification into one of four categories:

The reader hits "the pipeline associated" and expects "associated X with Y", so the sentence has to be re-parsed. The past tense also conflicts with the style guide's "stay in the present tense" rule. Suggest:

Console sorts every event that the pipeline matches to a published event specification into one of four categories:

2. Non-parallel list of the four categories

docs/event-studio/tracking-plans/data-quality/index.md:5 (frontmatter description) and docs/event-studio/tracking-plans/index.md:26

how many of them were valid, inferred, had violations, or failed

"were valid, inferred, had violations" breaks the parallel — "were" doesn't carry over to "had violations". Suggest "were valid or inferred, had violations, or failed" in both places.

3. Category names are inconsistent across the PR

The new page establishes the canonical set: "valid events, inferred events, events with violations, and failed events". Several other places shorten it differently, e.g. docs/event-studio/event-catalog/index.md:34:

split into valid, inferred, violations, and failed events

This mixes adjectives and nouns ("violations ... events"). The same shortened form appears in the release note description and in a couple of the new alt texts. Where the full names don't fit, "split by category" plus the link to the data quality page reads better than a half-abbreviated list. Worth picking one form and using it everywhere.

4. "decides" and "Failed events counts"

docs/event-studio/tracking-plans/data-quality/index.md:39

The Data quality rules button in the page header decides whether events that fail validation count as events with violations or as failed events.

A button doesn't decide; "controls whether" or "determines whether" is more precise.

Also :29: "Failed events counts come from…" → "Failed event counts come from…".

5. Event Catalog Volume cell is overloaded

docs/event-studio/event-catalog/index.md:34 — every other cell in that table is a short noun phrase; this one is now two sentences plus a link, which throws off the table. Suggest trimming to something like:

The number of events collected in the last 30 days on the selected pipeline, split by category. See Monitor tracking plan data quality in Console

…or moving the "See" sentence into the prose above the table.

6. Pipeline selector bullet: punctuation and UI bolding

docs/event-studio/event-catalog/index.md:45

• Pipeline selector: choose the pipeline for the volume and last seen columns. It defaults to your production pipeline

Two issues. The style guide's list rule is "no period at the end unless the item contains multiple sentences" — this has two sentences and no final period, unlike its single-sentence siblings. And the column names aren't bolded here, while the new data-quality page bolds Volume and Last seen as UI elements (CLAUDE.md: bold for UI elements). Suggest collapsing to one clause:

• Pipeline selector: choose the pipeline used for the Volume and Last seen columns; it defaults to your production pipeline

7. Release note date is a day ahead

release-notes/event-specification-validation-results-in-console/index.md:4 uses date: "2026-09-18" while the docs page uses 2026-09-17. Intentional (scheduled publish), or a typo?

Minor / optional

• Raw <img> in the release note. Line 15 uses <img src={require('./images/data-quality-panel.png').default} …>; every other release note in the directory uses markdown ![alt](images/…). Fine to keep if the maxWidth: 496px constraint matters, otherwise match the convention.
• Duplicated image binaries. data-quality/images/event-catalog-volume.png is byte-identical to event-catalog/images/event-catalog-overview.png, and data-quality/images/tracking-plan-data-quality.png is byte-identical to create-and-manage/images/tracking-plan-overview.png. Referencing the existing files with a relative path would avoid two copies drifting out of sync.
• Drive-by: the line you touched at event-specification-inference/index.md:18 ends "in the Console" — the style guide says Console takes no article. The rest of that file has the same pattern, so it's pre-existing and out of scope; just easy to fix on a line you're already editing.

[Gleb Lobov (gleb-lobov)]

Raw in the release note. Line 15 uses <img src={require('./images/data-quality-panel.png').default} …>; every other release note in the directory uses markdown . Fine to keep if the maxWidth: 496px constraint matters, otherwise match the convention.

This is odd, but looks like it's the only one way to not blow up the image to be way too big

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	documentation	467f9db	Commit Preview URL Branch Preview URL	Sep 22 2026, 08:27 AM

[Simone Poggiali at Snowplow.io (gibbok-snowplow)]

tracking plan => Tracking Plan
please double check in other parts too

[Gleb Lobov (gleb-lobov)]

Actually no, we call them lower case. I prefer the entities to be capitalized, but this is not what we are doing in general

[Simone Poggiali at Snowplow.io (gibbok-snowplow)]

look here please "What is a Tracking Plan"

https://docs.snowplow.io/docs/fundamentals/tracking-plans/

[Simone Poggiali at Snowplow.io (gibbok-snowplow)]

ok I checked more probably the example I provided should be changed too to lower case... anyway, maybe claude can do it for us

[Simone Poggiali at Snowplow.io (gibbok-snowplow)]

LGTM, I approve so I do not block you, but fix (if not done ready)
warning:
Missing SEO metadata

plus revise the capitalization in the headers to make it consistent with the rest

[Gleb Lobov (gleb-lobov)]

LGTM, I approve so I do not block you, but fix (if not done ready)
warning:
Missing SEO metadata

I've addressed it already

[Gleb Lobov (gleb-lobov)]

plus revise the capitalization in the headers to make it consistent with the rest

I think it already is consistent with the CLAUDE.md

CLAUDE.md, line 28: "Not proper nouns: entities, events, schemas, data structures, tracking plans"