isHidden
true
false
ExcludeHiddenAccounts = true
WHERE
ManagedCustomerServiceError.CANNOT_HIDE_OR_UNHIDE_MANAGER_ACCOUNTS
ManagedCustomerLink
ExcludeHiddenAccounts
On Monday, August 31, 2015 , in accordance with the deprecation schedule , v201405 of the DFP API will be sunset. At that time, any requests made to v201405 will return errors.
If you're still using v201405, now's the time to upgrade to the latest release and take advantage of fresh new features like DeliveryForecasts . To do so, check the release notes to identify any breaking changes, grab the latest version of your client library and update your code.
Some changes to look out for:
This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions.
- Chris Seeley , DFP API Team
We recently launched manual ad break playback across our iOS, Android, HTML5, and Flash SDKs. For more info on what this means and how to use it, read on!
Under a standard IMA SDK implementation, when an ad rules or VMAP response is returned, the SDK will automatically play each ad break at its cue point. With manual ad break playback, the SDK will instead fire an event when it’s time to play an ad break, and let you decide if or when you’d like to play it.
If you’re happy with your current ad rules or VMAP performance, this change doesn’t require you to do anything - your implementation will continue to work just as it does now. If you’d like more fine-tuned control over ad break playback timing, then we recommend using this feature.
We see two major areas in which this change will help publishers. The first is when a user starts a stream somewhere in the middle of the content instead of at the beginning. (The most common scenario is that the user watched part of the video previously, left the app or page, and returned to continue watching the rest of the video). With a standard implementation, the user will be greeted by (in some cases) a pre-roll, followed by the most recent mid-roll that they watched previously, then the content. By using manual ad break playback you can prevent the pre- or mid-roll (or both) from playing so that the user can go straight to the content, and then resume mid-rolls when the user sees their first mid-roll break for the new session.
The second major use case is misaligned ad breaks. If you’re playing long form content with mid-rolls, and your video fades in and out for mid-roll breaks, you want to make sure that your ad breaks properly align with those fades. In some cases, publishers have told us that the ad break scheduling changes slightly between pieces of content, causing the ad to cut off content for some streams. With this new system, if you know exactly when an ad break should play, you can listen for the AD_BREAK_READY event and delay the ad break playback until the exact time your stream is ready for it.
We have guides for each of the SDKs on implementing this new feature:
As always, if you have any questions feel free to contact us via the support forum .
clearTrackingTemplate()
clearFinalUrl()
clearMobileFinalUrl()
keyword.setCustomParameters({});
clearDescription1()
clearDescription2()
clearDestinationUrl()
clearLinkUrl()
Ins
After our last round of spring cleaning , we've gone back to the drawing board to take another look at how we could make reporting better. There currently is an abundance of Dimensions , DimensionAttributes , and Columns (and more coming with each release), so in an effort to simplify the list of fields, we will be sunsetting the following reconciliation-related dimension attributes / columns in all versions . This will happen on September 1, 2015 .
While the first two have equivalent replacements, the latter ones are not being replaced, as they don’t exist in core product reporting either.
This means that usage of these columns / dimension attributes will begin throwing errors in all versions starting September 1st . If your network is actively using any of these, please update your reports to switch to the supported fields or remove them entirely. If you have any questions, comments, or concerns about this, you know where to reach us !
- Nicholas Chen , DFP API Team