Server-side dynamic ad insertion is a combination of manifest manipulation, ad server communication, and ad bitrate and resolution normalization, all of which happens on the server-side before presenting a manifest to clients. Server-side ad insertion may also be referred to as dynamic ad insertion, or ad stitching.
By whatever name it is known, server-side ad insertion is difficult to get right for numerous reason:
- SERVER-SIDE AD INSERTION REQUIRES A HIGHLY SCALABLE ORIGINATION SERVICE.
- PERSONALIZED MANIFEST ARE NOT CACHEABLE.
- REPORTING AND CUSTOM PLAYER BEHAVIOR REQUIRES CLIENTS TO KNOW AND AD HAS BEEN PLAYED.
- DIFFERENT AD STANDARDS (VAST, MAPS), AD SERVERS, ORIGIN SERVERS, AND PLAYER ENVIRONMENTS COMPLICATE SERVER-SIDE AD INSERTION WORKFLOWS TO COPE WITH FRUSTUATIONS IN DEMAND FOR JUST-IN-TIME SERVER-SIDE AD INSERTION, A HIGHLY SCALABLE ARQUITECTURE IS REQUIRED- PARTICULARTY FOR BROADCASTES THAT MUST DEAL WITH THE SHARP PEAKS IN DEMAND THAT BREAKING NEWS, SPORTS EVENT AND POPULAR TV SERIES BRING. ADS IN STREAM PROVIDES CLOUD-BASED VIDEO PROCESSING WITH A SERVER-SIDE AD INSERTION INTEGRATION TO GOOGLE AD SERVERS TO MEET AUDIENCE DEMAND.
WHEN EVENTS ARE UNDERWAY, THE NUMBER OF CONCURRENT VIEWERS CAN VARY GREATLY AND UNPREDICTABLY. FOR EXAMPLE, VIEWERSHIP FOR A CLOSELY PLAYED GAME MAY REMAIN STEADY FOR MUCH OF THE CONTENT, THEN SURGE BY HUNDREDS OF THOUSANDS OF NEW VIEWERS DURING THE LAS FEW MINUTES.
THE KEY TO MANAGING WIEWER VARIANCES IS A VIRTUALIZED ENCODING AND PACKAGING PREPARED FOR RAPID DEPLOYMENT AND HOSTED IN A CLOUD INFRASTRUCTURE FOR QUICK AUTO-SCALING AND AIS HAS YOU COVERED. BECAUSE DEDICATED SINGLE PATH HARWARE ENCODERS AND PACKAGERS LACK FLEXIBILITY, THE PRACTICAL SOLUTION IS TO SPIN UP INSTANCES OF CLOUD-BASED VIDEO PROCESSING AS THEY ARE NEEDED. OUR CLOUD ARCHITECTURE IS UNIQUELY WELL SUITED TO CREATING MILLIONS OF INDIVIDUALLY TAILORED MANIFESTS OF CONTENT AND ADVERTISING FOR LIVE-STREAMED EVENTS.
