Most connection problems come down to one thing: the reporting email isn't (or is no longer) a user on the right Google property. This guide covers the common cases and how to fix each one. If you haven't connected a client yet, start with Connect Search Console and GA4.
The property isn't in the list
You open the client's settings, click Reload properties, and their site or GA4 property isn't there. Check these, in order:
- Has the client done it yet? Confirm with your client that they added the reporting email. Until they do, nothing shows up.
- Is it the right email? Copy it again from Google access and compare it with what the client added. A single wrong letter means Google invites an address that isn't yours. It ends in
.iam.gserviceaccount.com. - Is it on the right property? Clients often have more than one Search Console property (for example a domain property and a
https://www.one) or more than one GA4 property. Ask them to check the one for this website. In Search Console the users are under Settings → Users and permissions; in GA4 under Admin → Property access management. - Was it added with a permission? Search Console needs at least Restricted, and GA4 at least Viewer. Both are enough: the reporting email never needs more.
- Give it a minute. New access can take a minute to show up. Then click Reload properties again.
Only Search Console owners and GA4 administrators can add users. If your client can't find the buttons, someone else in their business may need to do it.
An error under Reload properties
If Google refuses the request, the line next to Reload properties turns red and shows Google's message for Search Console or GA4. It usually says what's wrong. If it looks temporary, reload again in a few minutes.
A property shows "no access from this account"
When a client was connected before but the reporting email can no longer see that property, the list shows it with "(no access from this account)". The client (or someone on their side) removed the reporting email. Ask them to add it again with the same steps, then click Reload properties.
"Can't be loaded" errors on the report
When a connected source fails, your own view of the report shows a red message at the top, such as Search Console or Google Analytics 4 followed by Google's error. These messages are for your team only, and the report says so.
Your clients never see errors. Shared reports and the client's live link simply leave out a section that couldn't load. The rest of the report still works.
- Check access. Make sure the reporting email is still a user on the property (see above).
- Refresh the data. Click Refresh in the report toolbar to fetch fresh data from Google.
- Try again later. Some Google errors are temporary. If the report says no data could be loaded, try again in a few minutes.
The daily check also catches this: you get an alert email when a source can't be read anymore. See Traffic alerts.
Only some sources are connected
A client with just Search Console, or just GA4, still gets a full report for what's connected. Your view shows a note listing the sources that aren't connected, with a link to connect more. Only you see this note.
GA4 numbers have no comparison
If the client's GA4 tracking started recently, the comparison period may have no Google Analytics data at all. Instead of marking every row as new, the report shows the current period only, with a note: "There's no Google Analytics data for the comparison period yet". When ReportFalcon knows the date, it also says when the website's data starts. Pick a later comparison period, or wait until there's more history. See Change dates and comparisons.
How long does it take?
Adding the email takes your client about two minutes. Once it's added, the property usually shows up within a minute when you click Reload properties. Dashboard trends fill in when you save the client and update once a day after that.