Trust & data
Data & Platform Connections
Twitch, YouTube, and Kick connections are not interchangeable. This page explains the provider-authorized inputs StreamPulse uses today, the gaps it leaves visible, and what to do when a connection needs attention.
Connection basics
Connections are optional and start from the signed-in Connections page. They require an active paid workspace with the relevant platform coverage, and only workspace admins can connect or disconnect a provider. Provider names describe compatibility and do not imply partnership, endorsement, or affiliation.
Current provider capability table
Inputs are recorded only when the connected provider returns them. “Unsupported” means StreamPulse does not simulate the missing measurement.
| Provider | Connection and permission state | Inputs available now | Known unsupported or limited |
|---|---|---|---|
| Twitch | A paid, entitled workspace admin authorizes the Twitch account. StreamPulse requests the connection scopes for account identity, channel subscriptions, and follower data. | Authorized creator identity plus live-stream availability, concurrent viewers, stream title, and game/category when Twitch returns them. | Follower totals and retention are not treated as available in the current Twitch snapshot flow; StreamPulse does not fill them in with estimates. |
| YouTube | A paid, entitled workspace admin authorizes the connected channel with YouTube read-only access. | Authorized channel name, subscriber count, total views, video count, and—when a live broadcast is found—live availability, concurrent viewers, and title. | Watch-time retention and clip signals are not available in the current connection flow. The channel snapshot does not treat live viewers or categories as channel-level fields. |
| Kick | A paid, entitled workspace admin authorizes Kick channel-read access. The connection identifies the channel slug. | Authorized channel slug plus live-stream availability, concurrent viewers, stream title, and category when Kick returns them. | Follower totals, recent VOD discovery, retention, click-through rate, and historical stream metrics are not available from the documented endpoint StreamPulse uses. |
Freshness and recovery
Freshness states
StreamPulse shows the last successful sync when one exists. While data is refreshing, retained samples remain available. A provider reporting the channel offline is not a connection failure. A connected provider with no saved samples needs a refresh to capture the first sample.
Recovery route
If authorization expires or a required permission is missing, reconnect the provider and approve the requested access. If a provider is temporarily unavailable or rate-limited, use Refresh data again later. Retained samples can be marked stale during those states rather than shown as current.
For a connection issue, use Support and name the provider, the workspace if applicable, and the state or message shown in Connections. Do not send provider tokens.