Use this guide to resolve common problems.
If your issue persists after following the steps below, contact the Segwise support team.
Network | Common failure cause | Fix |
Meta | Instagram toggle incorrectly set, or Pages/Businesses not both connected | Remove and connect again — set Instagram toggle correctly; connect both Pages AND Businesses |
Google Ads | Organisation policy blocks third-party apps | Ask your Google Admin to whitelist Segwise in Google Admin Console |
TikTok | Permission boxes deselected during OAuth | Remove and connect again — keep ALL pre-checked permission boxes selected |
Snapchat | Unexplained connection failure | Refresh the page and try again; contact support if it persists |
Unity | "Basic" included in the Authorization Header | Remove and connect again — copy ONLY the string after "Basic " |
Axon | Missing Campaign Management API key or session expiry | Use dashboard invite method; ensure all 3 credentials are ready before starting |
Any API key network | Session expiry after 15-20 minutes idle | Close the tab, open Segwise fresh, have all credentials ready before starting |
Adjust | API token from a deactivated user account | Generate a new token from an active account and reconnect |
How to remove a connection and connect again
There is no Reconnect button. To reconnect an ad network, remove the account and connect the network again:
Go to Settings → Integration Hub → Connect Ad Networks.
Under Active, click View on the network. The network's page lists each account with Account, Pages, Owner, Status and Actions columns.
Click the trash icon in the Actions column for the account you want to remove.
Click Connect on the network again and complete its sign-in or configuration dialog.
Your already-synced historical data stays in your reports.
Note: If an integration shows as connected but data is still missing after 24 hours, contact Segwise support with the network name, affected date range, and any error messages. A connected account's Status on the network's page reads, for example, "Active since Jun 03, 2026".
My Google Ads connection says "contact support" or "link expired" — what should I do?
How to fix an expired or broken Google Ads connection in Segwise. This usually happens when the OAuth session expired during the connection flow, or the correct permissions weren't granted the first time.
To fix it:
Close the tab where you currently have Segwise open.
Open a fresh new tab and go to Segwise.
Go to Settings → Integration Hub → Connect Ad Networks.
Click View on Google Ads and click the trash icon in Actions to remove the account.
Click Connect on Google Ads. Complete the sign-in flow and make sure to grant all requested permissions this time.
This resolves most "link expired" or "contact support" errors on the Google Ads connection. If the issue persists after following these steps, reach out to our support team.
Meta shows "Accounts connected successfully" but doesn't appear as connected in Connect Ad Networks — what's wrong?
Why Meta may not show as connected even after a successful connection message. If you see a success message during the Meta connection flow but Meta doesn't appear as connected under Settings → Integration Hub → Connect Ad Networks, this is typically caused by one of the following:
The Instagram toggle was not set correctly before signing in
Both Pages AND Businesses were not connected during the OAuth flow
The connection completed partially due to a session issue
To fix it:
Go to Settings → Integration Hub → Connect Ad Networks.
If Meta is listed under Active, click View and remove the account with the trash icon in Actions.
Click Connect on Meta.
Before signing in, make sure the Instagram toggle is set correctly.
When prompted, connect both your Facebook Pages AND your Businesses.
Grant all requested permissions and complete the flow.
After reconnecting, Meta appears under Active with its number of accounts (for example "1 Account"). If it still doesn't show as connected after reconnecting, please reach out to our support team.
Still stuck? Share a screenshot of the error you're seeing and we'll help.
