Users and sessions
Count unique browser visitors and sessions, then connect an anonymous journey to an internal Django user ID after login.
Website and product analytics for Django developers
Django analytics connected to the code behind every journey
Measure traffic, sessions, users and conversions beside Django errors and slow requests, so the dashboard explains both what visitors did and what stopped them.
Consent-aware · No credit card · Errors and conversions together
A smaller, more useful dataset
The analytics a Django developer checks before shipping a fix
FetchNode focuses on the questions that connect product usage to production health. It is deliberately not an advertising platform or a warehouse of hundreds of reports.
Pageviews and top pages
See which routes people actually use without treating every backend or static request as a pageview.
Traffic sources
Understand referrers and campaign parameters behind a session before looking at the errors it encountered.
Key events
Track explicit product milestones such as signup_completed, checkout_started or invoice_paid.
Conversion
Calculate how many unique users reached a chosen milestone, not how many times one user repeated it.
Error impact
Move from a traffic chart to the Django issue, route or slow request that interrupted the same customer journey.
Google Analytics answers marketing questions
Keep Google Analytics when you need its ecosystem
Google Analytics is suited to broad acquisition reporting, advertising integrations, audiences and established marketing workflows. FetchNode does not try to reproduce every GA report.
Use it alongside FetchNode when a marketing team depends on those capabilities. The numbers can differ because tools apply different consent, bot, identity, session and timezone rules.
FetchNode answers developer questions
Use one view when product health is the goal
FetchNode is useful when the next question after “conversion dropped” is “did a Django error or slow request cause it?” Traffic, key events, backend requests and grouped errors share one website project.
- One definition for each visible metric, with dashboard tooltips.
- Project-level environments and releases for deployment context.
- A portfolio overview for freelancers, agencies and founders managing several Django sites.
Consent-aware by design
Your cookie banner remains the control point
Loading the FetchNode browser script does not have to mean collecting analytics. Pageviews, sessions, identity and custom product events remain off until your site grants analytics consent.
Error tracking can be handled separately according to your privacy policy and legal basis. FetchNode’s generated Django configuration also keeps headers, bodies, IP addresses, query strings and SQL text off by default.
See the Django error-monitoring defaultsExample consent flow
// Analytics stays off by default.
FetchNode("init", { projectKey: "..." });
// Run after the visitor accepts analytics.
FetchNode("consent", { analytics: true });
// Track a milestone that matters to your app.
FetchNode("track", "signup_completed", {
plan: "free"
});On logout, call FetchNode("reset") so a shared browser is not left connected to the previous internal user ID.
Django analytics FAQ
Know what the dashboard is—and is not—measuring
What analytics can FetchNode collect for a Django website?
After analytics consent, FetchNode can collect pageviews, sessions, traffic sources, internal user IDs and explicitly tracked key events such as completed signups or paid invoices.
Does FetchNode replace Google Analytics?
Not for every use case. Google Analytics has a broader advertising and marketing-reporting ecosystem. FetchNode is a focused option for Django developers who want traffic and conversion data connected directly to application errors and backend performance.
Does FetchNode analytics run before cookie consent?
No. Browser pageviews, sessions, identity and product events remain disabled until the site explicitly grants analytics consent to the FetchNode snippet.
Measure one real Django journey
Connect one website, grant analytics consent in your test browser and verify a pageview, internal user ID and key event before rolling it out further.