Managing connections
Refresh ad-account lists, recover from expired tokens, and understand what disconnect would do.
Day-to-day, the only thing you'll do here is refresh ad-account lists and reconnect after a token expires. This page documents both, plus the constraints that affect placements pointing at a connection.
Refreshing ad accounts
When the platform side changes — a new sub-account is added in 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 Actions menu on the connected-account 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.
You can refresh both inside the Connected accounts page and inline when you're creating a new placement — the placement modal has its own refresh button so you don't have to leave the form.
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.
When a token is no longer valid, the next refresh attempt fails. The connected-account card switches state:
- The card border turns red.
- A banner appears: "Authentication required — The access token for this profile has expired."
- A Reconnect button replaces the status badge.
Clicking Reconnect runs the same OAuth flow as the original connection. After approval the same connected account is updated with a fresh token — placements that point at it resume syncing without any change to the placements themselves.
What "Disconnect" would do
The action menu shows a Disconnect option that, when triggered, asks for confirmation: "Disconnect <profile>? This will remove all associated data and stop syncing."
The disconnect action is in the UI but not yet wired up end-to-end. To remove a connected account today, contact your administrator. We'll update this page when self-serve disconnect ships.
When self-serve disconnect ships, it will:
- Stop pulling new data for every placement that pointed at the connection.
- Mark those placements as orphaned — their existing data stays available, but no fresh sync.
- Free the OAuth slot on the platform side, so a different Level user can re-authorize the same login if needed.
Permissions
Anyone signed into Level can connect their own ad accounts and manage their own connections — connected accounts are scoped to the user who created them. To share access to ad data with teammates, link the underlying ad account into a client via a placement; the client (not the connected account) is what teammates see.