Bitmovin IOS v3.8.0(Nowtilus SSAI) with Content Provider Metrics

Step by step integration of the Mediamelon Player SDK with Nowtilus SSAI with Bitmovin Player 3.8.0

Integrating the MediaMelonSmartStreaming Framework

There are five steps involved in integrating the MediaMelon Player SDK using the MediaMelonSmartStreaming Framework:

  1. Importing the framework

  2. Providing asset information for the content before starting the player and after creating its instance

  3. Cleaning up the SDK integration session

  4. Disable manifest fetching by the SDK

  5. Add the SSAI Manager Delegate

  6. Create a new session and update the asset information

  7. Enabling Content Provider Metrics

All Bitmovin Player-related code of the sample application can be found in the Swift classViewController.swift

Open the project file ~/sampleintegration/SampleBitmovinPlayer_v3.8.0_SSAI_MMSDK_<SDK Version>/BasicPlayback.xcworkspace in XCode and edit the file ViewController.swiftas mentioned below

1. Import Frameworks

import BitmovinPlayer
import MMSmartStreamingSDK // For Cocoaapods release
or
import MMGenericFramework // For Framework release

2. Provide Asset information

After the instance of the player is created, and SourceConfig is set with it, we should set the asset information and send it before starting its playback. In ViewController.swift, call function self.configureMMSDK(mediaURL: String, vastURL: String)

3. Cleaning up the SDK Session

We need to clean up the SDK session once the playback is completed. The SDK internally manages the cleanup for most of the cases. For example - when playback finishes or some error is notified.

However, in some error cases, like network reachability issues, the error notification is delayed. Before this error notification is available, the user may trigger another session. Therefore, it is advised to clean up the session once the playback finishes.

We recommend cleanup at the following two places.

  • When the view controller hosting the post-roll ad terminates

  • When the player is restarted

4. Disable manifest fetching by the SDK

If your workflow restricts the manifest to be accessible from both player and the MediaMelon Player SDK simultaneously, then, you can disable the fetch of the manifest via disableManifestsFetch() in method _configureMMSDK()

Note: Disable Manifest Fetch is Optional

5. Add the SSAI Manager Delegate

Add the SSAIManagerDelegate to the ViewController class in ViewController.swift

You can now use the 2 delegate functions to get the event information whenever an AD event occurs

6. Create a new session and update the asset information

During playback updateAssetInfo can be used to create a new session and update the asset information. The usage can be seen in the updateAsset function in the ViewController

7. Enabling Content Provider Metrics

Content Provider Metric Reporting is enabled by calling the setContentProviderDetails function defined in the BitmovinPlayerIntegrationWrapper.swift. This needs to be done immediately after the call to configure the Media Melon SDK

The setContentProviderDetails expects the URL with the Content Provider information as shown in the table below. In case the information is correctly provided it enables content provider metrics reporting.

Parameter
Value

provider

stzp : Starz tbox: Toolbox

tbtoken

JWT Token for Toolbox endpoint

cid

Content ID

sid

Starz session ID

For enabling Toolbox metrics please pass - provider, tbtoken and cid values as shown below

For enabling Starz content provider metrics please pass: provider, cid, and sid values as shown below

Last updated

Was this helpful?