Understanding Authentication in TagAssistant.ai
Why you might see different email addresses and how your login and Google Analytics connections work together

Hi, I'm Tessa! π
Your Tag Service Assistant
Great question! It can be confusing to see different email addresses in different places. Let me explain how authentication works in TagAssistant - it's actually designed this way to give you more flexibility!
Quick Tips
- β’Your TagAssistant login and Google Analytics connection are separate
- β’This lets you log in with one email and connect GA with another
- β’Both systems work together seamlessly behind the scenes
The Important Thing to Know
TagAssistant uses two separate authentication systems:
Your TagAssistant Account
This is the email you use to log into TagAssistant.ai. It controls your account, scans, and settings.
Example: alice@company.com
Your Google Analytics Access
This is the Google account you use to connect Google Analytics. It must have access to your GA4 property.
Example: analytics@company.com
These Can Be Different!
How It Works
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β HOW AUTHENTICATION WORKS IN TAGASSISTANT β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ββββββββββββββββββββββββ ββββββββββββββββββββββ β Your Login β β GA Connection β β (TagAssistant) β β (Google OAuth) β ββββββββββββββββββββββββ€ ββββββββββββββββββββββ€ β Email: β β Email: β β alice@company.com β β analytics@co.com β β β β β β Controls: ββββββlinkedββββββΊβ Gives Access To: β β β’ Login to app β behind the β β’ GA4 data β β β’ Run scans β scenes β β’ Property metrics β β β’ View results β β β’ Analytics API β β β’ Account settings β β β ββββββββββββββββββββββββ ββββββββββββββββββββββ β β β β You choose You choose this when this when you sign up you click "Connect Google Analytics"
It's All Connected
Why Two Separate Systems?
Having separate authentication for your TagAssistant account and Google Analytics connection gives you flexibility and solves common real-world scenarios:
Personal vs. Work Accounts
Scenario: You use your work email for TagAssistant but your personal Google account has the GA access.
Login: work@company.com
GA Access: yourname@gmail.com
Shared Analytics Accounts
Scenario: Your team shares a central GA account for analytics access.
Login: alice@company.com
GA Access: analytics@company.com
Login: bob@company.com
GA Access: analytics@company.com (same)
Client Work
Scenario: You're a consultant managing analytics for clients.
Login: consultant@agency.com
GA Access: client@business.com
Security & Permissions
Scenario: Different permission levels for different services.
Your account logs into TagAssistant, but GA access is controlled by whoever owns the Analytics property.
Where You'll See Each Email Address
Your TagAssistant Login Email
You'll see this email in:
- βΈThe top-right corner of TagAssistant (user menu)
- βΈYour account settings page
- βΈEmail notifications from TagAssistant
- βΈThe login screen when you sign in
Your Google Analytics Connection Email
You'll see this email in:
- βΈThe "Google Analytics Overview" card in your scan results
- βΈThe GA connection status indicator
- βΈWhen you hover over the "Connected to GA4" badge
- βΈGoogle's OAuth consent screen (during connection)
Quick Check
Common Questions
I logged in with one email but see a different email in my GA connection. Is this a problem?
No, this is completely normal and expected! The two emails can (and often should) be different:
- Login email: The account you use to access TagAssistant
- GA email: The Google account that has access to your Analytics property
As long as you can see your GA4 data in TagAssistant, everything is working correctly!
Can I connect multiple Google accounts to the same domain?
Currently, each TagAssistant user can connect one Google Analytics account per domain. However:
- Multiple users can each connect their own Google account to the same domain
- You can switch accounts by disconnecting and reconnecting with a different Google account
- Different team members can have different GA accounts connected
Example: Alice and Bob both have TagAssistant accounts. Alice connects company-analytics@business.com to the domain, while Bob connects his personal GA account bob@gmail.com to the same domain. Both work fine!
What does "verified user" mean?
When you connect your Google Analytics account, TagAssistant verifies that:
- β Your Google account exists and is valid
- β You have permission to access the GA4 property you selected
- β The OAuth connection is working correctly
Once verified, you'll see a "β Verified" badge or similar indicator showing that your GA connection is active and working. This verification happens automatically during the OAuth connection process.
How do I change which Google account is connected?
To switch to a different Google account for GA access:
- Find the "Google Analytics Overview" card in your scan results
- Click "Disconnect" or "Revoke Access"
- Click "Connect Google Analytics" again
- When Google's OAuth screen appears, make sure you're logged into the correct Google account
- Grant permission
Pro Tip: If Google doesn't show you an account picker, it might auto-select your currently logged-in account. Use an incognito window or log out of other Google accounts first.
Can I use the same Google account for both login and GA?
Yes, absolutely! If you want to use the same Google account for everything, that works perfectly:
- Log into TagAssistant with yourname@gmail.com
- Connect Google Analytics with the same yourname@gmail.com
In this case, you'll see the same email address everywhere - which might actually be simpler for personal or small business use!
What happens if I change my Google account password?
Your TagAssistant login is separate from your Google account password.
If you change your TagAssistant login password:
- Your TagAssistant login credentials update
- Your GA connection is NOT affected
If you change your Google account password (the one connected to GA):
- Your GA connection continues to work (uses OAuth tokens, not password)
- You DON'T need to reconnect in TagAssistant
- Your TagAssistant login is NOT affected
OAuth uses tokens, not passwords, so password changes don't break the connection!
Security & Privacy
How Your Data is Protected
Separate Authentication Systems
Your TagAssistant login and Google Analytics access are completely independent. Even if someone got access to one, they couldn't access the other.
OAuth 2.0 Security
We never see or store your Google password. Google's secure OAuth protocol handles authentication, and you can revoke access anytime.
Read-Only GA Access
The Google account you connect only gets read-only access to view Analytics data. TagAssistant cannot modify, delete, or change anything in your GA4 property.
Encrypted Token Storage
All authentication tokens are encrypted at rest using Google Cloud's industry-standard encryption. Your data is always protected.
Full Control
You can disconnect your Google Analytics at any time from TagAssistant settings or from your Google Account permissions.
Now You Know!
Understanding how authentication works in TagAssistant helps you make the most of the platform. If you have more questions, don't hesitate to reach out to support!