Analytics brings your Google Analytics 4 (GA4) data into Atoms, so you can check how a published site is performing without leaving your project.

This guide covers reading your reports, understanding why a report is empty, fixing a missing tracking code, and disconnecting a property. To set the connection up in the first place, see Connect Google Analytics 4.

How Analytics works

Analytics is the first tab in the Marketing module, alongside Performance and Operations under SEO, and Google Ads under Ads. It is the tab Atoms opens by default.

Analytics reads from the GA4 property connected to your project. It does not measure anything itself and it does not change your site, so anything GA4 is not tracking will not appear here. It also cannot show activity from before collection began.

Before you start

Before Analytics can show you anything, make sure that:

• Your workspace is on the Pro plan or higher. Analytics reporting is not available on the Free plan. See Plans and credits.
• Your project has been generated. Until it has, Analytics shows Site Analytics and asks you to start building your site.
• Your site is published, and the published version is the one containing the tracking update. GA4 only collects from a live site.
• A GA4 property is connected to this project. See Connect Google Analytics 4.
• Enough time has passed. Google can take 24–48 hours to process data into standard reports.

Important: Connecting GA4 and viewing reports are gated separately. On the Free plan you can authorize Google and connect a property normally, and your site collects data into that property as usual, but Analytics shows an upgrade message instead of your reports. Nothing is lost while you decide: the data is in your own GA4 property, and you can read it in Google Analytics at any time.

Viewing Analytics is not restricted by role, any project collaborator on an eligible plan can read the reports. Only the workspace owner can connect or disconnect the property.

Marketing is not available for mobile app projects, and Analytics data is not available in shared view.

Open Analytics

1. Open the project whose published site you want to measure.
2. Select Marketing in the project toolbar.
3. Open Analytics.

If no property is connected yet, Atoms shows the connection prompt instead of your reports. See Connect Google Analytics 4.

Expected result: Analytics shows report blocks for the property connected to this project.

Read your reports

Use the date selector to switch between Last 7 days and Last 30 days.

These are the possible date ranges, and Atoms defaults to 7. There is no custom range and no period-over-period comparison, so read these reports for direction rather than precise change. For custom ranges and comparisons, open the property in Google Analytics.

Review Analytics reporting after GA4 data is available

Analytics shows six blocks:

• Active Users & Sessions — a bar chart of Users and Sessions across your selected range.
• Top Referrers — a table of Referrer and Active Users, showing where your traffic comes from.
• Top Regions — active users by country.
• Top Browsers — active users by browser.
• Device Categories — active users by device type.
• Top Pages — a table of Page Title, URL, Views, Active Users, Events, and Bounce Rate.

When reports are empty

Atoms shows No data available in each block when the connection is working but GA4 has returned nothing. An empty report does not mean the connection failed. Treat the connected property and the reporting state as separate checkpoints.

Two things are quick to rule out first:

• You see an upgrade message rather than empty blocks. That is the plan requirement, not a data problem. See Before you start.
• A status banner is showing. Follow what it says — see Fix a tracking code problem below.

If your property is connected, your site is published, and no banner is showing, the question is no longer whether the setup is right. It is whether GA4 is receiving anything at all.

Collection and processing are different things

Google separates two things that look identical in Atoms:

• Collection — whether hits reach your property. Visible in Google Analytics' Realtime report, usually within minutes.
• Processing — turning those hits into the standard reports Atoms displays. This takes up to 24–48 hours.

Atoms shows processed reports only, so it cannot tell these apart for you. Realtime can.

Check whether data is being collected

1. Open your published site in a new browser tab and visit a couple of pages.
2. In Google Analytics — not Atoms — open the connected property and go to its Realtime report.
3. Look for your own visit in the last 30 minutes.

Read the result

Your visit appears in Realtime. Collection is working, and what you have is a processing delay. Nothing is broken. Standard reports fill in within 24–48 hours of collection starting, so check Atoms again tomorrow.

Your visit does not appear in Realtime. Hits are not reaching the property. Work through these three causes:

• The published version does not carry the tracking code. Publishing after the tracking task finished is what puts it on your live site. If in doubt, publish again and retest.
• You are looking at a different property or data stream from the one your site sends to. Compare the property connected in Atoms against the one you opened in Google Analytics, and check that its data stream points at your live URL.
• Your own visit is being blocked. Ad blockers, privacy extensions, and cookie-consent banners stop GA4 collecting, and they most often stop it for you rather than your visitors. Retest in a browser with no extensions, accepting any consent banner your site shows.

If Realtime stays empty after all three, the tag is not firing on your live site. Use Check Status on the Analytics tab, and see Fix a tracking code problem below.

For Google's own explanation of the difference, see Realtime and processing in GA4.

Note: The 24–48 hour banner in Atoms can be dismissed, and once dismissed it stays hidden in that browser permanently. If you cannot get it back, that is why — it is not a fault.

Fix a tracking code problem

When Atoms cannot confirm the tracking code on your site, a status banner explains what it found and offers up to two buttons. The most common messages are:

Banner	What it means	What to do
Please publish your site to enable analytics tracking	The project is not published	Publish, then return
GA4 tracking code is not found on your site	Atoms cannot find a GA4 tag on your site	Select AI Fix if offered, then publish
GA4 configuration does not match the expected settings	The tag Atoms found is not the one it expects for the connected property	Check which property is connected, and reconnect it if it is not the one you want
Failed to verify GA4 status / Unable to determine GA4 status	The check itself did not complete	Select Check Status to run it again

The two buttons do different things:

• Check Status re-runs the check and reports what is on your site. It changes nothing. It also refreshes whether AI Fix is available, so run it first if you expect AI Fix and cannot see it.
• AI Fix asks your agents to add the tracking configuration for you. It appears only when Atoms has a fix to offer for the problem it found. Because the agents change your project rather than your live site, publish it again afterwards or the fix will not reach visitors.

Expected result: after publishing, Check Status no longer reports a missing or mismatched tag, and new activity reaches the connected property.

If the same problem persists after one retry, contact Atoms Support. Include the project name, the connected property name if shown, the visible status or error text, the approximate time, and a redacted screenshot. Never include passwords, verification codes, access tokens, or other credentials.

Disconnect or reconnect GA4

There are two disconnects, and which one you need depends on what you are changing.

What you want to change	Use
A different GA4 property, same Google account	Disconnect per project
A different Google account	Disconnect account-wide, then authorize again

Change property for one project

In Marketing → Analytics, open the property selector and select Disconnect. This unbinds the property from this project only and leaves your Google authorization in place, so you can select a different property straight away.

There is no confirmation step, so check you are in the right project first.

Change the Google account

Do this when you authorized the wrong Google account, or when the property you need belongs to a different one.

Important: Connectors are a workspace setting, so disconnecting here removes the authorization across every project in the workspace that uses it, not just the current one. Other projects connected through the same Google account will need reconnecting. If you only want to point this project at a different property, use Change the property for one project above instead.

1. Open Settings.
2. Select Connectors under Workspace.
3. Open Google Analytics 4. The Connectors section shows the authorized Google account.
4. Select Disconnect and confirm.
5. Select Connect and sign in with the Google account that can access the property you want.

Expected result: the Connectors section shows the new Google account, and you can connect a property to your project from it.

What disconnecting does not do

Neither disconnect deletes anything from your Google Analytics account, and neither removes the tracking tag from your published site. GA4 keeps collecting; Atoms simply stops displaying it. To stop collection entirely, remove the tag from your site as well.

For the full authorization and property-selection steps, see Connect Google Analytics 4.