Back to rankings

Replit Launches Project Analytics for Published Apps

ReplitView original changelog

Replit introduced Project Analytics, a built-in usage-analytics dashboard for published web apps accessible directly from the Growth pane. It surfaces visitor trends, popular pages, traffic sources, and geographic, browser, and device data, letting developers understand how their app is being used without adding a third-party analytics tool. Paid plan subscribers can go further and ask Agent to set up custom event tracking and funnel analysis for conversions like sign-ups or purchases.

Key Takeaways

  • Replit added Project Analytics, a native usage-tracking dashboard built directly into the Growth pane of every published app.
  • The dashboard covers visitor trends, popular pages, traffic sources, geography, browsers, and device types without requiring an external analytics service.
  • Turning it on requires enabling analytics and republishing the app, after which data collection begins going forward, not retroactively.
  • Paid plan subscribers can request custom event tracking and funnel analysis through Agent, letting them measure specific conversions like sign-ups or purchases.
  • The feature reduces reliance on third-party tools like Google Analytics or PostHog for basic usage insight, keeping more of the app lifecycle inside Replit.
  • It extends Replit's recent pattern of consolidating post-launch tooling (SEO Agent, Growth Skills, now analytics) into the same Growth-focused surface used to grow published apps.

Analytics Built Into the Growth Pane

Replit introduced Project Analytics, a native usage-tracking dashboard for any published web app, accessible directly from the Growth pane inside the workspace. Instead of wiring up Google Analytics, PostHog, or another third-party script, developers can now see how people are actually using their app without leaving Replit.

What It Shows

The dashboard surfaces visitor trends over time, the most popular pages within an app, where traffic is coming from, and breakdowns by geography, browser, and device type. That gives builders a baseline read on who is visiting their app and how, information that was previously only available by adding an external analytics integration.

Turning It On

Project Analytics is opt-in: developers enable analytics for their app and then republish it before data starts flowing in. Because collection begins going forward rather than retroactively, apps that want historical usage data need to turn the feature on as early as possible.

Custom Events and Funnels for Paid Plans

For developers on a paid plan, Project Analytics extends further through Agent. Rather than manually instrumenting event tracking, subscribers can ask Agent to set up custom events and funnel analysis for specific conversions, such as tracking how many visitors complete a sign-up flow or finish a purchase. That puts conversion-focused analytics, normally the domain of dedicated product-analytics tools, within reach of a single Agent prompt.

Why It Matters

Project Analytics continues a pattern Replit has been building over the past few months: features like the SEO Agent and Growth Skills already extended Replit's reach past the build phase and into what happens after an app ships. Native analytics closes an obvious gap in that story, giving developers a reason to keep monitoring and iterating on a published app inside Replit rather than exporting to a separate analytics stack the moment it goes live.