Skip to main content
Google Analytics (GA4) is Visen.io’s source for traffic data. Connecting it alongside Google Search Console gives you a complete picture — rankings and organic visibility on one side, user behavior and traffic quality on the other.

Prerequisites

Before connecting, make sure you have:
  • A Google Analytics 4 (GA4) property set up and collecting data
  • Editor or Administrator access to the GA4 property in Google Analytics
Visen.io supports GA4 only. Universal Analytics (UA) properties are not supported. If you haven’t migrated to GA4 yet, do that in Google Analytics before connecting to Visen.io.

Connect Google Analytics

1

Open Integrations

In your Visen.io workspace, navigate to Settings → Integrations.
2

Select Google Analytics

Find the Google Analytics card and click Connect.
3

Authorize with Google

A Google OAuth window will open. Sign in with the Google account that has access to your GA4 property, then grant the requested permissions.
4

Choose your property

After authorization, Visen.io displays the GA4 properties available to your account. Select the property that corresponds to the website you want to track.
5

Save the connection

Click Save. Visen.io confirms the connection and begins importing your analytics data.
Integrations are per-workspace. If you manage multiple websites, connect each site’s GA4 property within the corresponding Visen.io workspace.

What data flows in

Once connected, the following GA4 data is available in your Visen.io dashboard:
SignalDescription
SessionsTotal sessions on your site, segmented by source and channel
UsersNew and returning users over any time range
Traffic sourcesBreakdown of organic, direct, referral, and paid traffic
Page performancePageviews, engagement rate, and time on page per URL

GSC + GA together: the full picture

When both Google Search Console and Google Analytics are connected to the same site, Visen.io combines the two data sources in your dashboard:
  • Rankings → Traffic: See which keywords drive actual sessions, not just impressions.
  • Pages: Compare a page’s average position in search against its engagement metrics.
  • Trends: Overlay organic click data from GSC with session data from GA to validate SEO impact.
Connect both integrations for the same property to unlock the combined view. You can connect them in any order — Visen.io merges the data automatically once both are active.

Data freshness

Real-time indicators appear in your dashboard as soon as the connection is saved. Full historical trends populate within 24–72 hours. GA4 data from Google may have its own processing delay of up to 48 hours on Google’s side, which can affect how quickly recent sessions appear.

Troubleshooting

Visen.io requires at least Editor access to your GA4 property to read data. Viewer-level access is not sufficient.To check or update your access level:
  1. Open Google Analytics and go to Admin.
  2. Under the property, select Property access management.
  3. Confirm your Google account has Editor or Administrator role.
Ask your GA4 administrator to update your role if needed, then reconnect in Visen.io.
Only properties where your authorized Google account has Editor or Administrator access appear. If your property is missing:
  • Confirm you used the correct Google account during the OAuth flow.
  • Verify your role in GA4 under Admin → Property access management.
  • If access was recently granted, wait a few minutes and try reconnecting.
If your authorization expires or is revoked:
  1. Go to Settings → Integrations.
  2. Click Reconnect next to Google Analytics.
  3. Complete the Google OAuth flow again.
Your property selection and historical data are preserved during re-authorization.
Confirm the integration shows a Connected status in Settings → Integrations. If it does but data is still missing:
  • Allow up to 72 hours for the initial sync to complete.
  • Verify that your GA4 property is actively receiving data by checking it directly in Google Analytics.
  • Make sure you selected the correct GA4 property (not a UA property or a test stream with no traffic).
If the issue persists after 72 hours, try disconnecting and reconnecting the integration.
Last modified on April 6, 2026