Integrations
Connect Google Search Console, Bing Webmaster Tools and BunnyCDN to a site — and what disconnecting one destroys.
Settings → Site → Integrations is where a site is joined to the three outside services Pulse can pull from. Each has its own page explaining what the data means once it arrives; this one is about the panel itself — connecting, reading the status, and disconnecting.
All three are per site, not per workspace. Connecting a service for one site does nothing for the others, and they carry no data between them.
The three rows
| Row | What it brings in | Where it is documented |
|---|---|---|
| Google Search Console | Queries, pages, countries and devices, plus daily clicks, impressions and average position | Search Console |
| Bing Webmaster Tools | Daily clicks and impressions at site level | Search Console |
| BunnyCDN | Bandwidth, requests, cache hit ratio and edge errors | CDN analytics |
Each row shows a status chip once it is connected: Connected while it is healthy, Syncing while a sync is running, and Error when the last attempt failed. An Error chip is not a retry in progress — a rejected credential parks the connection, and it stays parked until you reconnect.
Connected rows expand to show the details Pulse holds, including Connected since.
Connecting
Google Search Console uses OAuth: the button reads Connect with Google, and it sends you to Google to approve access before returning. Pulse asks for read-only scope and nothing else, which the panel states next to the button.
Bing Webmaster Tools takes an API key rather than an OAuth round trip. ⚠️ That key is per account, not per property — it reaches every site on the Bing account it came from.
BunnyCDN takes an API key and a Pull zone. The form's button reads Connect BunnyCDN.
Tokens and keys are encrypted at rest. Only an owner or admin sees these controls at all; a member sees the rows and their status without the actions.
Disconnecting deletes the data, not just the link
This is the part worth reading before you click. Disconnect is not a "pause", and it does not merely forget a credential. Every disconnect removes the stored history along with the connection, in a single transaction, and nothing keeps a copy:
| Disconnecting | Also deletes |
|---|---|
| Google Search Console | Every stored search row for the site — queries, pages, countries, devices and the daily totals |
| Bing Webmaster Tools | Every stored Bing daily row for the site |
| BunnyCDN | Every stored CDN row for the site |
Warning
Reconnecting does not bring the old rows back — it starts a fresh sync, bounded by what the provider will still give you. That bound is the sharp edge: Bunny serves roughly the last 364 days, so anything older than that is gone for good the moment you disconnect. Search Console's own window is 16 months.
Note the asymmetry with Reset Data, which is the gentler of the two despite the name. Resetting Search Console clears the query-level rows and leaves your daily clicks, impressions and position alone. Disconnecting takes those too.
If what you actually want is to stop a service syncing without losing the history, there is no control for that today. The honest options are to leave it connected, or to accept the deletion.
When a connection breaks on its own
A credential that stops working parks the connection in Error rather than retrying forever, and Pulse stops including it in the sync schedule. That is deliberate: a key that has been revoked will not start working because it was tried again a thousand times.
Reconnecting is the fix, and it is the same flow as the first time. Your stored history survives a reconnect — it is only an explicit Disconnect that deletes it.