Quickstart: Sypnia Cloud
From nothing to your first session and your first problem on Sypnia Cloud, in five steps and about ten minutes.
Cloud This page is for anyone with a web app and no Sypnia yet. It uses Sypnia Cloud, where we run the engine for you: there is nothing to deploy. To run the engine yourself, use the self-host quickstart instead; the snippet in your app is the same.
At the end you will have: your app sending to Sypnia, your own visit listed as a session, and one problem that you caused on purpose.
You need: a web app you can edit and run, and about ten minutes. The free tier is enough.
Create a project
Open
https://app.sypnia.com, create an account, and create a project. Name it after your app; the examples here useShop.You should seeThe project’s page shows its ingest key, which starts withspk_, and says it is waiting for the first event. Keep the page open.The ingest key is public. It can only send data to this project, so it is safe in your app’s code.
Add the SDK to your app
npm
npm install @sypnia/browserimport { init } from '@sypnia/browser'; init({ project: 'YOUR_PROJECT_KEY' });pnpm
pnpm add @sypnia/browserimport { init } from '@sypnia/browser'; init({ project: 'YOUR_PROJECT_KEY' });yarn
yarn add @sypnia/browserimport { init } from '@sypnia/browser'; init({ project: 'YOUR_PROJECT_KEY' });bun
bun add @sypnia/browserimport { init } from '@sypnia/browser'; init({ project: 'YOUR_PROJECT_KEY' });script tag
<script async src="https://ingest.sypnia.com/v1/sdk.js" data-project="YOUR_PROJECT_KEY"></script>No build step and no
initcall: paste it before</head>. The tag starts Sypnia with the key indata-project.Put the
initcall where your app starts, before it renders:src/main.ts,src/main.tsx,src/index.js. Then replace it with this fuller version, with your own key:src/main.ts import { init } from '@sypnia/browser'; init({ project: 'spk_7d1f0c9e4b8a2f6d3c5e1a9b0f4d8c2e', environment: location.hostname === 'localhost' ? 'development' : 'production', });The
environmentline keeps your own testing apart from your customers: on your machine the app reports asdevelopment, everywhere else asproduction. Alerts are only sent forproduction.Using Next.js? Follow Next.js for this step and come back. Using an AI app builder? See Lovable, Bolt, v0 and Replit.
You should seeYour app builds and runs as before. Nothing looks different.Open your app and check that it sends
Run your app, open it in a browser, and click on a few things. Open the browser’s developer tools, tab Network, and type
ingestin the filter.You should seeWithin 10 seconds, aPOSTrequest tohttps://ingest.sypnia.com/v1/ingest/eventswith status200. Its answer looks like{"accepted": 5, "dropped": 0}.If there is no request, or it is red, go to Troubleshooting.
See your first session
Go back to Sypnia and open Sessions. Choose the environment
development.You should seeWithin 10 minutes, one session: yours. It lists the pages you opened and what you clicked, in words: «Clicked Add to cart».The session is anonymous: Sypnia does not know who you are until your app says so. That is one more line, in Identifying people.
Cause your first problem
Add one line after
init, save, and reload your app once:src/main.ts import { init, reportError } from '@sypnia/browser'; init({ project: 'spk_7d1f0c9e4b8a2f6d3c5e1a9b0f4d8c2e', environment: location.hostname === 'localhost' ? 'development' : 'production', }); reportError(new Error('Sypnia test: the cart total is missing'));Then open Problems in Sypnia, in the environment
development.You should seeWithin 2 minutes, one new problem. Its first title is the technical one,Error: Sypnia test: the cart total is missing. A moment later the agent replaces it with a sentence in plain words and says who it hit (1 person), since when, and where in your code.Remove the line again. In real use you never call
reportErrorfor this: errors nobody caught are reported by themselves.
What you have now
- Every visit to your app is a session, with its pages and clicks.
- Errors, slow pages, slow and failing API calls, and rage and dead clicks are captured without more code.
- Sessions where something goes wrong are recorded, with everything a person types masked.
- Problems arrive as sentences, with the prompt for your coding agent.
Do these next
| To get | Do |
|---|---|
| The whole loop once, with a rage click, a replay and the fix | Your first problem |
| «Since yesterday’s change», and your own file names in stacks | Set release and upload source maps: Source maps in CI |
| «3 people», with their names | Identifying people |
| The request followed into your backend | Node, Next.js or OpenTelemetry |
| Your coding agent reading problems by itself | Install with your coding agent |
| To know what is sent and what never is | Privacy and masking |
When you deploy, your app reports as production and Sypnia starts sending alerts and the daily summary by e-mail.