Analytics and Release Workflow Rollout

Kreativ Sound now tracks the parts of the site that directly affect releases: product clicks, outbound traffic, theme toggles, and 404 views. The goal is not to collect noise. The goal is to see whether visitors can find a product, open a tool, and leave for the right checkout or download page.

What changed

The release workflow now includes checks that run before deployment. The gate builds the Astro site, validates product data, checks thumbnail assets, verifies internal links, runs rendered smoke tests, exercises Preset Mutator, and collects Lighthouse scores.

That gives each publish a clearer pass/fail signal. If a product image is missing, a generated app route drifts, or a page falls below performance thresholds, the problem is caught before the public site changes.

Why it matters

The catalog changes often: new packs, Lite versions, tool routes, and old archive links all need to keep working together. A repeatable release check keeps those updates from depending only on manual browser review.

Monitoring notes were also added so uptime, analytics quality, and release health can be reviewed after each deployment. That keeps the public site focused on the user while still making operational problems visible.