Every visit, signup and payment, tied to one person.
Paste one snippet, or let your AI install it. Kissmetrics records your events itself and joins a person's devices once they sign up, log in or pay.
Paste one snippet, or let your AI do it.
# or install from your terminal$ npx @kissmetrics/install --api-key YOUR_KEY
The snippet, the terminal and the AI install all end in the same place.
Four events from day one, then the ones you choose
The snippet records four events on its own from the moment it lands: visited site, page view, search engine hit and ad campaign hit. The events that matter to your business, a signup, an order, a payment, you define once, with the AI install and ready-made schema examples to help.
- Visits, page views, search and ad campaign arrivals, captured on their own
- Signups, orders and payments defined once, with help
- Works on a site, a product, or both at once
Every event resolved to one person
A visitor who reads on their phone, signs up on a laptop and buys a few days later is one person. Each device is anonymous until the person signs up or logs in on it; from then on, everything they did on that device joins the same record. That is what makes retention, attribution and lifetime value measurable.
- Anonymous history follows a person once they sign up or log in
- One identity across devices, sessions and channels
- Every report counts people
- Company
- Acme Freight (sample)
- First channel
- LinkedIn Ads
- Last channel
- Organic search
- Plan
- Team plan (their product)
- Devices
- phone, laptop, work laptop
Server events on the same person
Not everything happens in a browser. Send events from your backend, from a webhook, or through Segment or Google Tag Manager, and they land on the same person as the events from your site. Past data from another tool comes in through our paid migration service.
- Server-side events on the same person
- Segment, Google Tag Manager, the mobile SDKs, Shopify and WordPress
- Past data through the paid migration service
| Source | Events | Status |
|---|---|---|
| JavaScript snippetBrowser, first-party | 701,300 | Connected |
| Server-side APIYour backend | 2,716 | Connected |
 StripeWebhooks to the server API: payments and plans | 1,388 | Connected |
 CalendlyWebhooks to the server API: booked demos | 640 | Connected |
How we handle identity
First-party cookies
The JavaScript tracker sets first-party cookies to keep one person’s actions together across pages. Every event is tied to a person identifier.
Cookie-free, from your server
Prefer no browser cookies? Send events through the server-side API instead. Nothing is stored in the visitor’s browser, though you supply the identifier yourself, so this is cookie-free rather than anonymous.
The Safari limit
One limitation worth knowing: Safari caps first-party cookies at seven days, so a visitor returning after longer than that can be counted as new.
Try it on your own data. Free to start, no card.
Install with AI in about 5 minutes.
No card required. Free plan. No developer needed for your website.