# Twitch.tv Connector: Integrate with BigQuery, Redshift, ClickHouse, and more without manual pipelines

> Managed connector to sync Twitch channels, followers, clips, and subscriptions to BigQuery, Redshift, ClickHouse, and more. Zero maintenance.

Source: https://www.erathos.com/en/blog/new-twitch-tv-connector
Em português: https://www.erathos.com/blog/new-twitch-tv-connector
Published: 2024-08-20
Category: New Connectors

![Twitch logo with streaming metrics being synced to a data warehouse](https://cms-media.erathos.com/QNbqWjj9r4KYlVy8KEmZdnxrEjI-1.png)

We now support Twitch.tv among Erathos connectors.

Twitch is a live streaming platform launched in 2011 that quickly became one of the largest in the world, especially focused on video game broadcasting. Beyond gaming, the platform also hosts music, sports, art, chat shows, and other forms of live entertainment. The solution has scaled and gained significant relevance in recent years, also becoming a workspace for creators and brands that leverage Twitch's influence in marketing strategies, community building, training, and corporate broadcasts.

Unlike a CRM or a support tool, Twitch data doesn't live in a sales spreadsheet; it is scattered across channel performance, audience engagement, and sponsorship results. Without consolidating this into a data warehouse, channel or community managers remain dependent on the native Twitch dashboard, which doesn't join this data with anything outside the platform itself.

Erathos is launching a managed connector for Twitch.tv. Eleven endpoints available, eight supported destinations, and zero pipeline code to write or maintain.

## What you can ingest

The Twitch connector delivers eleven endpoints ready to be materialized in your destination data warehouse:

Endpoint

What it contains

`user`

Profile data for the connected user/channel

`channels`

Channel information

`followers`

Channel followers

`subscriptions`

Channel subscribers (subscriptions)

`videos`

Published videos, including VODs

`clips`

Clips created from broadcasts

`polls`

Polls held during live streams

`goals`

Channel goals (followers, subscriptions, etc.)

`moderators`

Channel moderators

`vips`

VIPs configured in the channel

`banned_users`

Banned or timed-out users

Supported destinations are **BigQuery**, **Redshift**, **Databricks**, **ClickHouse**, **PostgreSQL**, **Supabase**, **Azure Synapse**, and **Amazon S3**.

## What you can do once Twitch data lands in the warehouse

**Channel performance over time.** With `followers`, `subscriptions`, and `videos` in the warehouse, you can build historical growth series that Twitch's native dashboard doesn't keep beyond a short window, which is essential for understanding seasonality and the impact of specific campaigns.

**Sponsorship ROI and paid collaboration.** By joining `clips` and `videos` published during a period with campaign data from another source (CRM, contract spreadsheet, paid media tool), you can measure the actual return on a partnership, not just the isolated number the brand receives from Twitch.

**Community health and moderation.** With `banned_users`, `moderators`, and `vips`, you can track how much the channel relies on active moderation over time, an indirect sign of community health that is rarely measured with historical data.

**Engagement by content format.** Joining `polls` with `videos` lets you identify which type of broadcast actively engages the audience the most, providing valuable information to make future content decisions based on data, not gut feeling.

## How to authenticate

The Twitch connector authentication is done via **OAuth**, with no token to generate or copy manually. Just log in to the Twitch account associated with your browser and click **Authorize Twitch.tv** during the connection setup on Erathos.

The complete process is documented at [docs.erathos.com/connectors/apis/twitch.tv](https://docs.erathos.com/connectors/apis/twitch.tv).

## Why outsource ingestion to Erathos

The connector's premise is straightforward: the engineering overhead of maintaining ingestion shouldn't be the responsibility of channel or community managers. Pagination, rate limiting, retries, schema evolution, failure alerts, volume drop alerts, and backfills, all of this is the responsibility of the ingestion platform operator.

With the connector configured, the platform delivers:

**End-to-end visibility of every execution.** Extraction time per endpoint, record count per window, which windows were processed, and where retries occurred.

**Out-of-the-box alerts.** Execution failures, volume drops per endpoint, and window delays are detected and routed through the alerting integrations your team already uses.

**Reprocessing as a native platform operation.** When you need to reprocess a window, it is a platform operation, not an improvised script run in the warehouse.

## Frequently asked questions about the Twitch connector

**Does the Twitch connector use an API key or OAuth?** OAuth. You authorize access by logging directly into the Twitch account associated with your browser, without needing to manually generate or copy any token.

**What Twitch data can I bring to my warehouse?** Profile, channel, followers, subscribers, videos, clips, polls, channel goals, moderators, VIPs, and banned users data. The complete list is in the endpoints table above.

**Does the connector support incremental sync?** Yes, endpoints are synced incrementally after the initial historical load.

**Does the connector work for agencies managing multiple channels?** Yes, as long as each channel is configured as a separate connection and authorized with its corresponding Twitch account.

**Which destinations does the Twitch connector sync data to?** BigQuery, Redshift, Databricks, ClickHouse, PostgreSQL, Supabase, Azure Synapse, and Amazon S3.

## Available pipelines

The Twitch connector is available with the following destinations:

- [Twitch.tv → BigQuery](https://www.erathos.com/pipelines/twitch-tv-bigquery)
- [Twitch.tv → Redshift](https://www.erathos.com/pipelines/twitch-tv-redshift)
- [Twitch.tv → Databricks](https://www.erathos.com/pipelines/twitch-tv-databricks)
- [Twitch.tv → ClickHouse](https://www.erathos.com/pipelines/twitch-tv-clickhouse)
- [Twitch.tv → PostgreSQL](https://www.erathos.com/pipelines/twitch-tv-postgresql)
- [Twitch.tv → Supabase](https://www.erathos.com/pipelines/twitch-tv-supabase)
- [Twitch.tv → Azure Synapse](https://www.erathos.com/pipelines/twitch-tv-azure-synapse)
- [Twitch.tv → Amazon S3](https://www.erathos.com/pipelines/twitch-tv-amazon-s3)

## Get started now

[Create your Erathos account](https://app.erathos.com/signup?slug=blog&button=cta&utm_campaign=twitch_release) and connect your Twitch channel to your warehouse in minutes, with zero pipeline code to write, maintain, or monitor.
