Versions

Your snippet never names a player file. Each time a page loads, the loader asks which version that page should run and is told, so a new version, or a return to an old one, reaches every page without editing it.

Channels

A channel is a name that points at one version and moves when a new version is promoted: dev, beta, stable. Everyone follows stable unless they choose otherwise. beta and dev get new versions earlier. Choosing a channel other than stable needs the Growth edition.

Pins

A pin holds one exact version and never moves until you change it. Pin a property on its Settings → Versions screen in the dashboard (Growth edition and up), or pin a single page in its snippet:

<div id="pb-player"></div>
<script
    src="https://cdn.stream.tulip-tech.app/sdk/web/index"
    data-key="YOUR_KEY"
    data-playlist="YOUR_PLAYLIST_ID"
    data-pin="1.4.2"
    data-target="pb-player"></script>

If your account moves below Growth, a stored property pin and channel are kept but not applied, and pages follow stable. Moving back up restores them.

Which choice wins

The first of these that applies decides the version, highest first.

  1. 1A version named in the snippet itself, with data-pin.
  2. 2The channel one player follows, set in the player editor. Outranks the property pin.
  3. 3One exact version for a property, set on its Versions screen.
  4. 4The channel one property follows, set on its Versions screen.
  5. 5A staged rollout of a new stable version, when your property is in it.
  6. 6The channel your account follows, set in the dashboard.
  7. 7stable, when nothing above says otherwise.

The answer says why: the manifest a page receives carries resolvedBy, such as property-channel:stable, and so does the response header PBP-Resolved-By. You can see which rule chose your version without opening the dashboard.

Staged rollout

A new stable version can reach properties a share at a time — 1%, 10%, 50%, 100% — before it becomes stable for everyone. Which properties go first is fixed per property, so once yours is in, it stays in as the share grows; its version does not flip back and forth. Only properties that follow the default are included: a property with its own channel or pin keeps what it chose.

Withdrawn versions

A version with a serious bug can be withdrawn. It is then never served, even to a page that pins it. Such a page gets the next choice down — the property’s channel, then the account’s, then stable — and resolvedBy ends in ;withdrawn:<version> so you can see why it changed (PBP-101007). A withdrawal reaches pages within about two minutes. The changelog marks withdrawn versions.

When the service cannot be reached

The page still plays. The loader uses the last answer it saved on that browser, and without one, a version built into the loader itself (PBP-101001). Every version is checked against its published hash before it runs.