Connect Google Analytics 4 to Tatheon and traffic joins revenue on the same board, so conversion rate stops being a number you calculate by hand across two tabs. This guide is for whoever administers the GA4 property. It covers the access Tatheon needs, how to grant it, and what to expect once sessions start arriving.
How this connection works
Tatheon does not ask you to paste an API key or sign in through Google. It uses a service account, which is a Google identity that belongs to Tatheon rather than to a person.
That design has a practical benefit worth knowing. Connections tied to an individual break when that person changes their password, loses admin rights or leaves the business, and they usually break silently. A service account has none of those failure modes. It keeps working until somebody deliberately removes it.
Before you start
You need Administrator access on the GA4 property, not Editor. Only an administrator can add a user to a property, so if the Property access management screen is read only for you, someone else has to complete this step.
Have the property ready. If you run several, pick the one that receives your storefront traffic, which is usually obvious from the realtime report.
Grant access
Open the source wizard and choose Google Analytics 4. The wizard shows the Tatheon service account address. Copy it.
In Google Analytics, open Admin, then Property access management, and add a new user using that address. Grant the Viewer role. Tatheon reads reports and never writes, so Viewer is sufficient and anything higher grants access that is not needed.
Return to the wizard. Tatheon detects the property automatically once the service account has been added, so there is no property identifier to type in and no chance of connecting the wrong one by transcription error.
What happens next
Sessions, landing pages and funnel behaviour begin backfilling, and a nightly sync keeps them current. GA4 imposes its own quota limits on how much can be read at once, so a property with years of history fills in over several nightly runs rather than immediately.
One quirk of GA4 is worth expecting. It does not record a row for a day with no traffic, so a gap in the data is genuinely a day with no sessions rather than a sync that failed. Tatheon accounts for this and does not treat an empty day as missing.
What GA4 is for, and what it is not
GA4 tells you about behaviour: how people arrived, what they looked at, where they left. It is the best source available for that.
It is not a revenue source, and Tatheon does not treat it as one. Revenue comes from Shopify, because the store is the only system that knows what money actually changed hands. If you have compared GA4 revenue against your Shopify payouts you already know they disagree, and the reason is that GA4 counts what it observed in the browser while Shopify counts what it settled. Tatheon takes each source for what it is reliably good at.
Confirm it is working
Compare sessions for a recent closed week against the same week in GA4 itself. They should be close. Small differences come from timezone handling, because Tatheon reports against your business timezone and GA4 reports against whatever the property is configured with. If those two settings differ, check the property timezone before assuming anything is wrong.
Common problems
No data arriving after the service account was added is usually a role problem. Confirm the account was given Viewer at property level rather than at account level, because access granted higher up does not always apply to the property.
Sessions arriving for the wrong site means several properties exist and the service account was added to the one that is not your storefront.
Next
Add Search Console next. It uses the same service account approach and brings organic query performance alongside the sessions GA4 reports.