|
||||||
Hello,
Michael here and I work along with Teejay.
The iOS DAI supports OM SDK which is the same with the one your shared for iOS client side link in your first message. In which, IMA SDK introduces an API for registering these overlays with the Open Measurement SDK. Having said that, I believe the best way to achieve your use case is to follow the registering of video controls overlay obstructions. This way it will be considered as friendly obstruction and will not violate anything from both IMA and OM SDK. A sample can be found at the near bottom of the documentation, posting snippet below.
UIView *myTransparentTapOverlay = [[UIView alloc] initWithFrame:CGRectMake(0, 0, 300, 250)]; UIButton *myPauseButton = [[UIButton alloc] initWithFrame:CGRectMake(0, 0, 50, 10)]; // Substitute "myTransparentTapOverlay" and "myPauseButton" with the elements // you want to register as video controls overlays. // Make sure to register before ad playback starts. IMAFriendlyObstruction *overlayObstruction = [[IMAFriendlyObstruction alloc] initWithView:myTransparentTapOverlay purpose:IMAFriendlyObstructionPurposeNotVisible detailedReason:@"This overlay is transparent and does not impact viewability."]; IMAFriendlyObstruction *pauseButtonObstruction = [[IMAFriendlyObstruction alloc] initWithView:myPauseButton purpose:IMAFriendlyObstructionPurposeMediaControls detailedReason:@"This is the video player's pause button."]; [displayContainer registerFriendlyObstruction:overlayObstruction]; [displayContainer registerFriendlyObstruction:pauseButtonObstruction];
Let us know if you have further question in the above information.
Regards,
|
||||||
|
||||||
Hello Mohammed,
This is Jackson from the IMA SDK team. We recently found an error in our OM SDK guide, which is not updated (please see the link ).
The change is can be see in the 'Key point', and is:
The 'detailedReason' string used when creating a IMAFriendlyObstruction must follow the IAB standard by: