Managing connections
Refresh ad-account lists, recover from expired tokens, and disconnect a connection safely.
Day-to-day, the main things you'll do here are refresh ad-account lists, reconnect after a token expires, and — occasionally — disconnect a connection you no longer need. This page documents all three, plus what each one means for the ad accounts pointing at a connection.
Refreshing ad accounts
When the platform side changes — a new sub-account is added in a Google Ads MCC, an ad account is granted to your Business Manager, an account is suspended — Level needs to be told to re-fetch.
To refresh:
- Open the kebab menu on the connection card.
- Click Refresh accounts.
Level calls the platform's API again with your stored token, replaces the cached account list, and updates the expanded view in place.
Reconnecting after token expiration
OAuth tokens don't last forever:
- Google Ads — refresh tokens are durable but can be revoked from the Google account's security settings.
- Meta — long-lived tokens expire after roughly 60 days. Meta also caps data access at roughly 90 days per authorization.
Level warns you ahead of time with pills on the card: Expires in {n}d (warning at 14 days or less, red at 3 or less) and, for Meta's data-access window, Access in {n}d. Once a token is no longer valid, the pill flips to Token expired (or Access expired) and the card switches to a Reconnect required state:
- A banner explains what happened: "Authentication required — The access token for this profile has expired. Please reconnect to resume data sync."
- A Reconnect button appears on the card.
- A red dot appears on the Connected Accounts item in the sidebar so you notice even from another page.
The Reconnect required state is persistent — it survives reloads and stays until you actually reconnect.
Clicking Reconnect runs the same OAuth flow as the original connection. After approval the same connection is updated with a fresh token — ad accounts that point at it resume syncing without any change to the ad accounts themselves.
Level distinguishes a few error states on the card:
| Banner | What it means | What to do |
|---|---|---|
| Authentication required | The access token has expired. | Click Reconnect and re-approve. |
| Platform account access not granted | You authorized, but didn't grant access to the platform accounts Level needs. | Reconnect and allow access to the accounts in the platform's consent dialog. |
| A transient error | The platform API hiccuped — nothing is wrong with your token. | Click Retry. |
Disconnecting
To remove a connection, open the kebab menu on the card and click Disconnect.
If nothing depends on the connection, it's removed right away. If the connection backs one or more ad accounts, Level shows a red "Disconnect anyway?" confirmation that spells out the consequences. Disconnecting will permanently:
- delete those ad accounts,
- erase all metrics collected for them,
- remove their data from your reports,
- stop syncing them.
This cannot be undone. If you only need to fix a broken token, use Reconnect instead — it keeps everything in place.
After disconnecting, the same platform login can be re-authorized later — by you or a different Level user — but it starts from scratch: new connection, new ad accounts, new sync.
Permissions
Anyone signed into Level can connect platform accounts and manage their own connections — connections are personal to the user who created them. To share ad data with teammates, wire the underlying platform account into an organization as an ad account; the organization (not the connection) is what teammates see.