Migrating
Migrating to Kymo is: add the tag, confirm events, then remove the old one. There is no data import — Kymo starts counting from the moment it is installed.
Steps
- Install Kymo alongside your current tool
Add the Kymo tag. Run it in parallel with your existing analytics for a day so you can compare and confirm events arrive.
- Verify
Confirm events land — see Verify.
- Remove the old tag
Delete the Google Analytics or Plausible snippet. Leaving it in place keeps setting cookies (in GA's case) and doubles your page weight for no benefit.
From Google Analytics
- Cookies go away. GA sets cookies and needs a consent banner. Kymo sets none — you can remove the banner GA required.
- No sampling. Kymo counts every event it receives; there is no threshold above which numbers become estimates.
- Uniques are defined differently. GA stitches sessions across days with a cookie. Kymo's unique is per UTC day by design — see Cookieless identity. Expect your unique-visitor number to differ; it is not wrong, it is a different definition.
- Events are simpler. Kymo has pageviews, outbound clicks, and goals — not an open-ended event schema.
From Plausible
Plausible is already cookieless, so the privacy story is familiar. The reason to switch is AI visibility: Kymo classifies AI crawlers, separates live AI-answer fetches from index sweeps, and confirms AI-referred humans — see AI visibility. Install is the same shape: one script tag.
Historical data
Neither migration brings history with it. Analytics data is tied to each tool's own identity model, and Kymo's cookieless daily hash cannot be reconstructed from another tool's records. If you need the old numbers, export them from the old tool before you remove it.