Repository navigation
fix(analytics): send Cloudflare beacons from the browser - #629
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
harlan-zw
added
the
harlan-agent-review
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. 0d1c3349-dd81-45f9-b096-a921ef670828 |
harlan-github-agent
Bot
removed
the
harlan-agent-review
|
🤖 Agent verification by Codex: Loaded the production build's bundled beacon in a headless browser. Initial load and navigation sent three requests directly to Cloudflare reads show thousands of proxy requests after October 6 while recorded page views almost disappear. Cloudflare documents that RUM cannot collect Worker subrequests: https://developers.cloudflare.com/web-analytics/faq/#can-i-use-real-user-monitoring-rum-with-cloudflare-workers Production deployment passed: https://github.com/skilld-dev/skilld.dev/actions/runs/38241485542 Cloudflare activated Worker version |
harlan-github-agent
Bot
added
harlan-agent-ready
![harlan-github-agent[bot]](https://avatars.githubusercontent.com/in/4579275?s=60&v=4){kind=small}
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
harlan-github-agent
Bot
removed
the
harlan-agent-ready
1 participant
🔗 Linked issue
❓ Type of change
📚 Description
Browser analytics almost disappeared after events began passing through the Worker proxy. Successful page requests continued.
Disable the Cloudflare Web Analytics proxy while keeping the beacon bundled. Events now go directly from browsers to Cloudflare. Cloudflare documents that RUM cannot collect Worker subrequests.