Your client grants everything you need in one Google consent screen. No shared passwords, no "which account was that again," no back-and-forth.
Google doesn't have one "give my agency access" button. Access to Ads, Analytics, Tag Manager, Search Console and Business Profile is granted separately, in different places, each with its own permission model — and most clients don't know where any of it lives. eGiiG collapses all of it into a single consent.
Google works through one OAuth consent that can cover several products at once. You choose which products to request; the client sees them on Google's own screen and approves.
Request every Google product in a single consent, or narrow it to exactly what you need, Analytics only, or Ads and Analytics and nothing else. Your client sees only the products you ask for, can narrow further at the consent screen, but never has to grant more.
This is a real differentiator. You can request all Google products in one screen, or narrow it to just what you need — e.g. Analytics only, which asks for the four Analytics scopes and nothing else. The client can narrow further at consent but never widen. That means the consent screen matches the work, and the client isn't scared off by a wall of unrelated permissions.
The client authorises access on the platform’s own screen. No credentials are ever shared with you or eGiiG.
You request exactly the access the work requires. The client can narrow it, but never has to grant more.
Every connection lives in the client’s portal, where they can review or revoke access whenever they choose.
Where Google's API lets one user set another user's role, eGiiG shows an access-level dropdown at connect time — full transparency for the client:
Search Console, Business Profile and Merchant Center don't offer a level dropdown — Google's API can't set another user's level on those, so access is granted at the default level (this is a Google limitation, worth a one-line footnote so it doesn't look like a gap in your product).
eGiiG runs Google Ads off each connected account's own access, so an MCC is not a hard requirement to onboard a client. If an agency has no manager account yet, eGiiG detects that and guides them to create one (Google doesn't expose an API to create a top-level MCC automatically) — but they can start onboarding clients immediately either way.
Choose which Google products to request in the Flow builder.
Send the branded onboarding link.
Client approves on Google's consent screen → each product lands in the right section; portal shows what they granted.
Start free, no card. Send one branded link and get the Google access you need.