NTE QUICK TOOLS CLOUDFLARE WEB ANALYTICS SETUP PACKET
Last reviewed: 2026-07-13
Production site: https://ntequicktools.pages.dev
Host: ntequicktools.pages.dev
Analytics status: https://ntequicktools.pages.dev/analytics/status.json

Why this matters
- AdSense approval and first-dollar revenue still depend on Google review, real traffic, and ad serving.
- Cloudflare Web Analytics gives a lightweight page-level traffic fallback while GA4 is not fully configured.
- It does not replace GA4 custom events, Search Console, AdSense reports, or first-dollar proof.

Current site integration
- NEXT_PUBLIC_CLOUDFLARE_WEB_ANALYTICS_TOKEN configured at build time: yes
- Current token value in this build: 59c9d053... (public token redacted)
- Pages project Web Analytics enabled/associated: yes
- Pages project evidence status: enabled-token-mismatch (checked 2026-07-14T03:09:12.153Z)
- The app-owned beacon loads only when a public token exists and the Pages project is not already associated with Web Analytics.
- When Pages-managed Web Analytics is enabled, the app suppresses its manual beacon so Cloudflare can inject exactly one snippet on deployment.
- Because the site is deployed as a static export, Cloudflare dashboard env changes alone do not rewrite the already exported HTML.

Official Cloudflare setup paths
- Dashboard setup guide: https://developers.cloudflare.com/web-analytics/get-started/
- Cloudflare Pages one-click path: Workers & Pages > ntequicktools > Metrics > Enable under Web Analytics.
- Manual site path: Cloudflare dashboard > Web Analytics > Add a site > set hostname > copy JS snippet.
- API docs: https://developers.cloudflare.com/api/resources/rum/
- API endpoints used by the automation:
  GET /accounts/{account_id}/rum/site_info/list
  POST /accounts/{account_id}/rum/site_info
  GET /accounts/{account_id}/pages/projects/{project_name}
  PATCH /accounts/{account_id}/pages/projects/{project_name}

Local automation
- The script never prints or stores private Cloudflare API tokens.
- It reports only a redacted prefix for the public site token and never prints private Cloudflare API credentials.
- To only inspect status when an API token exists:
  CLOUDFLARE_ACCOUNT_ID=0ea85d9ab8e1d654ac20537baf87e3ff CLOUDFLARE_API_TOKEN=... npm run cloudflare:web-analytics
- To create the Web Analytics site if missing:
  CLOUDFLARE_ACCOUNT_ID=0ea85d9ab8e1d654ac20537baf87e3ff CLOUDFLARE_API_TOKEN=... npm run cloudflare:web-analytics:create -- --host ntequicktools.pages.dev
- To discover/create the site and associate it with the ntequicktools Pages project in one run:
  npm run cloudflare:web-analytics:activate -- --host ntequicktools.pages.dev

After Pages association is enabled
1. Refresh Cloudflare evidence so data/cloudflare-web-analytics.json records the association:
   npm run cloudflare:traffic:oauth -- --start <YYYY-MM-DD> --end <YYYY-MM-DD>
2. Rebuild without adding a second manual Cloudflare beacon:
   NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run build
3. Verify that the static export has no app-owned duplicate beacon:
   NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run measurement:check
4. Deploy through the repository deployment command:
   npm run deploy:cloudflare
5. Recheck the public site and confirm it contains exactly one Cloudflare beacon:
   NEXT_PUBLIC_SITE_URL=https://ntequicktools.pages.dev npm run live:check

Current known limitation
- The existing wrangler OAuth session can read the Pages project and GraphQL analytics, but RUM site inventory still requires Account Settings Read.
- The current Pages project status is enabled-token-mismatch; a locally embedded standalone token does not prove the Pages project association is active.
- Enable Web Analytics in the Pages project dashboard or provide a temporary API token with Account Settings Read/Write and Account Analytics Read.
- Do not put API tokens, payment data, identity data, bank data, tax data, or login codes into NEXT_PUBLIC_* variables.

Pass criteria
- Pages Project API reports a non-empty Web Analytics tag/token association.
- Public homepage contains exactly one static.cloudflareinsights.com/beacon.min.js reference.
- Cloudflare dashboard starts showing page-level visits after traffic arrives.
- /analytics/status.json changes cloudflareWebAnalytics.configured to true only after Pages project association evidence is enabled.