---
title: How do I connect Google (Search Console, GA4, Tag Manager, Google Ads)?
question: connect google
area: integrations
order: 9
surface: desktop
audience: beginner
keywords: [google, connect google, search console, analytics, ga4, google analytics, tag manager, gtm, google ads, adwords, oauth, developer token, api center, client id, client secret, analytics tracking, rankings, conversion tracking, ppc]
related: [integrations-overview, connect-meta-ads, connect-stripe-and-xero]
updated: 2026-07-21
---

# How do I connect Google (Search Console, GA4, Tag Manager, Google Ads)?

Open **Integrations** in settings, find the **Google** card under **Analytics + tracking**, and click **Connect with Google**. You connect your Google account once, and that single connection covers **Search Console**, **Analytics (GA4)**, **Tag Manager**, and **Google Ads**. codus signs you in through your browser. Once connected, agents can read your search rankings and traffic, manage tags and conversion tracking, and pull ad performance across your Google marketing stack.

## Before you start

- You need the Google account that owns your Search Console, Analytics, and Tag Manager.
- codus signs you in with Google's secure loopback flow. There is no redirect URI to register: Google handles that automatically for desktop apps.
- **Google Ads is a separate extra step.** Search Console, Analytics, and Tag Manager work as soon as you sign in. Google Ads also needs a developer token, covered near the end of this page.

## Steps: connect your Google account

1. Open the gear (**⚙**), click **See all settings →**, then click **Integrations**, and find the **Google** card.
2. Click **Connect with Google**. If your build ships codus's own verified Google app, this is one click and there is nothing to create or paste.
3. Your browser opens Google sign-in. Choose the account that owns your Search Console, Analytics, and Tag Manager, and click **Allow**.
4. Come back to codus. The card flips to **Connected** with your email.

### If the card asks for a Client ID and secret instead

Some builds ask you to bring your own Google Cloud client (and you can always choose this under **Advanced: use your own Google Cloud client**). It is a one-time setup that keeps you on your own API quota:

1. On the card, click **Open the Google Cloud console** to open console.cloud.google.com, and create or pick a project.
2. Under **APIs & Services → Library**, click **Enable** on each API you want: **Tag Manager API**, **Google Search Console API**, **Google Analytics Data API**, and (for ads) **Google Ads API**.
3. Open the **OAuth consent screen**, set User type to **External**, fill in the app name and your email, and save. Under **Test users**, add your own Google email. No publishing or Google review is needed for your own use.
4. Go to **Credentials → Create credentials → OAuth client ID**, set application type to **Desktop app**, name it **codus**, and create it. A dialog shows your **Client ID** and **Client secret**.
5. Paste both into the boxes on the card, then click **Connect with Google**. You do not need to add a redirect URI.

## Steps: add Google Ads (developer token)

Google Ads needs a developer token, which is separate from signing in. Tag Manager, Search Console, and Analytics work without it.

1. Connect your Google account first (above). Once connected, the card shows a Google Ads section with a note that a developer token is needed.
2. In your **Google Ads** account, go to **Tools → API Center** and get a developer token. Apply for **Basic access** so the token can query your real (non-test) account.
3. Back in codus, paste the developer token into the **Google Ads developer token** box on the card.
4. If you use a manager account, put its **Manager (MCC) customer id** in the optional box below. Otherwise leave it blank.
5. Click **Save Google Ads token**. The button reads **Saved** when it is stored.

## How do I know it worked?

The card shows a green **Connected** label with your Google email. After you save a Google Ads token, the Google Ads note reads "A token is saved." From then on, an agent can pull Search Console, Analytics, Tag Manager, and (with the token) Google Ads data when you ask.

## Common problems

- **My ads data will not load, but everything else works.** Google Ads needs its own developer token with **Basic access**. A token stuck on test access cannot read a real account. Apply for Basic access in **Tools → API Center**, then save the token again.
- **The consent screen warned the app is unverified.** For your own account you add yourself as a **Test user** on the OAuth consent screen, and that is enough. No Google review is required.
- **I picked the wrong Google account.** Click **Disconnect** and confirm, then **Connect with Google** again and choose the right account.
- **The browser opened but codus did not update.** Finish the approval in the browser and bring codus to the front. The card re-checks when the window regains focus.