NTE QUICK TOOLS MEASUREMENT ACTIVATION CHECKLIST
Last reviewed: 2026-05-29
Production site: https://ntequicktools.pages.dev
Analytics status: https://ntequicktools.pages.dev/analytics/status.json
Cloudflare Web Analytics setup: https://ntequicktools.pages.dev/analytics/cloudflare-web-analytics-setup.txt
Realtime test plan: https://ntequicktools.pages.dev/advertising/ga4-realtime-test-plan.txt

Why this exists
- This project is deployed as a static export: Next.js writes final HTML into out/.
- When using wrangler pages deploy out, NEXT_PUBLIC_* values must be present at build time.
- Setting a value only in Cloudflare after a direct-upload build will not change the already exported HTML.
- This checklist prevents a false-positive setup where a dashboard value exists but no analytics script is in the live static site.

Minimum activation env
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev
NEXT_PUBLIC_GA_MEASUREMENT_ID=G-XXXXXXXXXX
NEXT_PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN=59c9d05322724a16a43b1b8d83c17b7b

Build with the values you want embedded
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev \
NEXT_PUBLIC_GA_MEASUREMENT_ID=G-XXXXXXXXXX \
NEXT_PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN=59c9d05322724a16a43b1b8d83c17b7b \
npm run build

Verify the exported static files before deploy
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev \
NEXT_PUBLIC_GA_MEASUREMENT_ID=G-XXXXXXXXXX \
NEXT_PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN=59c9d05322724a16a43b1b8d83c17b7b \
npm run measurement:check

Deploy the verified static export
npm exec --yes wrangler@4.95.0 -- pages deploy out --project-name ntequicktools --branch main --commit-dirty=true

Verify the public site after deploy
NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev \
NEXT_PUBLIC_GA_MEASUREMENT_ID=G-XXXXXXXXXX \
NEXT_PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN=59c9d05322724a16a43b1b8d83c17b7b \
npm run live:check

GA4 pass criteria
- The public homepage contains googletagmanager.com with the configured G- measurement ID.
- GA4 Realtime shows a page_view after opening the production homepage.
- At least one safe revenue-loop event appears after following the realtime test plan.
- Current instrumented event count: 100.

Cloudflare Web Analytics pass criteria
- The public homepage contains static.cloudflareinsights.com/beacon.min.js.
- The beacon data attribute contains the configured token.
- Cloudflare dashboard begins showing page-level visits after traffic arrives.
- Setup packet and API automation entrypoint: https://ntequicktools.pages.dev/analytics/cloudflare-web-analytics-setup.txt.
- If an API token with the required Cloudflare Web Analytics permission is available, run npm run cloudflare:web-analytics or npm run cloudflare:web-analytics:create.

Safety boundaries
- This checklist does not prove traffic, ad impressions, clicks, RPM, sponsor payment, or first-dollar revenue.
- Do not publish private dashboard screenshots, payment details, tax data, identity data, or account tokens.
- Cloudflare Web Analytics is only page-level fallback measurement; GA4 is still needed for custom revenue-loop events.