Token Expiration and Authentication
Problem
You see an error message like:
TOKEN EXPIRED or user changed Facebook Password!
Or:
Authentication failed for Platform account
Or your data source shows an "Access Token Expired" status.
This typically means your account's authentication credentials have expired or become invalid.
Why This Happens
Data source authentication tokens can expire for several reasons:
- Password Changed: You changed your account password after authorizing TMR
- Token Expiration: The authorization token naturally expired (some platforms expire tokens after a period of inactivity)
- Account Deactivation: Your account was deactivated or suspended by the platform
- Permission Revocation: You or an administrator revoked TMR's access permissions
- Multi-Account Issue: You're signed into multiple accounts and permissions got confused
- Third-Party Changes: The platform updated security settings that invalidated your token
Affected Platforms
Common platforms that require re-authentication:
- Facebook Ads & Facebook Insights
- Google Ads
- Google Analytics
- Instagram Insights
- LinkedIn Ads
- Twitter/X Ads
- TikTok Ads
Solution: Re-authenticate Your Account
Step 1: Open Data Sources
In Two Minute Reports:
- Click on Data Sources in the left navigation menu
- Find the data source showing the authentication error
Step 2: Edit the Data Source
- Select the data source that gave you the token expiration error
- Click the Edit button (pencil icon)
Step 3: Re-authenticate
- You'll be redirected to the platform's login screen (Facebook, Google Ads, etc.)
- Log in with your account credentials
- Grant permission to Two Minute Reports to access your account
- You'll be redirected back to TMR
Step 4: Verify Connection
- The data source should now show as "Connected" with a green status indicator
- Your report or query should start pulling data again
- If a scheduled refresh was pending, it will now run automatically
Troubleshooting Re-authentication
Problem: Login Screen Loops Back
Solution: This usually means you're using the wrong email account. Ensure you're:
- Using the same email address you used to create the account on that platform
- Checking if you have multiple accounts and logging into the correct one
Problem: Permission Denied After Re-authentication
Solution: The account may have had its permissions changed:
- Go to the platform's settings (Facebook, Google Ads, etc.)
- Check that Two Minute Reports still has the necessary permissions
- Manually revoke TMR's access and try re-authenticating
- Grant all requested permissions when prompted
Problem: Still Getting Authentication Error
Solution: The account may have been deactivated or suspended:
- Log into the platform directly (Facebook.com, Google Ads, etc.) to verify the account is active
- If the account is deactivated, reactivate it first
- Then return to TMR and re-authenticate
- If you cannot access the account directly, you may need to create a new connection with a different account
Multiple Account Sign-In Issues
If you have multiple accounts on the same platform (multiple Facebook pages, multiple Google Ads accounts), watch for:
Problem: You accidentally authenticated with the wrong account
Solution:
- Go to the platform's settings and verify which account is connected
- If it's the wrong one, revoke TMR's access and re-authenticate with the correct account
- Or create a new data source with the correct account
See Multiple Account Sign-In Issues for more details.
Preventing Future Expirations
- Keep Your Password Safe: Avoid changing your passwords frequently; if you must change it, re-authenticate in TMR afterward
- Don't Revoke Permissions: Don't manually revoke TMR's permissions in your platform's settings unless you plan to disconnect
- Monitor Status: Regularly check your data sources in TMR to ensure all show a "Connected" status
- Refresh Schedules: If a scheduled query fails to run, it may be due to an expired token. Check the data source status
Still Having Issues?
If you've re-authenticated and continue to see errors:
- Take a screenshot of the error message
- Note which platform/data source is affected
- Note whether you can log into that platform directly
- Contact [email protected] with this information
Our support team can help identify if there's a platform-specific issue or account configuration problem preventing successful authentication.