All the steps in the previous chapters can be reused and the Step 2 can be replaced by the following chapters.

Step 2 - Ads

So far so good, but all we've done at this stage is fundamentally tackle the routing for the original source. When you configure a broadpeak.io Dynamic Ad Insertion service, there will be segments for ads referenced in the manifest, which will most likely come from different origins.
How you go about it depends on whether you are using broadpeak.io to process your ads or not.
Ads prepared by broadpeak.io
If you use broadpeak.io for ad insertion, and use the transcoding feature, broadpeak.io will originate the prepared ads through stream.broadpeak.io. In this case, the path to the prepared content will start with /bpkio-jitt/.
For example, the stream output with a short pre-roll might look like the following: