Changelog

Server-Side Ad Tracking (SSAT)

You can now enable Server-Side Ad Tracking with Ad Insertion services.

This causes broadpeak.io to replace ad segment URLs in manifests with specific URLs that redirect the player to the actual segments.

When broadpeak.io receives these requests, it knows that the player has accessed the segments, and calls the ad tracking server with the appropriate beacons.

Thanks to this mechanism, the ad tracking server can track ad playback without any specific implementation in the player.

When SSAT is enabled, you can enable an option (Check ad media segment availability) that checks that the ad segment exists before replacing its URL, avoiding a call to the ad tracking beacon for a segment that cannot be actually played.

See below a screenshot of these options in the Ad Insertion configuration page of the WebApp:

Please see the serverSideAdTracking object in our ad-insertion API reference
for the corresponding API.

Service configuration (WebApp)

When creating a service, the WebApp now displays possible use cases for each service type.

See below a screenshot of the service creation page:

Service configuration (WebApp)

We have added badges in the drop-down selection menus of the service configuration pages.

Blue badges indicate the source type, tan badges indicate their format.

You can filter the source list by typing their name, type or format.

Ad Server check

When we check the connectivity to an Ad Server, we now include the query parameters in the request.

Also, we now treat http errors (4xx and 5xx) as warnings, so that the source can be created.

These two changes will make it easier to use certain Ad Servers with broadpeak.io.

Slot management (beta, webapp)

We now display the seconds in the "Start time" and "End time" fields of the Calendar view.

Slot management API

We now check that a new or updated slot does not overlap with another slot on the same category.

This applies to both Content Replacement and Virtual Channel services and both the REST and ESNI APIs.

Pagination support

Pagination headers are now also present in the response of the GET all slots APIs.

Please see our API reference
for examples and more details.

Slot management (beta, webapp)

In the Slot creation or edition form, the "Replacement content" field is now located between the "Event name" and "Start time" fields.

Service configuration

We have removed the second step in Content Replacement and Virtual Channel service configuration. It is no longer possible to create a slot in this process. This possibility is provided by our Scheduler function.

We have fixed an issue where Chrome did not display AM/PM in certain time fields.

We have enabled Gzip and Brotli compression on manifest requests (stream.broadpeak.io endpoint).

Compression is used when the client includes a Accept-Encoding header with either br, gzip, or both.

When both are accepted, Brotli is selected.

This allows reducing the egress consumption with clients that support it.

It is now possible to delete future slots and end current slots with our scheduler.

The "Delete slot" button is present:

• in the "Actions" column of the List view
• in the slot edition window of the List and Calendar views.

The "Delete slot" button is replaced by an "End it now" button if the slot is in progress (started but not finished).

Clicking "End it now" changes the duration and endTime so that the slot ends in 10 seconds.

Note: past slots cannot be edited or deleted. The "Delete slot" button is greyed-out in this case.

Check status API

We now return an error when the manifests of a source do not match with the declared type (Live or Asset).

In DASH, Live sources must have a type="dynamic" attribute and Assets must have type="static".

In HLS, Live sources must have EXT-X-PROGRAM-DATE-TIME tags in their media manifests, while Assets must not.

Therefore, it is no longer possible to create such sources.

We now return several headers in the responses of the GET all APIs:

• x-pagination-count: number of items in the response body
• x-pagination-limit: max number of items in a page, as set in the query
• x-pagination-offset: offset of the first item, as set in the query
• x-pagination-total-count: total number of existing items

Please see our API reference
for examples and more details.

It is now possible to edit future and current slots with our scheduler. This is accessible from:

• the List view: click on the "Edit slot" button (pencil) of a slot in the "Actions" column
• the Calendar view: click on a slot

This opens a window where you can:

• edit all fields of a future slot (not started yet)
• change the duration or endTime of a current slot (started but not finished)

Notes:

• past slots cannot be edited. The "Edit slot" button is greyed-out in this case.
• the "Delete slot" button produces an error message with past and current slots. We will fix this soon.