---
url: https://docs.notice.cx/tower/integrations.md
description: >-
  What you are connected with, whether each connection works, and where to
  connect something new.
---

# Integrations

An **integration** is your account with a provider, such as Google or an ad network, connected so NoticeOS can collect from it, usually once for every site it covers. Credentials are entered here, encrypted in the store, and never written in a file. A site's own **Data sources** tab shows the same connections for that one site.

The Integrations page shows what you are connected with, and what else you can connect.

## What you see

The page starts with a one-line summary: **Nothing connected yet · 8 integrations to choose from**, **5 of 8 integrations connected**, or, when something is wrong, **Bing Webmaster Tools needs attention** with the reason beside it. A connection that is failing or overdue is sorted to the top of its group.

Four groups follow, in the order a founder looks for them: **Traffic & search** (Google, Bing Webmaster Tools, DataForSEO, PostHog, Microsoft Clarity), **Revenue** (Mediavine), **Coordination** (calendar feeds, Discord) and **Other**.

Each row is the provider's logo, its name, its one status, and one button. A provider that does not connect in the panel opens its own page instead, with **All integrations** to go back.

A banner at the top names anything that blocks connecting on this installation, with the one command that fixes it. The connect panel does not repeat it.

**Integrations** and **System health** are next to each other in the sidebar, and separate on purpose. Integrations is where you make and change a connection, from the credential store. System health shows what each source is producing, from the collectors' own evidence, grouped by where a failure comes from: this machine's network, a provider, or a site's own setup.

## What you can do

The button is the row's only control:

* **Connect**, when nothing is connected, opens the connect panel: paste the credential, select **Connect**, tick the sites, select **Start collecting**.
* **Reconnect**, when the key is failing, opens the key field again.
* **Manage**, when it is connected, opens the connection: its sites and how each is doing, its schedule, **Replace API key** (tested before it is saved) and **Disconnect** (one confirmation that names what stops).
* **Import from this machine**, on a card marked **Legacy env**, moves the whole secrets file into the store.

## States and labels

The statuses are the same on every screen: **Not connected**, **Not checked**, **Key accepted**, **Signed in**, **URL accepted**, **Collecting**, **Working**, **Overdue**, **Failing**, **Not using**, **Unknown**. Every status is explained in [Connect data sources](/guides/connect-data-sources).

* Small chips beside a status count sites failing or reports missing.
* **Expires in 7d** or **Key expired** appears when a credential has a recorded expiry.
* **Unknown** means the monitoring read is older than ninety seconds or failed, so the page does not mark a connection as working or failing.
* **Not checked** means a saved credential nobody has tested. A green status requires a stored successful attempt; the page never shows green before one exists.
* **Legacy env** marks a provider whose credential still comes from the environment file.

## Related guides

* [Connect data sources](/guides/connect-data-sources)
* [Connect Google](/guides/connect-google)
* [Secrets and credentials](/operate/secrets-and-credentials)
* Every provider, what it provides, and how its test behaves, in [doc 11, Integrations & economics](../11-integrations.md)