Seamless Google Account Access Setup

Overview

During the January 2026 access setup meeting, Asymmetric gained full access to Seamless's Google Analytics, Google Ads, and Search Console accounts. The process required navigating Google's 2FA authentication before adding Asymmetric as a permanent user — eliminating the need for future 2FA involvement from the client.

This article documents the workflow used and the resulting access state, as a reference for similar client onboarding situations.

Related client: ^[1]

Access State After Meeting

Access Workflow

Step 1 — Identify the Google Account

The Google properties (Analytics, Ads, Search Console) were tied to the client's primary Google account, not a dedicated marketing email. The marketing@sbswi.com address did not have a Google account attached.

Lesson: Always confirm which Google account actually owns the properties before attempting login — it may not be the obvious marketing address.

Step 2 — Authenticate via 2FA (Phone Prompt Method)

Google's 2FA for this account used phone prompts rather than SMS codes. The workflow:

1. Initiate login from Asymmetric's side
2. Google sends a numbered prompt to the client's registered phone (e.g., "Is this you trying to sign in? Tap 7")
3. Client confirms on their phone; Asymmetric completes login

This required the client (Brandon Aman) to be available and reachable during the session. He was called in advance to keep his phone accessible.

Note: The prompt appears as a push notification, not a text message — clients may not recognize it if they're not expecting it. Brief them beforehand.

Step 3 — Add Asymmetric as a User on Each Property

Once authenticated, Sebastian Gant added Asymmetric's email (sebastian.gant@asymmetric.pro) as a user on each Google property individually:

• Google Analytics — added via Analytics admin panel
• Google Ads — added via Ads account access settings
• Search Console — added as a user; ownership verification required inserting a verification token into SiteGround (done in the same session)

After this step, Asymmetric can log in directly to all three properties without requiring client 2FA.

Step 4 — Credential Documentation

A master credentials document was identified as a next step. All new logins and access details should be consolidated and shared with the client.

Action item (open): Create and share master credentials document — assigned to Asymmetric.

SiteGround Access (Related)

SiteGround access was resolved in the same session via password recovery to the chris.sbsw email. A new password was set and Asymmetric was added as a collaborator.

Note: Seamless's WordPress site is being migrated from SiteGround to Asymmetric's hosting environment. SiteGround may remain relevant only if it continues to hold DNS records — pending confirmation from Mark on whether DNS moves to Cloudflare. See ^[1] for infrastructure context.

Generalizable Pattern

This workflow applies broadly to any client where Google properties are owned by a personal or primary Google account with 2FA enabled:

1. Confirm the owning account — don't assume it's the marketing email
2. Pre-brief the client on the phone prompt — they need to be available and expecting it
3. Add agency as a user on each property separately — Analytics, Ads, and Search Console are independent
4. Verify Search Console ownership via DNS or hosting provider if not already done
5. Document all credentials in a shared master doc immediately after the session

Related

• ^[1]
• ^[2]
• ^[3]