Help · Connect your sources
Google Analytics and Search Console
Your own read-only Google service account: paste its key on Connections, then add it as a Viewer in GA4 and a Restricted user in Search Console.
About 10 minutes.
Your dashboard reads Google Analytics and Search Console through a Google service account: a robot account with its own address (ending in .iam.gserviceaccount.com) that can only see what you add it to. It's yours, in your own Google Cloud project, so no one else's dashboard can use it. Remove it from your properties, or delete its key, to cut access at any time.
Create the service account (once, about 5 minutes)
- Open console.cloud.google.com and create a project (any name, e.g. RevWarn). It's free.
- In APIs & Services → Library, enable these three: Google Analytics Data API, Google Analytics Admin API, Google Search Console API.
- In IAM & Admin → Service accounts, select Create service account. Give it a name; skip the optional roles; select Done.
- Open it → Keys → Add key → Create new key → JSON. A file downloads.
- Open the file in a text editor, copy everything, and paste it on your dashboard's Connections page under Google. Its address then shows at the top of that page. Delete the file afterwards.
Google Analytics 4 (one step for all your properties)
- In Google Analytics, select Admin (bottom left).
- At the account level, open Account access management.
- Select + (top right) → Add users.
- Paste the service account's address (shown on your Connections page), choose the Viewer role, and untick "Notify new users by email" (it can't read email).
- Select Add. Added at the account level, it covers every property in that account.
Search Console (each property)
- In Search Console, pick the property.
- Open Settings → Users and permissions → Add user.
- Paste the same address, choose Restricted, and select Add.
- Repeat for each site (a Domain property covers all its addresses).
Count a site's traffic with Google Analytics instead
Already use GA4 and don't want another snippet? On the Sites page, open the site's Edit and set Traffic counted by to Google Analytics. Its tile, the morning email and the low-traffic warning then use GA4 sessions, and earnings per page use GA4 page views. Its property is found by the site's address; if you have several streams for one address, type the property ID (Admin → Property details) instead.
GA4 takes up to a day to finish counting, so its warnings judge the day before yesterday rather than yesterday. Cloudflare Web Analytics is hourly and stays the quicker choice.
When it shows up
The search collector runs at 4am Pacific and loads the last weeks of data. Sites it can't read yet are listed on the Setup page, under Google Analytics and Search Console.
If you see…
| Message | What it means | What to do |
|---|---|---|
| search: … can't read … | The service account hasn't been added to that property, or was added to a different one. | Add it as above to the property for that exact site address (http vs https, www vs not matter for URL-prefix properties). |
| GA4 sessions differ from Cloudflare visits | They count differently (cookies, consent banners, ad blockers). | Normal; use each for trends. |
From the service's own documentation: Google Analytics Help: Add, edit and delete users · Search Console Help: Manage users and permissions. Menus move; if a step doesn't match your screen, tell us.