# Four products, one sign-in

Google Ads, Analytics, Search Console and Tag Manager on one connector, under your own Google sign-in.

Live · Your own Google sign-in · One connector

## Four products, counted

Each product is its own consent and page; its tools are listed from day one and work once you grant it.

- **[Google Ads](https://adcopilot.cloud/platforms/google-ads)** (Live): Read, audit and change Google Ads from your AI client. It cannot delete, and nothing changes until you allow it. (77 tools, usable once Google Ads is connected)
- **[Google Analytics](https://adcopilot.cloud/platforms/google-analytics)** (Live): Run GA4 reports and create conversion events, custom dimensions and metrics from your AI client. (29 tools, usable once Google Analytics is connected)
- **[Search Console](https://adcopilot.cloud/platforms/search-console)** (Live): Read search performance, inspect a URL, audit which pages are not indexed, notify the Indexing API and submit a sitemap. (8 tools, usable once Search Console is connected)
- **[Tag Manager](https://adcopilot.cloud/platforms/tag-manager)** (Live): Audit a container and stage the fix in Tag Manager. You publish the version yourself, then verify. (18 tools, usable once Tag Manager is connected)
- **All four at once**: One connector, one sign-in, and every product's tools listed from day one; each one runs once you grant its product. Each grant is separate, and each one can be withdrawn on its own. (135 tools on the full tier, whichever products are connected, as of v2.46.25)

## What you actually grant

Stated in the words you would use, because you are being asked to make a decision here.

- **What you are granting**: One Google sign-in, and then a separate consent per product. Granting Google Ads does not grant Analytics, Search Console or Tag Manager.
- **What it can reach**: It runs as you. If you cannot open an account or a property in Google's own interface, the connector cannot reach it either, unless your workspace owner shares a teammate's login that can open it with you, which that teammate has to allow first. In Google Ads that login reads only: a Google Ads change always runs on your own login.
- **Where the grant lives**: In your own Google account, on its permissions page, where you can withdraw it at any moment without asking us first.

Start with Google Ads and add the others when you want them. Each product is its own consent, granted and withdrawn in your own Google account.

## Three short answers

The three things people ask before they connect this one, answered without hedging.

### Do I have to connect all four?

No. Google Ads on its own is a working connector; the other three add what they add. Each is a separate consent in your own Google account, and withdrawing one leaves the rest exactly as they were.

### Is this one Google sign-in or four?

One sign-in, then a consent per product. The connector uses that grant for whichever products you turned on, and it reaches only what your own Google login opens, plus what a teammate's login opens if your workspace owner shares it with you (in Google Ads, for reads only).

### Where does the work actually happen?

In your AI client. It asks our server, our server checks the connector, the tier and the account, then calls Google with your credential and hands the answer back. Our server also writes a ledger entry for the call and caches a Google Ads audit's reads for up to an hour. The privacy policy lists everything it keeps.

## Connect it, then read the ledger yourself.

[Connect Google Ads](https://app.adcopilot.cloud/signup?utm_source=site&utm_medium=cta) · [Every fence](https://adcopilot.cloud/security)

---

This is the markdown copy of https://adcopilot.cloud/platforms/growth-stack. The index of the site's pages is https://adcopilot.cloud/llms.txt.
