Skip to content

docs(docs): Clarify Cloudflare analytics setup - #12

Merged
WillieCubed merged 1 commit into
mainfrom
cloudflare-guidance-audit
Sep 24, 2026
Merged

WillieCubed merged 1 commit into
mainfrom
cloudflare-guidance-audit

Conversation

@WillieCubed

Copy link
Copy Markdown
Contributor

TL;DR

The analytics setup guides now give complete, repeatable steps for Cloudflare account tokens, the collector domain, and Web Analytics tokens on LVBT sites.

Overview of Changes

The production runbook describes account-owned deploy and report tokens with their account and zone limits, the exact GitHub secret destinations, and a check before changing an existing events DNS record. It keeps the collector secret and weekly report setup in the same guided sequence. The site integration tutorial explains when lasvegasfortransit.org subdomains share the organization's Web Analytics token and when a separate domain needs its own property. The rotation guide preserves the existing property if Cloudflare will not accept a replacement for the same hostname.

The documented setup was checked against Cloudflare's current Web Analytics setup and FAQ pages and the owner's observed dashboard labels. pnpm check passes.

Follow-ups

The repository still uses repository-tooling v0.2.8. Updating the standard and the published package scope is a separate change so the guide review can land on its own.

Document account-owned deploy and report tokens, a safe custom-domain
check, and Web Analytics token setup for each hostname family.

Co-authored-by: Codex <noreply@openai.com>
@WillieCubed
WillieCubed merged commit 8ba1ea0 into main Sep 24, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant