Syndicate Streaming Content with Tracking Across Multiple Distribution Channels

With Real-time Streaming you can syndicate content through multiple distribution partners or channels. This can be helpful to maximize the number of viewers or monetizing content through other platforms. In order to accomplish this, it is important to be able to track syndicated streams for analytics and billing.


Broadcast syndication defines a process for leasing the rights to distribute content through various third-parties. If you own the distribution rights to content you are broadcasting, you may want to sell the feed to other platforms to playback to their audience in order to maximize reach. It is important to do this securely while also metering who is consuming the content that you are distributing.

Syndication workflow

The following is an example workflow for setting up syndicated substreams:

  1. Create a Publish token for your broadcast. Make sure this token has the secured setting enabled.
  2. Before the broadcast begins, create a Subscribe token with tracking for each 3rd party you are syndicating a stream. These Subscribe tokens function as "master" tokens for each platform you are syndicating content. The master Subscribe token can be used by the 3rd party to self-sign other Subscribe tokens for their users if they need to secure their streams.
  3. Begin broadcasting your premium content via The 3rd parties can use the provided Subscribe token to access the stream for their viewers or to sign more Subscribe tokens for their viewers.
  4. When the stream is running, the media server will gather statistics for the viewer associated with the tracking ID information. Since charges based on bandwidth, this data can be used to bill the 3rd parties relative to their consumed data.

RTMP syndication

In certain circumstances, you may also choose to distribute content with RTMP to share on public commercial streaming platforms. Follow the Simulcast WebRTC and RTMP on OBS guide to learn how you can use OBS to create a real-time WebRTC stream and an RTMP stream simultaneously. It is important to note that the WebRTC stream will be real-time (<500ms), while the RTMP stream may have more delay (6s - 30s).

How-to track syndication

The Streaming platform lets you track the following data while using syndication:

  • Bandwidth consumption per a distribution channel. The trackingId parameter, which groups viewers of the same stream, allows you to get the aggregated bandwidth usage of all viewers. This is useful for billing or user engagement analytics.

  • Bandwidth consumption of a specific viewer. By assigning a unique identifier to each viewer via the customViewerData parameter, you can access the bandwidth consumption of each viewer for analytics purposes. This form of tracking is not available for everyone and requires contacting sales.

To manage viewing access, there are two types of tokens you use to syndicate:

  • Subscribe tokens can be used to restrict access for "who" may view a stream. You can assign a trackingId to each token for correlating usage.
  • Self-signed Subscribe tokens are JSON Web Tokens (JWT) that can be generated using a single subscribe token as the parent. These tokens can also be used to restrict access for "who" may view a stream but are instead created, signed, and managed by the content owner or distributor.

Creating a Subscribe token with tracking ID

You can create a subscribe token with a tracking ID using either the Create Token API or the dashboard.

To use the Create Token API, add the following to your API request body:

  "label": "with-tracking-2",
  "streams": [
      "streamName": "test-stream",
      "isRegex": false
  "tracking": {
    "trackingId": "JohnDoe"
  "originCluster": "ams-1"


Region Origination

The published stream and Subscribe token must originate from the same cluster region. The "Auto" region may be selected for both if the broadcast region changes from stream to stream. For more information, see Multi-region Support.

Alternatively, you can specify a tracking ID using the dashboard when creating a Subscribe token.


Tracking with self-signed Subscribe tokens

Once you have created a Subscribe token with a tracking ID, you can self-sign the token by following this procedure. Be aware of the limitations.

Viewing statistics

With your API Secret found on the dashboard, you can query information based on your viewer's tracking ID and other data using the following REST APIs:

To get the bandwidth consumption of a specific viewer, use the Viewer Records REST API.