Import your analytics history into Vireo
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 | 404s | Clicks | Events |
|---|---|---|---|---|---|---|---|---|---|---|
| Google Analytics 4 | API | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes |
| Jetpack Stats | API | Yes | No | Yes | Yes | No | No | No | No | No |
| Koko Analytics | Same database | Yes | Yes | Yes | Yes | No | No | No | No | No |
| Statify | Same database | Yes | No | Yes | Yes | No | No | No | No | No |
| WP Statistics | Same database | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Burst Statistics | Same database | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No |
| Independent Analytics | Same database | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| SlimStat Analytics | Same database | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No |
| Plausible Analytics | CSV export | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Matomo | API | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No |
| Fathom Analytics | API | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| Simple Analytics | API | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| Clicky | API | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| Cloudflare Web Analytics | API | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
| Post Views Counter | Same database | Yes | No | Yes | No | No | No | No | No | No |
404s are missing pages. Clicks are outbound link clicks and file downloads. Events are custom events, goals and form submissions, where the source recorded them. Jetpack Stats, Statify and Post Views Counter record no visitors, so imported days carry pageviews. 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
Page views broken down by date, referring sites and clicks: Vireo gives you all three on your own server. Pageviews by day and referrers come across from Jetpack, and clicks on outbound links are recorded from the day you switch them on. Jetpack keeps its stats on WordPress.com rather than in your database, so Vireo fetches every day Jetpack recorded from the WordPress.com stats API.
From Koko Analytics
Koko Analytics stores its stats in your WordPress database, so Vireo copies them straight from Koko's tables.
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.
From Matomo
Vireo imports Matomo two ways. On a site running Matomo for WordPress, it reads Matomo's log tables from your WordPress database. For a self-hosted Matomo or Matomo Cloud, it asks Matomo's Reporting API for your history with the site address, site ID and an auth token.
From Fathom Analytics
Fathom counts visits on its own servers without cookies and shows them in its own dashboard. Vireo's Fathom importer asks Fathom's API for your history day by day and stores it in your WordPress database.
From Simple Analytics
Simple Analytics counts visits on its own servers without cookies and shows them in its own dashboard. Vireo's Simple Analytics importer asks its Stats API for your history day by day and stores it in your WordPress database.
From Clicky
Clicky counts visits on its own servers and shows them in its dashboard. Vireo's Clicky importer asks Clicky's API for your history with the site ID and sitekey and stores it in your WordPress database.
From Cloudflare Web Analytics
Cloudflare Web Analytics measures visits with a JavaScript beacon, added automatically on sites Cloudflare proxies or by a snippet you paste, and shows them in the Cloudflare dashboard. Vireo's importer reads that history through Cloudflare's GraphQL Analytics API and stores it in your WordPress database.
From Post Views Counter
Post Views Counter keeps its daily view counts in its own table in your WordPress database. Vireo reads the daily rows, for the whole site and for each post, and brings them across.
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, Jetpack Stats, Matomo, Fathom, Simple Analytics, Clicky and Cloudflare Web Analytics are read through their APIs, using a key you provide for the length of the import. Plausible is read from the CSV export you upload.
Imports add to what's already stored. Every importer skips days already imported, from any tool, so running one again only adds what's missing, and each run has an Undo this import link. Imports stop the day before Vireo's own data begins, so your imported history ends where Vireo's own counts start. Imported days sit alongside the traffic Vireo records itself.