Agency

Agency integrations

Connect your agency-level manager accounts, reporting access and client data sheets once - every client inherits them.

I'm using the platform as a
All help topics

Your agency-level integrations are configured once under More - Connections - Integrations (admin-only) and then power every client, rather than being set up per account. This is the backbone of how you manage many clients efficiently.

Google

One card covers Google Analytics, Search Console and Google Ads, in three steps:

  1. Sign in with Google. Use the Google account that manages your Ads manager account - this is your main login, and the address your clients are told to grant access to. If some clients' Analytics, Search Console or Ads sit under a different Google account, add it under Other Google logins with Add another Google login; the list shows how many client accounts each one reads. On each client's Google cards you then pick which login reads each platform, and the platform remembers it. (Clients can connect their own Google accounts too; those appear in the same dropdown.)
  2. Paste your Google Ads developer token. Google only shows it inside your manager account, under API Center - the card links straight there. It is checked with Google before it saves: a token Google does not recognise is refused, and a token with only Test access saves with a warning, because live client accounts refuse it until Google approves Basic access. Apply for Basic access in the API Center; the same token keeps working once approved. Skip this step if you do not run Google Ads.
  3. Pick your manager (MCC) account from the list of manager accounts your Google login can reach. If there is only one, it is chosen for you. If yours is not listed, you can type its ID.

Until you sign in, you can still set the address clients are told to grant access to, under Reporting access email.

Meta

  1. Paste a System User token. In Meta Business Settings, under System Users, pick or add an admin system user, choose Generate token, set it to never expire and tick the permissions the card lists. The token is checked with Meta before it saves.
  2. Your Business Manager is read from the token where Meta allows it - one business fills itself in, several become a list. Otherwise type its ID, found in Business Settings under Business info.

Clients then add your Business Manager as a Partner on their ad account, Page and Instagram.

Optional: under Advanced, connect your own Meta app so clients can connect Meta in one click, with your branding on Facebook's consent screen.

TikTok

  1. Paste your access token. In TikTok Business Center, open your developer app, authorise it on your Business Center with ad account and reporting access, and copy the long-lived access token. It is checked with TikTok before it saves.
  2. Your Business Center is read from the token where TikTok allows it - one fills itself in, several become a list. Otherwise type its ID.

Clients then add your Business Center as a Partner on their advertiser account.

Once set, each client's connection screen shows the relevant ID and the steps for the client to follow. See Connecting Google and Connecting Meta, TikTok, LinkedIn & X.

AI provider keys

AI provider keys have a page of their own, AI keys, linked from the top of Integrations. Add your own keys there for the AI providers that power the platform (the main AI model, plus the engines behind AI Search and market research). Keys are write-only - entered but never shown back, for security. Your Claude (Anthropic) key must be created inside a workspace in the Anthropic Console; a key that is not tied to a workspace is refused when you save it. For your workspace's first 7 days your Claude and Google AI work runs on ours, so nothing waits on these two keys at the start - see The setup hub.

Client data sheets

Some clients keep spend, deals or offline revenue somewhere no connector can reach. For them the platform creates a Google Sheet per client and reads it daily (see Manual Uploads). Connect your own Google service account and those sheets are created, owned and read under your agency's identity rather than the platform's.

It takes about fifteen minutes, done once for the whole agency: a shared drive, a Google Cloud project with the Sheets and Drive APIs on, a service account added to that drive, the form under Client data sheets, and a template spreadsheet built for your workspace. Every step, what a partial save does, and what to check when a client cannot open their sheet are in Client data sheets under your own Google account. Do it before the first client sheet is created - a sheet made under the platform's account does not move across on its own.

Telephony

Voice Outreach is marked coming soon, so its voice and telephony keys are not shown on the Integrations page at the moment. The section returns when the tool launches. Keys already saved are kept.

Good to know

  • Agency-level credentials beat per-client setup - one configuration, every client benefits.
  • Keep the two onboarding surfaces (the Setup tab and the setup wizard) in mind - both reflect what you've configured here.