Getting Started

Platform overview

1. P.1 Google Cloud (GCP) Setup: prepare the GCP project that will host the server-side infrastructure. GCP project selection in the app is deferred until after scanning.
2. P.2 GA4 Setup: confirm Analytics access and prepare the GA4 properties and measurement IDs needed for the setup.
3. P.3 GTM Setup: confirm GTM account access and confirm the web container. A server container can be created later during the setup workflow.
4. P.4 Settings: Google sign-in, API verification, and app configuration.

P.1 Google Cloud (GCP) Setup

This is the platform layer for the server-side part of the implementation. If GCP is new to you, treat this as the infrastructure foundation that the later Cloud Run steps build on.

P.2 GA4 Setup

The setup workflow needs GA4 access to scan your existing setup and create a temporary shadow property for validation.

P.3 GTM Setup

The setup requires a web GTM container. A server container can be created during setup if you don’t have one yet.

P.4 Settings

The app’s Settings page is where you connect Google access and confirm the prerequisites before you start the audit.

1. 1

   Open Settings in the app

   Start in the app’s Settings page. This is where Google access, API checks, and project configuration are managed.

2. 2

   Sign in with Google

   Use the hosted Google sign-in flow in the app. You do not need to create a separate OAuth client or provide a client_secret.json file for GSS.

   What to expect:

   1. Click Sign in with Google in the app.
   2. Use the Google account that has access to the Analytics, GTM, Cloud Run, and GCP resources for this implementation.
   3. Approve the requested scopes so the app can read configuration and perform setup actions later in the workflow.
   4. If the wrong account is connected, disconnect it in Settings and sign in again with the correct one.
3. 3

   Confirm required APIs and account access

   Use Settings to verify that the required Google APIs are enabled and that the connected account can access the Analytics, GTM, Cloud Run, and GCP resources for this implementation.

4. 4

   Select the GCP project when the app prompts for it

   You do not need to bind the project before the first audit. Once you move into the build step, select the prepared GCP project in the app so deployment and validation happen in the right place.