Bring your history with you
Changing analytics tools usually means your charts start again at zero. Vireo imports your old numbers first, so they run straight through. The table shows what comes across from each source.
| Source | How | Pageviews | Visitors | Pages | Referrers | Countries | Devices |
|---|---|---|---|---|---|---|---|
| Google Analytics 4 | API | Yes | Yes | Yes | Yes | Yes | Yes |
| Jetpack Stats | API | Yes | No | Yes | Yes | No | No |
| Koko Analytics | Same database | Yes | Yes | Yes | Yes | Yes | Yes |
| Statify | Same database | Yes | No | Yes | Yes | No | No |
| WP Statistics | Same database | Yes | Yes | Yes | Yes | Yes | No |
| Burst Statistics | Same database | Yes | Yes | Yes | No | No | No |
| Independent Analytics | Same database | Yes | Yes | Yes | No | No | No |
| SlimStat Analytics | Same database | Yes | Yes | Yes | Yes | Yes | No |
| Plausible Analytics | CSV export | Yes | Yes | Yes | Yes | Yes | Yes |
Koko Analytics brings countries and devices only with Koko Analytics Plus data. Jetpack Stats has no visitor counts, so imported days use views for both. Statify records no visitors by design. Each guide has the details.
From Google Analytics 4
Vireo reads your GA4 property through Google's Analytics Data API and stores the history in your WordPress database, in the same tables as the traffic it records itself.
From Jetpack Stats
Jetpack keeps its stats on WordPress.com rather than in your database, so Vireo fetches them from the WordPress.com stats API for the date range you choose.
From Koko Analytics
Koko Analytics stores its stats in your WordPress database, so Vireo copies them straight from Koko's tables. If you also run Koko Analytics Plus, its country and device stats can come across too.
From Statify
Statify keeps one row per view with the date, the referrer and the page. Vireo reads that table and brings the views and referrers across.
From WP Statistics
WP Statistics stores page views per day and one row per visitor per day. Vireo reads both, so pageviews and visitors carry over with the same meaning they had before.
From Burst Statistics
Burst Statistics stores one row per hit with a timestamp and a visitor ID, so Vireo can work out both pageviews and daily visitors from it.
From Independent Analytics
Independent Analytics stores each view with its page and session. Vireo reads those tables to rebuild daily pageviews, daily visitors and per-page numbers.
From SlimStat Analytics
SlimStat stores one row per pageview with a timestamp, the page, the post ID, the referrer and a country code. Vireo reads that table and rebuilds daily numbers from it.
From Plausible Analytics
Plausible lets you export a site as a zip of CSV files. Vireo's Plausible importer reads that export, so there's no API key to hand over, and it works the same for Plausible Cloud and self-hosted Community Edition.
How importing works
Every importer lives under Vireo Analytics, then Settings, on the Import & export tab. The plugin importers read the other plugin's tables in your own database and never change them. Google Analytics and Jetpack Stats are read through their APIs, using a key you provide for the length of the import.
Imports add to what's already stored. Running the same history twice counts it twice, so import each source once. Imports stop the day before Vireo's own data begins, so the days it already counted aren't added twice. Imported days sit alongside the traffic Vireo records itself.