#analytics

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

PEARL Nueroscience @amyegan I replaced 'unique-path' with my project ID and it still gives me a 404 error. Can you please help?

BestCodes NO. I refuse to be jealous of your website's traffic numbers Just kidding, that's a super cool idea I might have to try this. Do you have any plans to open-source it?

Neeeophytee Thanks! Yeah it's been fun to dig into. Here's the dashboard with realtime data from my own site if you want to poke around: https://botwatcher.vercel.app/demo Not open-source yet but it's something I'm seriously thinking about for the core detection layer. Right now the bot signature list is the part that needs the most community input since new bots show up constantly. Saw that you built Discraft and that it deploys to Vercel. If you want to see what's hitting bestcodes.dev I can get you set up in a few minutes. Just the log drain, one CLI command and you'd have a live dashboard. Happy to host it for free while I'm looking for early feedback. DM me on TG (@tradeyst) or hit me at shilpa@agentarena.site if you want to try it.

Pauline P. Narvas Sharing this with the rest of the community too - amazing session! https://community.vercel.com/t/community-session-why-i-built-databuddy/20366?u=pawlean

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

PEARL Nueroscience Looks like the unique-path/script.js file is not working, it's returning a 404 error. Can anyone please help?

Pauline P. Narvas Hey, Paul! Welcome to the Vercel Community **Analytics Drains are project-scoped, not environment-scoped.** When configuring a Web Analytics Drain, you can only select which **projects** should send data to your endpoint. There's no native option to filter by environment (production vs. preview/development) for Web Analytics drains. However, each analytics event **does include** a `vercelEnvironment` field (with values like `"production"`) in the payload, so you can filter events on the receiving end. Since you can't configure environment-level filtering at the drain level for Web Analytics, the recommended approaches are: 1. **Filter at your ingestion endpoint**: Configure a single drain and have your receiving endpoint inspect the `vercelEnvironment` field in each event, routing production events to your production analytics store and dev/preview events elsewhere. 2. **Use a middleware/proxy**: Set up an intermediary endpoint that receives all events and routes them to different backends based on the `vercelEnvironment` value. 3. **Use sampling + filtering**: If you primarily care about production data, set a low sampling rate and filter by environment at ingestion time. Here are some relevant documentation: * https://vercel.com/docs/drains/using-drains * https://vercel.com/docs/drains/reference/analytics * https://vercel.com/changelog/you-can-now-configure-advanced-sampling-rules-for-vercel-drains * https://vercel.com/docs/drains

Hercules 8202 Yeah this is would be really nice to have

naaiyy +1 on this !

Pauline P. Narvas Thank you for the detail. We've shared with our engineering team and will loop back!