A proxy lets you route EazyData analytics traffic through your own domain. Instead of a visitor's browser sending requests to a third‑party analytics URL, those requests go to a path on your site (for example, /analytics), and your server quietly forwards them to EazyData. This simple change improves reliability when ad blockers are present, gives you more control over security and logging, and keeps your analytics endpoints consistent with your brand domain.
You can think of a proxy as a helpful receptionist at your front desk. All analytics requests come to your domain first. The receptionist checks that they look correct, adds any details your server needs (like cookies or headers), and then passes them along to EazyData. Replies come back to the receptionist, who hands them to the browser. Visitors never need to talk to a separate analytics host, and your site remains the single, trusted origin for requests.
In a Next.js app, a proxy is typically implemented using rewrites in next.config.js or by creating lightweight route handlers that forward requests. The browser calls paths on your site, such as /api/sessions/start or /api/events. Your server receives these and forwards them to EazyData's API, preserving essential headers and cookies so sessions remain accurate. Because the origin is your domain, common blocking lists are far less likely to interfere.
This approach keeps authentication and CORS simple. Your middleware can allow your own origin by default, apply security headers, and log requests centrally. For most teams, a proxy reduces edge cases, minimizes support overhead, and produces cleaner, more consistent analytics.
Any endpoint used by EazyData can be proxied through your domain, including session starts, page views, custom events, and heartbeat or live session queries. Your server forwards only the necessary request body and headers, then returns EazyData's response to the browser. This preserves visitor and session identifiers and ensures your analytics state remains in sync, even for single‑page apps or complex caching setups.
Proxied traffic also gives you the option to add observability. If you choose, you can log request rates or errors at your edge, set up alerts for unusual spikes, or temporarily rate‑limit abusive traffic — all without changing the analytics behavior for normal visitors.
The exact configuration depends on how you deploy Next.js, but the steps are straightforward. First, decide the public paths you want to expose (for example, /api/sessions and /api/events). Then configure your rewrites or route handlers so those paths forward to EazyData. If you use rewrites, your Next.js server handles the forwarding transparently; if you use route handlers, you can enrich the request (for example, attach cookies) before sending it on.
After setting up the proxy, load your site and check that a visit appears in the EazyData dashboard. Navigate across a few pages to confirm page views are recorded, and trigger a simple custom event to ensure event forwarding works. Because traffic now originates from your domain, you should see fewer issues with blockers and consistent results across all browsers.
If your organization has stricter compliance needs, a proxy is often the best fit. You keep control over the inbound endpoint, you can apply your own policies or audits, and you still benefit from EazyData's analytics accuracy and performance.
A proxy reinforces privacy by keeping analytics requests under your domain and limiting what is forwarded to only what’s necessary. EazyData uses anonymous identifiers for visitors and sessions; personal data is not required for measurement. If your region or legal requirements call for consent, you can delay initializing the client script or proxy endpoints until consent is granted, and continue to route everything through your own origin.
Combined with client‑side and server‑side tracking, a proxy offers a robust, flexible setup: real‑time behavior in the browser, reliable revenue attribution on the server, and a single, trusted domain for all analytics traffic.