Connect Google Analytics 4 (GA4) to your Atoms project to track website traffic and understand how users interact with your published site.

This guide walks you through the full setup process: opening the GA4 connection, authorizing the correct Google account, selecting the property for your live site, publishing the tracking update, confirming that data is being collected, and preparing the connection for Google Search Console verification.

How the GA4 connection works

A GA4 property is the Google Analytics resource that collects and reports data for a website or app. Atoms uses the Google account you authorize to find the Analytics accounts and properties that account can access. Connect the property used by the published site for your current Atoms project.

There are three parts to the setup:

1. Authorize a Google account. Sign in to the account that can access the correct GA4 property and approve the requested Google permissions.
2. Connect the matching property. Select the Analytics account and GA4 property used by your project’s live website.
3. Add the tracking setup, publish, and check reporting. Wait for Atoms to add the tracking configuration, review and publish the updated site, then confirm that the correct property is connected and receiving data.

The GA4 connection is separate from Sarah’s SEO content workflow. Sarah can plan and generate SEO pages without GA4. The connection is used for Analytics reporting.

A GA4 connection authorized by the user can also support automatic site verification when you later connect Google Search Console, if the connection meets Google’s requirements.

Before you start

Before connecting Google Analytics 4 (GA4), make sure that:

• You are the project owner. Other collaborators may be able to view the project, but only the owner can manage its GA4 connection.
• You have a Google account with access to the GA4 property used by your website.
• You know which GA4 property belongs to the published site. If several properties have similar names, check the website or web data stream in Google Analytics first.
• Your website has been generated and is published or ready to publish. If Marketing → Analytics tells you to start building the site, finish generating it before continuing.
• Your browser allows Google authorization pop-ups from Atoms.
• Any current Sarah or Alex task has finished before you change the Marketing connection.

You can connect GA4 before your custom domain is live. However, your published site must send data to the connected property before Analytics reports can appear.

If you plan to use GA4 to help verify your site in Google Search Console, use the same Google account for both connections. That account must also have edit access to the GA4 property.

If you cannot access the property, ask its Google Analytics administrator to give you the required access. See Google’s Analytics user-access guide.

If your Google account does not yet have an Analytics account, property, or web data stream, Atoms may guide you through creating one during setup. You can also create these directly in Google Analytics using Google’s website Analytics setup guide.

Google Analytics permission: Use a Google account that can access the Analytics account and GA4 property for this site. Selecting an existing property or web data stream requires access to that resource. Creating an Analytics account, GA4 property, or web data stream in the setup requires Editor permission (or equivalent) at the relevant Analytics level. If a resource is missing or you do not have the required permission, ask an Analytics administrator to grant access or create the resource in Google Analytics first, then return to Atoms and select Refresh.

Never paste Google passwords, verification codes, access tokens, or other credentials into Chat.

Connect Google Analytics 4

Open the GA4 connector

1. Open the Atoms project whose published website you want to measure.
2. Select Marketing in the project toolbar.
3. Open Analytics. If you start from Overview, you can also find the Analytics card under Marketing and select Set up Analytics.
4. Select Authorize GA4. This authorizes the Google account; you will connect the property in a later step.

Authorize Google Analytics 4 from Marketing

Authorize the Google account

1. In the Google authorization window, sign in to the Google account that can access the GA4 property for this site.
2. Check that the correct Google account is selected.
3. Review the access requested by Atoms. Continue only if you agree.
4. Return to Atoms and wait for the authorization step to finish.

If the browser blocks the authorization window, allow pop-ups for Atoms and try again. If Atoms offers Open authorization page, use it to continue in a new tab.

Connect the property for the live site

After you authorize your Google account, Atoms shows the Google Analytics accounts and properties you can access. What you see next may vary depending on how many Analytics resources are linked to your account.

1. If Atoms asks you to choose an Analytics account, select the one that contains the property for your website.
2. Select the GA4 property used by your published site. If you are unsure which one to choose, check the property in Google Analytics first.
3. If a web data stream appears, confirm that it uses the correct live website address.
4. Select Connect property.
5. Keep the page open until Atoms confirms that the connection is complete.

If part of the Analytics setup is missing:

• No Analytics account: If available, select Let Atoms create it for you fast, complete the Google setup, then return to Atoms and select Refresh.
• No GA4 property: Select the correct Analytics account, then choose Create property in Atoms and wait for the new property to appear.
• No web data stream: Select the property and choose Quick Create under Create web stream, or create one manually in Google Analytics Admin.

If an account, property, or data stream that should already exist does not appear, check that you are using the correct Google account and have access to it. If it was only recently created or shared with you, wait briefly and select Refresh.

Connect the GA4 property used by the live site

Finish the tracking update and publish

Connecting the Google resource does not by itself make the published website start collecting data. After Atoms confirms the property connection, it starts a project task to add the Analytics tracking configuration to the website.

1. Wait for the tracking task to finish. Avoid starting another build or Marketing task while the update is running.
2. Review the completed change and preview the website. Confirm that the site still loads and behaves as expected.
3. Publish the updated project. If the site was already live, make sure the newly updated version is the version now published.
4. Open the published homepage in a new tab and use the site normally to generate a test visit.
5. Return to Marketing → Analytics to check the connection and, after Google has processed the visit, the reporting state.

Expected result: Atoms shows the intended property as connected, the tracking update is present in the published version, and the live site begins sending new activity to that property. Connecting GA4 does not create historical data for activity that occurred before collection began.

Check that the connection worked

1. Return to Marketing → Analytics.
2. Confirm that the Google Analytics 4 setup no longer shows the initial connection prompt.
3. Check that the connected account or property matches the live site.
4. If the Analytics reporting area is available, open it and choose a recent date range.
5. If the site is new, visit the published site and return later to check for processed data.

An empty report does not necessarily mean that authorization failed. Treat the connected-property state and the reporting state as separate checkpoints. Confirm that the tracking task finished, the updated version is published, and the same property is receiving events from the live website. Google notes that many standard GA4 reports can take 24–48 hours to populate after collection begins; use Google Analytics Realtime when you need an earlier collection check. See Google’s data-collection verification guide.

Review Analytics reporting after GA4 data is available

Recover from a failed GA4 connection

Use the state that failed to choose the next safe action. A failed authorization or resource list usually needs a fresh authorization window, the correct Google identity, or a refresh after access was granted. A connected property with no reporting data needs a tracking-task and publish check before you retry the connection.

• Authorization or account loading fails: Allow pop-ups, reopen Open authorization page if it is offered, confirm the intended Google identity, and retry once.
• An account, property, or stream is missing: Confirm the required access and Editor permission for creation, then select Refresh after a recently created or shared resource becomes available.
• The property connects but tracking or reporting fails: Wait for the tracking task to finish, preview and publish the latest version, confirm that the connected property matches the live site, and use Google Analytics Realtime or the documented reporting delay before retrying.

If the same stage still fails after one retry, contact Atoms Support or your workspace administrator. Include the project name, connected property name if shown, failed stage, visible status or error text, approximate time, and a redacted screenshot. Never include passwords, verification codes, access tokens, OAuth codes, or other credentials.

Use GA4 with Google Search Console

Google Analytics based Search Console verification is conditional. In Atoms, Auto Verify via Google Analytics requires an eligible user-authorized GA4 connection. An Atoms-created managed GA4 setup cannot use this automatic-verification action. GA4 is not required if you use one of Google’s manual verification methods.

To set up and verify your site in Search Console, see Connect Google Search Console for the full steps and requirements.

Google’s Analytics verification method also requires a public homepage containing the supported Analytics tag and applies to a URL-prefix Search Console property, not a Domain property. If automatic verification is unavailable because the GA4 setup is Atoms-managed or any Google requirement is not met, continue with Verify manually in Google Search Console. See Google’s site-ownership verification requirements.

For the related content and reporting workflow, see SEO Agent.