Documentation
Quick start
All of JAMP in about a minute. Hand one prompt to your AI editor, or drop three scripts into your head. No cookies, no consent banner.
Grab your YOUR_WEBSITE_ID (and, for server errors, your source-map key) from the Settings page. Your dashboard also has a version of the prompt below with these already filled in.
1. The fast way: let your AI editor do it
Using Cursor, Claude Code, Copilot or similar? Paste this and it wires up every code-side pillar, analytics, performance, client errors, server errors and source maps, in the style of your codebase.
Set up JAMP monitoring in this project. JAMP is a privacy-first, all-in-one monitoring tool loaded from tiny drop-in scripts. It uses no cookies, so do NOT add a cookie or consent banner.
My website id: YOUR_WEBSITE_ID
1. Add these scripts to the <head> of the root layout (layout.tsx for Next.js, or index.html), each with the "defer" attribute so they never block rendering. If a version string or git commit SHA is available at build time, add a matching data-release="<version>" to every tag so each deploy is tracked.
- Analytics (required):
<script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/main.js"></script>
- Performance / real-user Core Web Vitals:
<script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/app.js"></script>
- JavaScript errors:
<script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/index.js"></script>
2. If this is a Next.js app, also capture server-side errors. In instrumentation.ts, add an onRequestError hook that fire-and-forget POSTs to https://jamp.io/api/errors/server with a JSON body of { website_id: "YOUR_WEBSITE_ID", key: "YOUR_SOURCE_MAP_KEY", message, stack, error_type, route, method }. It must never block or throw into the request.
3. If there is a CI or build step, upload source maps so stack traces are readable. After the production build, POST each .map file to https://jamp.io/api/sourcemaps keyed by the same release string, then strip the .map files from the deployed output so they are not served publicly.
Keep everything minimal and idiomatic to this codebase. Do not add analytics cookies or a consent banner.2. Or paste it yourself
Drop all three scripts into the <head> of your site. Analytics is required; the other two are optional, so delete whichever you do not want.
<!-- JAMP: analytics, performance, errors --> <script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/main.js"></script> <script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/app.js"></script> <script defer data-website-id="YOUR_WEBSITE_ID" src="https://jamp.io/index.js"></script>
For server-side errors, source maps and framework specifics, see Error tracking, Source maps and the full Installation guide.
3. Turn on the rest (no code)
Two pillars need nothing on your site at all, just a toggle in the dashboard.
- Uptime: enable it under Settings and JAMP checks your site every few minutes from our servers.
- Site audit: run one from Monitor → Site Audit to crawl for broken links, on-page SEO and trackers.
- Alerts: choose what pings you, and where (email, Slack, Discord), in the Alert Manager.
How to check it worked
Deploy, then open your site once. Your pageview shows up in the dashboard within seconds, and Settings flips each pillar to detected as its first data arrives. If nothing shows, confirm the data-website-id matches your site and that an ad-blocker is not stripping the script (the neutral main.js name avoids most, or use the first-party proxy for the rest).