Account and Billing

Managing connected third-party accounts

Learn how to view, authorise, and maintain OAuth connections to Google, Meta, Amazon, and other platforms from your Connected Accounts page.

4 min read 38 views Updated 13 Jul 2026

No results found

Try different keywords or browse all help articles.

    What the Connected Accounts page shows

    The Connected Accounts page, found in the Account area of your dashboard, displays every OAuth connection your user account has made to a third-party platform. This includes Google, Meta, Amazon, Microsoft, TikTok, Shopify, Pinterest, and review platforms such as Trustpilot, Reviews.io, Yotpo, and Judge.me.

    Each connection shows the platform name, the account or user you authorised, and the specific OAuth scopes (permissions) you granted during setup. Scopes define what data or actions the connection can access on your behalf. For example, a Google Ads connection might include scopes for viewing campaign performance and managing budgets, whilst a Meta connection might permit access to ad account data and audience insights.

    This page serves as your audit trail for third-party access. You can see at a glance which platforms are connected, who authorised them, and what permissions were granted.

    How connections work: user account vs. merchant account

    An important architectural distinction shapes how connections function. A connection belongs to the individual user who authorised it, not directly to the merchant account. When you authorise a platform connection, you are granting permission on your personal user account.

    A merchant account accesses a third-party platform through a user's connection being linked to that merchant. This means the same user can authorise a connection once, and then link that connection to multiple merchant accounts if needed. Conversely, a single merchant account can have connections from different users, each bringing their own authorised access to platforms.

    This architecture supports team workflows. If you leave the organisation or change roles, a connection you authorised can be transferred to another team member, or a new user can authorise a fresh connection for the merchant account to use.

    Multi-account support and linking

    Many platforms host multiple sub-accounts under a single login. Google Ads, for example, allows a single Google account to manage multiple advertising accounts. When you authorise a Google connection, the system discovers all Google Ads accounts associated with your login.

    You then choose which specific sub-account to link to your merchant account. If you manage three separate Google Ads accounts and need to run campaigns for two of them, you authorise the Google connection once and link the relevant two accounts to your merchant. The third account remains available in the connection but is not actively linked.

    This flexibility lets you keep all your platform access in one place whilst controlling exactly which sub-accounts feed data or take actions on behalf of each merchant.

    Connection health and token management

    The system monitors the health of each connection periodically. OAuth tokens can expire, be revoked by the user, or become invalid if the platform changes security settings. When a connection's health check detects a problem, the connection status changes to unhealthy or disconnected.

    When this happens, you receive a notification prompting you to reconnect. Reconnecting is straightforward: you authorise the platform again, and a fresh token is issued. The process takes seconds and requires no additional configuration.

    Regular health monitoring prevents silent failures. If a connection degrades, you are alerted before it causes disruption to your campaigns, listings, or reporting. Keeping connections healthy ensures continuous access to the platforms your business depends on.

    Managing your connections

    Use the Connected Accounts page to review and maintain your authorised platforms.

    View connection details. Click any connection to see the platform, the account or user you authorised, the date the connection was established, and the full list of OAuth scopes granted.

    Revoke a connection. If you no longer need access to a platform, or if you suspect a connection has been compromised, you can revoke it immediately. Revocation removes the connection from your user account and stops any merchant accounts linked to it from accessing that platform. You can re-authorise at any time.

    Reconnect if health declines. If the system detects that a token has expired or been revoked, click the reconnect button to re-authorise the platform. This restores access without affecting any other settings or linked accounts.

    Monitor scope changes. Occasionally, a platform updates its OAuth scopes or security requirements. If a scope change is needed, you may be prompted to re-authorise so the connection can request the updated permissions.

    Success criteria

    Your connected accounts are working correctly when:

    • All relevant platform connections show a healthy status in the Connected Accounts page.
    • Each connection is linked to the correct merchant account that needs access to that platform.
    • No alerts or notifications indicate token expiry or revocation.
    • Team members can see which connections are available and who authorised them.
    • When a connection does decline, you are notified promptly and can reconnect within minutes.

    Regular review of your Connected Accounts page, especially after team changes or platform updates, keeps your integrations reliable and your account permissions secure.