fivebar

Importing from Google Analytics

Copy page
View Markdown
Open with
Connect MCP
Claude Mistral Vibe Cursor VS Code

A site’s history comes over from its Google Analytics 4 property, read once with your permission.

Open Import in the site’s settings and choose Continue to Google. Sign in to the Google account that can read the site’s Google Analytics 4 property, and let fivebar see your Google Analytics data. Back on fivebar, choose the property and press Import. It takes up to 10 minutes: reload Import to see how it went.

What’s read

fivebar reads the property’s daily reports once, from the day it was made to two days before today in its time zone, as Google may still be processing the last two, and keeps no access: it gives the access back to Google as the import ends. Where that leaves days out, the import says so, and importing again a day or two later brings them over. Only the property’s web traffic on the site’s domain, or a subdomain of it, comes over, and its sources come without a referrer. Google dates its days in the property’s time zone, which the import says where it differs from the site’s.

Google leaves out some small counts, groups rarely seen values into one it calls (other), which fivebar leaves out, and can estimate figures from a sample. Where a report runs past 250,000 rows in 92 days, fivebar leaves out its least viewed. The import says where any of these happened.

Visitors

Google Analytics counts visitors by its cookie, where fivebar sets none, so the two can differ for the same traffic. See Visitors on imported days.

When an import fails

An import fails where Google refuses part of it, where the property’s limit at Google runs out, where it takes longer than 10 minutes, where Google has no days fivebar hasn’t already got, or where fivebar restarts part way. The import says which. Continue to Google to try again.