Skip to main content
Enrolling creates your account, your project and one website per domain, then gives you a snippet pinned to an exact tracker release. Serve your site over HTTPS; it is what Lumenstat is tested against.
1

Enroll your project

Open app.lumenstat.com/signup and fill in:
  • Project name and your email.
  • Domains you want to measure, one per line, for example example.org and docs.example.org. A leading www. is removed, so www.example.org and example.org are the same entry.
  • One Stellar link that ties the project to the ecosystem: your SCF project page on communityfund.stellar.org, a page on stellar.expert, stellarchain.io or lumenscan.io, a G… account address (checked on Horizon mainnet) or a C… contract address.
Depending on how the service is configured, your project is approved at once or waits for an SCF operator. Either way you land on the Setup page.
2

Paste the snippet

Copy the snippet from Setup into the <head> of every page. It looks like this, with your own website id:
Using a framework? See Framework recipes for Next.js, Vite, Astro, SvelteKit and Nuxt.
3

Confirm data is arriving

Visit your site in a normal browser, then open Setup again. Is data arriving? turns green with the page views from the last 24 hours. Your numbers are under Overview and Website.
Nothing showing? Check that the page is served over HTTPS, that the domain you visited is one you enrolled, and that the browser console shows no integrity error.
4

Add your API (optional)

On Setup, issue an ingest key and add a second OpenTelemetry exporter to your service. Your existing APM keeps full traces; Lumenstat keeps request counts, status codes and latency per route. Follow API analytics.

See the bot defense work

You can try to inflate your own numbers and watch Lumenstat refuse. From a clone of the repository, send scripted page views with forged browser headers:
Your page views do not move. The 20 events appear on the Website page under Flagged, not counted, with the reason no_proof. Bot and inflation defense explains each layer and how to test the others.

Next steps

Custom events

Count sign-ups, wallet connections and other actions.

Verify the tracker

Check the integrity hash yourself before you ship it.
Last modified on November 14, 2026