You may wonder what can you find on broadpeak.io interface, or even what are the core features that make stream manipulations an easy ride? Well, in this section we will take you on little tour to introduce you to the broadpeak.io webapp so you get familiar with it.

Sources : the material for any service you want to create.

Personalization services are based on Sources that you want to manipulate, Sources that you want to use as substitute content, or even Source that you want to insert. Thus, these Sources can be either:

A source is uniquely defined by its URL and its name. Some sources may have options (query parameters for ad servers). For more information about Sources, we invite you to visit the section Concept of Sources

When creating a new source, broadpeak.io checks the availability of the source. In case it's not available or the format fits not technical requirements, the platform prevent the source to be created and display an error message.

Services : perform the stream manipulation

Services manipulate original streams you've already declared in your interface to turn them into streams alterated with alternative contents. Here is a short description of each service type :

Once a service is created, the manipulated stream is displayed by an output URL that can be previewed in broadpeak.io or used in web players, application, web portals etc.

Other icons on the service list allow you to

• Preview the service comparing the original source to the manipulated stream.
• Create and manage slots in Virtual channel and Content replacement slot
• Edit the current service

More details about services can be found in the service chapter of "Understanding broadpeak.io's behavior".

Categories : activate personalisation

Categories are a key feature of stream personalisation. They segment your audience to make it possible to deliver different contents over the same period and on a single requested stream. They are closely linked to slot creation for Virtual Channel and Content replacement services. In case of ad insertion, the personalisation process is done by the ad server itself.

A catagory can be expressed in terms of age (Child, teenage, Young, Adult), geographical area (EMEA, APAC, Americas), device (Mobile, Web, TV) or any segmentation you are commonly using. It includes a sub-category feature to handle zip codes.

As soon as a category is created, you can associate it when creating a slot, along with defining a specific content for the manipulated stream. Then the output URL will deliver the manipulated stream for this category only. Other audience will get the original content. To help broadpeak.io identifying that a user belongs to a category, the stream request from the player has to hold a query parameter such as ?category=*

To illustrate the behavior of categories, let's take an example. Here is what you have created :

• A content replacement service with this output URL stream.broadpeak.io/###hash###/live/index.mpd
• A Category called "Child"
• A slot with a content replacement source adapted to a child audience, and linked to the category "child"

Then when the slot starts :

• stream.broadpeak.io/###hash###/live/index.mpd?category=child will display the replacement source
• stream.broadpeak.io/###hash###/live/index.mpd will display the original content

Details and examples of categories can be found in this part of the documentation.

Account settings : open boundaries of your account

3 elements can be found in webapp's account setting page:

• Team members, to invite user's to your broadpeak.io's space
• API key to create token that are necessary to reach broadpeak.io's API from a third part element. It's necessary as soon as you want to automate and scale up sources and services creation and update.
• Transcoding profiles, that are necessary for use of non transcoded sources (ads and slates) in ad insertion services. Currently, transcoding profiles are implemented by broadpeak.io's Customer Success team. Please reach out to us to have your transcoding profiles set.

API use is detailed further in this documentation