Require one server-side ModuleScript with your API key and it tracks players, sessions and servers on its own. Your code adds what only it knows: Robux purchases, credits and custom events.
Joins, leaves, time in server and players online are sent automatically from PlayerAdded, PlayerRemoving and a heartbeat. On shutdown everyone still in gets a clean leave.
Call analyse:purchase from ProcessReceipt for developer products and game passes. Pass the receipt's PurchaseId and a retried receipt is never counted twice.
Record a virtual currency spent or earned per item, and group items into categories so the revenue page shows where credits go.
The module reads LaunchData, ReferredByPlayerId and SourcePlaceId from join data, so tracked links, friend referrals, teleports and discovery each show as a traffic source.
When a player enters a code in your UI, send it with analyse:creatorCode and the rest of their session is attributed to the creator's campaign.
Each server reports its PlaceId as the deployment and the experience's GameId as the group, so a hub and its sub-places add up to one game.
A creator makes a video about your experience. You create a tracked link for the campaign and put it in the description instead of the plain game URL.
Players who join through the link carry its launch data, so their sessions and Robux purchases show under that campaign, next to players from discovery.
You add a Starter Pack developer product and record every ProcessReceipt with its product id and name.
The revenue page lists what the pack earns in Robux and who bought it, so you can see whether first-day players or returning players are buying it.
Your experience has a lobby place that teleports players into separate round places.
Each place reports as its own deployment within the experience, and arrivals from the lobby show as teleports instead of being mixed in with discovery.
Get the module from Downloads and insert it into ServerScriptService as a ModuleScript named Analyse. A Rojo project file is included.
In Roblox Studio, open Game Settings, then Security, and enable Allow HTTP Requests.
Copy the API key from your game's Settings, Integration and call Analyse.new from a server Script. Joins, leaves and sessions start right away.
Add analyse:purchase to ProcessReceipt, and credits, creator codes or custom events wherever your game handles them.
Call analyse:purchase inside MarketplaceService.ProcessReceipt with the amount spent, ROBUX as the currency and the receipt's PurchaseId. The id makes retries safe.
The module runs on the server only and errors if required from a LocalScript. Scripts in ServerScriptService never replicate to players, so the key stays on the server.
Yes. Joins are grouped into tracked links, referrals, teleports, creator codes and discovery, which covers joins from search or the home page with no link, referral or teleport.
Events are batched every 5 seconds, up to 1000 per request, and failed requests are retried with backoff. Delivery counters are available from analyse:stats.
If you run experiments from the dashboard, analyse:variant returns which variant a player is in and analyse:variantConfig returns that variant's settings.
Yes. Analyse is analytics for your own experience: players are never tracked across experiences, no advertising profiles are built, and your data is never sold or shared with ad networks. Roblox allows third-party analytics for your own experience, which is exactly what this is.
Free to start, 14 days of Pro, and about four minutes of setup.