Switch from Rybbit

Rybbit's exports don't use the file names and columns that misomoon's CSV import reads, so you write the files yourself. The dashboard export gives the daily totals. The API on a paid plan, or the database on a self-hosted Rybbit, gives the breakdowns per day. Your tracking calls keep their shape: window.rybbit.event('Signup', { plan: 'pro' }) becomes misomoon('Signup', { props: { plan: 'pro' } }). Goals, event properties, and identified users stay behind.

#Add misomoon next to Rybbit

1. Add your site in misomoon and paste its script tag into the <head> of every page, next to Rybbit's (Track your site).
2. Leave both scripts on for a week or two, until misomoon's numbers look right to you.

#Replace Rybbit's calls

Both calls take the event name first. misomoon puts the properties under props, and a property value is a string, a number, or a boolean.

Keep Rybbit's event names, such as signup_clicked. Imported events keep their names, so the days before and after the switch add up under one name.

The data-misomoon-* attributes need Tagged events, which a new site has on (Choose what to track). Rybbit has no revenue call, so revenue starts in misomoon. If a payment provider's webhook reports your sales instead, connect it and leave revenue out of the call, or each sale counts twice.

Goals don't move. Add each one again in Settings > Goals (Create a goal). A Rybbit goal on outbound clicks or form submits becomes a goal on the Outbound link or Form sent event. A goal counts the events misomoon already collected, so you can add it at any time.

#Bring your history

misomoon skips the days it already counted (Days that count once).

Rybbit Cloud's Free and Basic plans have no API keys, so on them only the daily totals and the chart can come across, from the dashboard export. Rybbit doesn't say which plans show the Export button.

#Export the daily totals

1. In Rybbit's dashboard, clear the filters and set the range to end today. The export holds the dashboard's current range and filters.
2. Click Export and unzip the download.
3. Open overview-timeseries.csv, the only file in the ZIP with a row per day. The other files hold totals for the whole range and have no date, so misomoon can't use them.
4. Write its rows into imported_visitors.csv with the columns below.

Rybbit doesn't document the columns of overview-timeseries.csv. The table uses the field names of the time-series API (overview/time-series with bucket=day), which returns the same daily numbers.

#Export the breakdowns

The breakdowns need Rybbit's raw events, one row per event:

• On Rybbit Cloud's Standard and Pro plans, page through GET /api/sites/:site/events with an API key, back from today, or from the day before you added misomoon to make fewer requests. The API allows 50 requests per 10 seconds, and 5,000 a day on Standard or 25,000 on Pro. Past the limit it answers 429 with a Retry-After header.

• On a self-hosted Rybbit, the events are in the events table of the analytics database. Open it with:

  shCopy

  docker exec -it clickhouse clickhouse-client --database analytics

Count the events per day in the misomoon site's time zone, because misomoon stores each row under its date in that time zone. Each file takes the visit columns for each value: visitors (distinct user_id), visits (distinct session_id), pageviews (events with type pageview), bounces (sessions with one pageview), and visit_duration (the seconds from each session's first event to its last, added up).

#Upload the files

1. Zip the files as rybbit-history.zip, with imported_visitors.csv among them.
2. In misomoon, open Settings > Integrations, click Upload CSV or zip, and pick rybbit-history.zip.

Imported days appear only in reports without filters (What imported data fills). If you uploaded the wrong file, delete the import and upload again.

#Remove Rybbit

Once the import shows in misomoon, remove Rybbit's script tag and its rybbit calls. Rybbit Cloud keeps your data for 3 years on Standard and 5 years on Pro. Keep your export files, so you can upload them again later.

#What stays behind

• The breakdowns, on Free and Basic. Only the daily totals come across there.
• Event properties. misomoon's CSV import reads none.
• Button clicks, copies, input changes, Web Vitals, and identified users. misomoon imports none of them.
• Goals and funnels. Add them again in misomoon.
• Time on page and scroll depth. Rybbit's events carry neither.
• Cities and hostnames. misomoon's CSV import reads no city, and a site with several hostnames gets their paths added together.
• Region names. Rybbit stores region codes, such as US-CA, and misomoon's own data names the region, such as California. The two sit on separate rows in Regions.
• Rybbit's channels. misomoon works out each channel from source, utm_medium, and utm_source.

#Sources

Checked on 2026-10-25.

• Rybbit: API getting started, get events, time series, dashboard export in the code, event fields in the code, managing your installation, script, custom events, goals, pricing