Integrations

Six platforms send data to reports. Other ad platforms can be connected and their accounts saved for later. CRM, messaging, file, database and similar sources connect, but send nothing to reports.

• Data chat can answer questions about HubSpot, Salesforce, Slack, Google Drive, monday.com and BigQuery by querying them directly, since their data isn’t stored with your ad results.
• Sources that don’t reach reports show Never synced on the Dashboard. Nothing is wrong.
• Every connection belongs to your agency. Its accounts, not the connection, are assigned to clients.

Each ad account belongs to one client. That decides whose dashboards, reports, pacing and Data chat answers its data appears in.

• Until an account has a client, its data syncs but appears nowhere: not in dashboards, reports or Data chat.
• An account can belong to one client only.
• Assigning an account starts a sync straight away. Earlier days catch up as Orbit re-syncs them, up to 90 days back.
• When you choose accounts on a connection, Suggested means Orbit pre-filled a client because its name appears in the account’s name. Nothing is saved until you save.
• Find Accounts adds accounts already chosen on a connection that are missing from this list. It doesn’t fetch new accounts from the platform: to add those, open the connection from Integrations.
• Re-check account names from Google/Meta refreshes names for every connection whose accounts you pick from a list, not only Google and Meta. Google Analytics, Shopify and Amazon Marketplace aren’t included.

Each connection has its own page, opened with Manage → in Integrations. It shows the connection’s status, how much data it has brought in, its accounts and its recent syncs.

• While a sync runs, the page refreshes itself every 5 seconds, for up to 10 minutes.
• There’s no sync button here, on purpose. The first sync starts when accounts are saved with a client, and the daily schedule takes over from there.
• The rows count is hidden, rather than showing 0, when Orbit doesn’t know where the source’s data goes.
• Anyone at your agency can open the page. Only Owners and Admins can change accounts, reauthenticate or delete.

Each connection has a sync status: on the Dashboard’s Data sync card, and in short in the Last Sync column in Integrations. Synced means it finished a sync in the last 24 hours. Failed and Stale are the ones to act on.

• The Last Sync column shows a time such as “3h ago”, Syncing…, Failed or Never. Hover Failed to read the error.
• Errors are shown as the platform reported them, in the platform’s own words.
• Sync health is the share of your connections that are Synced. Failed and Stale count as issues to review. Never synced lowers the percentage without counting as an issue.
• The “Data updated” badge shows the oldest last sync among your Synced connections, so it’s only as fresh as your least fresh data.

Orbit syncs every connection once a day on its own. There’s no Sync now button: the only way to sync sooner is Retry on a connection that failed.

• Each daily sync refreshes the last 7 days, so changes the platform makes to recent days come through.
• On Sundays, the sync refreshes the last 90 days instead. History older than that isn’t refreshed on its own; email support@orbit.group if you need it.
• A connection’s first sync starts as soon as its accounts are saved with a client.
• In the + Add Connection catalog, six platforms send data to reports: Facebook Ads, Google Ads, LinkedIn Ads, Google Analytics, Shopify and Amazon Marketplace. They’re marked Syncs to reports.
• Other catalog platforms, such as Microsoft Advertising, Snapchat Ads, X (Twitter) Ads and Google Ads Manager, can be connected but send no data to reports yet.
• Retry shows on the Dashboard’s Data sync card next to a connection that failed. Anyone at your agency can press it.

Orbit reads your data through the login used to connect the platform. When that login can no longer reach an account, syncs fail until someone signs in again.

It usually comes down to one of these:

• The login’s password changed, or its sign-in was revoked or expired on the platform’s side.
• The login lost access to an ad account, or its permissions on it were reduced.
• The person whose login it is left your agency and their account was closed.
• The ad account itself was closed or removed.

A connection is only as reliable as the login behind it. These habits keep it signed in.

• Connect with a login your agency will keep, not one tied to someone who might leave. If that login goes, every account on the connection stops syncing.
• When the person who connected a platform leaves or changes their password, reauthenticate it with a current login straight away.
• Keep that login’s access to each ad account on the platform. Removing it there stops the sync here.
• Glance at the Sync health tile on your Dashboard. A broken connection shows as Failed or Stale within a day.
• Finish setup on every connection, so nothing sits at Needs accounts or Needs clients.
• Fix a broken connection by reauthenticating, never by deleting it.

Integrations holds your agency’s connections, which feed everyone’s dashboards and reports. Profile › Connections holds your own Gmail and Google Calendar, which feed only your own Mission Control board.

• Gmail added from + Add Connection is a separate, agency-level source, and it doesn’t reach reports.

A System Role sets what someone can change in Orbit. Owners and Admins can do almost everything. Managers and Specialists work on plans, reports and pacing, and can view clients and connections without changing them.

Owner and Admin have the same permissions, with three exceptions. Only an Owner can make someone an Owner. The last Owner can’t be demoted or removed, so your agency always has one. And only an Admin can choose a client’s Trade Desk advertiser and push to The Trade Desk.

A System Role decides what someone can do. Which clients they can see is set separately, in their Client Access.

A connection can be healthy and still send nothing to a client’s dashboard. Usually an account isn’t chosen, has no client, or comes from a platform that doesn’t sync to reports yet.

• Needs accounts: the connection has no accounts chosen, so Orbit skips it. Press Finish setup → and choose them.
• Needs clients: it syncs, but some accounts have no client, so their data reaches no dashboard, report or Data chat answer. Assign them in Account Mapping.
• The platform doesn’t sync to reports yet. Only platforms marked Syncs to reports do.
• The account was assigned recently, so only recent days have filled in. Earlier days follow as Orbit re-syncs them.
• A teammate can’t see the client at all. Check their Client Access in Team.

Reauthenticating signs the same connection in to the platform again. Its chosen accounts, client assignments and data stay as they are.

• It opens the platform’s sign-in for this connection, then brings you back to its page in Orbit.
• Sign in with a login that can reach the connection’s ad accounts. A different login works if it has access to the same accounts.
• It doesn’t start a sync by itself. Press Retry on the Dashboard to sync now, or wait for the next daily sync.
• Days missed while it was down fill in with the next sync if they’re within the last 7 days. Longer gaps fill in with the Sunday 90-day sync.

Deleting a connection permanently removes its data from every report, and it can’t be undone. To fix a broken connection, reauthenticate it instead.

• Deleting removes the connection’s performance data, its CRM and collaboration data, and its sync history.
• Accounts keep their client in Account Mapping.
• Connecting again syncs from scratch, and history older than 90 days won’t come back on its own.

Your agency saves one set of Trade Desk credentials in Orbit. Claude uses them through Orbit’s Trade Desk server, and Command Center checks them before a push to The Trade Desk.

• Connected means a token is saved. Orbit doesn’t check it with The Trade Desk.
• There’s one set per agency. Saving again replaces it for everyone.
• Once saved, the page shows the Partner, Environment, Mode and when they were Last updated.
• Command Center’s push checks include TTD credentials configured and TTD-MCP key issued.

Claude.ai connects through a custom connector that you approve with your Orbit login. Claude Code and other tools use an API key you create in Orbit.

• Each API key is shown once, when you create it. If you lose it, revoke it and create another.
• Keys last until they’re revoked. The table lists each one’s Prefix, Created date and when it was Last used.
• The approval screen in Claude.ai says what Claude may do: “Read and modify TTD data”, or “Read TTD data (agency is in read-only mode)”.
• Owners and Admins see and can revoke every Claude.ai connection at your agency. Everyone else sees only their own.

+ Add Connection opens Add a Data Source, a catalog of the sources Orbit can connect. Search it or filter by category, and look for Syncs to reports on the sources that feed reports.

• Search data sources... matches a source’s name and its description.
• The category filter starts at All Categories. Categories include Marketing & Ads, Analytics, CRM and Messaging.
• Only six sources carry Syncs to reports: Facebook Ads, Google Ads, LinkedIn Ads, Google Analytics, Shopify and Amazon Marketplace.
• The steps along the top, Connect Platform, Choose Accounts and Sync Data, show where you are.
• Only Owners and Admins see Connect. Everyone else sees “Only agency owners and admins can add connections. Ask one of them to connect this platform.”
• The Trade Desk and Google Tag Manager aren’t in the catalog. They’re cards under AI Tools & MCP Servers in Integrations.

Orbit’s shared GTM service account can act only on the accounts and containers your agency lists under Container scope. Anything outside that scope is rejected.

• In Tag Manager, give the service account the Publish role on each container, or Edit if Claude should change tags but not publish.
• Find account and container IDs in Tag Manager’s admin pane.
• The approval screen in Claude.ai sums up the scope, for example “Read and modify GTM data · 1 account, all containers in scope”.
• Once authorized, the Claude.ai connector also works in Claude Code.

Google Tag Manager shows Connected once your agency has saved which containers Claude may use and marked Orbit’s service account as added. The Integrations card and the GTM page word the earlier steps differently.

• Marking it verified is your agency’s own confirmation. Orbit doesn’t check Tag Manager to see the service account was added.
• Changing the allowed accounts or containers sets it back to Pending verify. Changing Read-only or Allow publish doesn’t.
• There’s one Google Tag Manager setup per agency, shared by everyone.