Protocols

This is the interface for ad breaks owned by INPulseLiveSession

An ad break is a collection of ads that are to be displayed in sequence. INPulseLiveAdBreak are part of the “live” API’s, which are better suited for live/streaming video setups. For live breaks, the SDK will not notify the integration when to trigger ads, that responsibility is on the integration.

This @protocol is used to request information regarding the ad break.

This protocol is used to interact with a live session.

The live session does not trigger ads based on content progress and video player state like the standard OOPulseSession. Instead, it makes the ad break data available to the integration and it’s then up to the integration code to get the list of ads from each INPulseLiveAdBreak and trigger the ads when desired. The live session currently only supports linear video ads.

Delegate is used by INPulseLiveSession to communicate with your application.

This is the parent protocol for OOPulseVideoAd, OOPulsePauseAd and OOPulseCompanionAd.

This is the protocol for an ad break owned by an OOPulseSession.

An ad break is a collection of ads that are to be displayed in sequence.

This protocol is used to request information regarding the ad break, or to stop the ad break forcefully.

This protocol is used to handle companion banners, and notify the OOPulseSession about events regarding the companion banner.

As a minimum, the session object must be notified that the companion banner was displayed: -[OOPulseCompanionAd adDisplayed].

Depending on your application, you may also need the clickthrough URL (-[OOPulseAd clickthroughURL]) to respond to viewers tapping a companion banner.

This is the protocol for pause ads owned by a OOPulseSession.

This protocol is used to notify the session about events regarding this ad, and provides access to relevant properties.

You must notify this object of the following events:

• The ad has been displayed: -[OOPulsePauseAd adDisplayed]
• The ad has been closed by the user: -[OOPulsePauseAd adClosed]
• The ad failed to play: -[OOPulsePauseAd adFailedWithError:]

Depending on your application some of the other methods may need to be called in response to user interaction.

This protocol is used to interact with an ad session.

You must notify this object of the following events:

• The content has started: -[OOPulseSession contentStarted]
• The content playback position has changed: -[OOPulseSession contentPositionChanged:]
• The content has played to completion: -[OOPulseSession contentFinished]

The session will notify you through the delegate provided to -[OOPulseSession startSessionWithDelegate:].

This delegate is used by OOPulseSession to communicate with your application.

It will inform your application of the proper time to perform certain actions, or when some events have occurred.

This is the protocol for video ads owned by a OOPulseSession.

This protocol is used to notify the session about events regarding this ad, and provides access to relevant properties.

You must notify this object of the following events:

• The ad has started: -[OOPulseVideoAd adStarted]
• The ad playback position has changed: -[OOPulseVideoAd adPositionChanged:]
• The ad has played to completion: -[OOPulseVideoAd adFinished]
• The ad failed to play: -[OOPulseVideoAd adFailedWithError:]

Depending on your application some of the other methods may need to be called in response to user interaction.