Skip to main content
Connecting Google Analytics 4 lets Pharos pull your existing session and conversion data and break it down by AI referral source. Instead of digging through GA4’s acquisition reports yourself, you get a focused view: how many sessions came from ChatGPT, Perplexity, Claude, Gemini, and others — and whether those sessions converted. This makes it straightforward to connect AI visibility improvements you make in Pharos to downstream traffic and revenue impact.

​
Before you connect

You need Edit access (or higher) on the GA4 property you want to connect. Read-only access is not sufficient because Pharos stores a refresh token scoped to your Google account — if your access to the property is later removed, the connection will stop refreshing data.

​
Connect GA4

1

Open Integrations settings

In the sidebar, navigate to Settings, then click the Integrations tab.
2

Find Google Analytics 4

Under the Measure & Attribute section, locate the Google Analytics 4 card.
3

Click Connect

Click the Connect button on the GA4 card. A Google OAuth popup opens.
4

Sign in and grant access

Sign in to the Google account that has access to your GA4 property, then click Allow to grant Pharos read access to your Analytics data.
5

Select your GA4 property

After the popup closes, a property selector dialog appears. Choose the GA4 property that corresponds to your brand’s website and click Select.
If your browser blocks the OAuth popup, allow popups for Pharos and click Connect again. Do not navigate away from the Settings page during the OAuth flow — doing so will interrupt the connection and you will need to start again.
Once connected, the GA4 card shows the name of the selected property and a green status indicator. Pharos begins syncing data in the background.

​
Metrics Pharos pulls from GA4

Pharos fetches session-level data from your GA4 property and organizes it by traffic source. You can view up to 90 days of history.
MetricDescription
SessionsTotal sessions attributed to each referral source
UsersUnique users per source
ConversionsGoal completions and purchase events
RevenueTotal revenue from e-commerce and purchase events
Conversion rateConversions divided by sessions
Pharos maps GA4 referral domains to display-friendly platform names automatically:
GA4 source domainDisplayed as
chatgpt.com, chat.openai.comChatGPT
perplexity.aiPerplexity
claude.aiClaude
gemini.google.comGemini
copilot.microsoft.comCopilot
you.comYou.com
phind.comPhind
poe.comPoe
Sources that do not match a known AI platform are displayed using their raw domain name. In addition to source breakdowns, Pharos also surfaces:
  • Daily trend — sessions, users, conversions, and revenue charted over time
  • Top landing pages — which pages receive the most AI-referred sessions and generate the most conversions
  • Per-source per-page breakdown — which AI platform sends traffic to which pages

​
Change your selected property

If you connected the wrong property or need to switch to a different one:
1

Open the GA4 connection panel

Go to Settings → Integrations and click the Google Analytics 4 card. Because it is already connected, clicking the card opens the connection details panel.
2

Click Change property

Click Change property. Pharos fetches your available GA4 properties and opens the selector again.
3

Select the correct property

Choose the new property and click Select. Pharos immediately begins pulling data for the new property.

​
Disconnect GA4

Disconnecting removes Pharos’s access to your GA4 data. Historical data that Pharos has already synced is retained, but no new data will be pulled.
1

Open the connection panel

Go to Settings → Integrations and click the Google Analytics 4 card.
2

Click Disconnect

Click Disconnect in the connection panel and confirm the action.
Disconnecting GA4 immediately stops data sync. If you want to pause syncing temporarily, disconnecting and reconnecting later is the only option — there is no pause state.
After disconnecting, you can reconnect at any time by clicking Connect on the GA4 card and completing the OAuth flow again.