> ## Documentation Index
> Fetch the complete documentation index at: https://docs.theaitracker.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Connect Google Analytics, Search Console and Bing Webmaster Tools to see what your AI visibility is actually worth.

AI Tracker measures your visibility in AI answers without any integration at
all. Connecting your analytics and search accounts adds the other half of the
picture: whether that visibility turns into visits.

All three are optional, and each can be connected at any time from **Brand Hub
→ Integrations**, or during [setup](/guides/onboarding).

<CardGroup cols={3}>
  <Card title="Google Analytics 4" icon="chart-simple" href="/integrations/google-analytics">
    Sessions arriving from AI assistants, engagement, and the pages they land on.
  </Card>

  <Card title="Search Console" icon="magnifying-glass" href="/integrations/search-console">
    Clicks, impressions and position, plus how your AI-cited pages rank.
  </Card>

  <Card title="Bing Webmaster Tools" icon="b" href="/integrations/bing-webmaster">
    Bing and Copilot performance, and whether your pages are indexed at all.
  </Card>
</CardGroup>

## What connecting unlocks

| Without integrations | With integrations |
| - | - |
| Visibility scores per platform | ...plus the sessions those answers actually sent you |
| The answers and sources | ...plus how those cited pages rank in search |
| Competitor benchmarks | ...plus the queries you're seen on but not clicked on |

## Two things worth knowing before you start

<AccordionGroup>
  <Accordion title="Each connection is per brand">
    Connections belong to a campaign, not to your account. Running three brands
    means connecting each one to its own property — which is the point in an
    agency setup, where each client's data stays with that client's campaign.
  </Accordion>

  <Accordion title="Analytics and Search Console can use different Google accounts">
    They are connected separately and do not have to share a Google identity.
    This matters when a client grants you analytics access but search access
    sits with someone else, or vice versa.
  </Accordion>
</AccordionGroup>

## Connecting

<Steps>
  <Step title="Open Integrations">
    **Brand Hub → Integrations**, with the right brand selected in the sidebar
    switcher.
  </Step>

  <Step title="Sign in with the account that has access">
    You are sent to Google or Bing to sign in and approve access, then returned.
    Use the account that can actually see the property — access is the most
    common failure here, not configuration.
  </Step>

  <Step title="Choose the property or site">
    Pick which Analytics property, Search Console site or Bing site belongs to
    this brand. AI Tracker preselects the one matching your brand's domain when
    it can find it.
  </Step>

  <Step title="Wait for the backfill">
    Roughly 400 days of history is pulled in within minutes. You do not have to
    wait for tomorrow to see a trend.
  </Step>
</Steps>

## Managing connections

<AccordionGroup>
  <Accordion title="Naming connected accounts">
    Connected Google accounts can be given a nickname. Worth doing the moment
    you have more than two — `client-acme-analytics` is considerably easier to
    pick from a list than a generic Gmail address.
  </Accordion>

  <Accordion title="Domain verification">
    AI Tracker checks that the connected property actually covers your brand's
    domain, and flags a mismatch rather than silently reporting someone else's
    traffic. You can re-run that check after fixing access.
  </Accordion>

  <Accordion title="Switching property">
    Selecting a different property re-runs the backfill and replaces the stored
    history for that source.
  </Accordion>

  <Accordion title="Disconnecting">
    A source can be disconnected from one brand while staying connected to
    others, or removed from your account entirely. Already-collected history
    stays on the pages that used it.
  </Accordion>
</AccordionGroup>

<Note>
  What all of this feeds is the [Traffic page](/guides/traffic) — including its
  two known blind spots, which are worth reading before you reconcile these
  numbers against another tool.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.