PlugsightDocs

Set up Plugsight for a new client

An agency walkthrough - connect a new client's accounts, give them their own MCP server, check what your AI can see and run a first report.

This guide takes you from "we've signed a new client" to your AI answering questions about that client's accounts, and only that client's accounts. It takes about 15 minutes.

What you need

  • A Pro or Agency plan. Marketing and analytics connectors (Google Ads, Microsoft Advertising, Search Console, GA4, Tag Manager, YouTube, Merchant Center) aren't on Free. Agencies with many clients usually need Agency, for its 50 connections and unlimited MCP servers. See Plans.
  • A Google login (or Microsoft login, for Microsoft Advertising) that can open the client's accounts. This is usually your own agency login after the client has given it access, or a login the client created for you.
  • An AI app that supports remote MCP servers, such as Claude or ChatGPT. See Connect AI apps.

Step 1: decide how the client's data reaches Plugsight

An MCP server picks whole connections, not individual ad accounts or sites inside them. That matters for agencies:

How you reach the client What happens
Through your manager (MCC) account, or an agency Google login that sees many clients You already have one connection that reaches every client. A new client appears in it automatically. You can't give this client a server that reaches only their Google Ads account through that connection.
A separate login that only sees this client Connecting it creates a new connection that reaches only this client. You can give the client a server of their own.

Hiding an ad account, site or property with Show sites & accounts hides it from every MCP server, not one. It's for keeping things out of all answers (a test site, a closed client), not for splitting clients between servers. See Choose which sites and accounts your AI can see.

Connecting the same Google login to the same service a second time doesn't add a new connection: it replaces the sign-in of the one you already have.

Step 2: connect the client's accounts

For each service the client uses:

  1. In the Plugsight app, open Connections and click Add connection.
  2. Choose the service, for example Google Ads, Google Analytics 4 or Google Search Console.
  3. Read What happens next and click Continue to Google.
  4. Choose the Google account that can see the client's data.
  5. Tick the permission box Google shows, and continue.
  6. Back on Connections, check the message, for example "Connected you@example.com: 12 Google Ads accounts."

Each Google service is its own connection, even from the same Google login. A client with Google Ads, GA4 and Search Console on a new login uses three connections. If you hit your plan's limit, see Stay within your limits.

The full steps and fixes for each service are on its connector page: Google Ads, Google Analytics 4, Google Search Console, Microsoft Advertising, Google Tag Manager and Google Merchant Center.

If you're using an existing agency connection (your MCC, say) and the client's account doesn't show yet, click Refresh list next to that connection.

Step 3: check which items are visible

  1. On Connections, click Show sites & accounts next to each new connection.
  2. Check every site, property and ad account you want your AI to use shows Visible.
  3. Switch anything you never want in answers to Hidden, for example a staging site.

Step 4: create the client's MCP server

  1. Open MCP servers and click Create MCP server.
  2. Name: the client's name, for example "Acme (client)". Your AI app shows this name, and so does Activity.
  3. Account access: choose Selected accounts and tick only this client's connections.
  4. Allow changes: untick it if this server only needs to read, which is the case for marketing work. Marketing connectors are read-only anyway.
  5. Click Create server.

If the client is only reachable through a shared agency connection (Step 1), you have two choices: keep using your main server and name the client in every question, or ask for a separate login that only reaches this client. See One MCP server per client or purpose.

Step 5: add the server to your AI app

  1. On the new server's page, under Connect an AI app, open the steps for your AI app.
  2. Copy the Server URL and add it to your AI app as a connector.
  3. When the Plugsight window opens, check the server under MCP server is the client's, then click Allow access.

Full steps for each app: Claude, ChatGPT, Claude Code and others. If this is the first marketing connection on the account, refresh the tools list in your AI app and start a new chat.

Step 6: check what your AI can see

In a new chat with the client's server switched on, ask:

  • "List my Plugsight accounts."
  • "List my marketing accounts."

The answer should name only the client's connections and the client's sites, properties and ad accounts. If something is missing, see Your AI can't see an account.

Step 7: run a first report

A good first question for a new client:

  • "Give me an overview of all marketing accounts on this server for the last 30 days compared with the 30 days before."

This runs the account overview deep dive: spend, conversions, CPA, ROAS, organic clicks, sessions and revenue for each platform. Use it as your baseline. Next, try the Google Ads audit and the SEO health check.

When the client leaves

  1. Open the client's server and use Delete server under Danger zone. Its link stops working in every AI app.
  2. On Connections, click Remove next to any connection used only for this client.
  3. If the client was reached through a shared agency connection, hide their accounts with Show sites & accounts so they stop appearing in answers.