DoubleClick Rich Media

New feature

• Support for HTML5 Expanding and Floating creative formats

New feature

• Google Maps component, which lets you drag and drop map functionality into a Rich Media ad
  • this component as part of the latest component set
  • See also Google Maps component API

Bug fixes

• Fixed CS6 issue when publishing to Flash Player 11.2
• Renamed ContextualDiscovery events to StudioEvent.CONTEXT_LOAD and StudioEvent.CONTEXT_FAIL.
• Changed buffer and wait so it doesn't wait if the user calls play before the video has buffered.
• Fixed full-screen button so it doesn't flicker in AS3.
• Fix DART-hosted streaming.

New features

• IM Expand format
• Support for HTML5 assets in In-page format

New feature

• Dynamic Creative code included in the Enabler component in the public MXP starting with version 2.2.0.

Bug fixes

• Fixed problem where "start muted" was tracking in AS3 but not in AS2.
• Video Player Advanced with playlist no longer adding videos with code initiating autoplay.
• Fixed issue of STOP and BUFFERED events not firing in AS2/AS3 in Studio version 2.1.3.
• Fixed problem where "buffer and wait for" command in Video Player Advanced wasn't waiting. (AS3 2.1.3)
• Fixed live top-tier issue of videos showing rainbow pixelation in client creatives using Studio v. 2 components.
• Fixed error in which triggering an exit then immediately calling a close from a Floating creative prevented the URL from opening consistently in Safari.
• Clicking the Close Button component in a Floating unit in Flash IDE no longer warns that the Enabler is required even when the Enabler is there.
• Local Connect no longer throwing null object reference runtime error.
• Fixed problem in AS2 where exit was triggering without an exit name (locally only).
• Video Component Inspector now allows colon character.

New features

• Roadblock preview
• Position tool support for Floating creatives

New features

• Flash-in-Flash Enabler
  Support for Flash-in-Flash in Studio version 2 only when pushing from Studio UI version 1. Push from version 2 expected later in 2012.

Bug fixes

• Fixed error where video view time event started its increment after each expanding of a creative.
• Fixed reporting discrepancies of the same creative running on the same site on different dates.
• Dynamic Video Player Advanced streaming video now works in DoubleClick Studio UI version 2.
• Fixed error is Studio version 2.1.3 where individual video tracking failed with dynamically instantiated AS3 Video Player Advanced.
• "Start muted" checkbox no longer causing volume issues using AS2 in Video Player Advanced version 2.1.3.
• Drag-and-drop component now supported using video component API with Advanced Video Player.
• Fixed error where video stop didn't track on exit click when enabler.stopAllVideos(); was used.
• When video finishes, "call function..." now works in AS2 in Video Player Advanced version 2.1.3.
• Stop and Replay counters are now firing in Video Player.

New features

• Settings tab that lets users edit their own details
• For Admin users, Settings tab moved under Admin section in the UI
• Help link now available at the top of the UI

Highlights

• More creative info in Creative Properties
• 5 different colors for 5 different statuses
• QA Failed status changed to QA Rejected

How does this release affect me?

More creative info in Creative Properties

DoubleClick Studio version 1 displayed an Info button in the QA Console that showed details about the creative being QAed.

In version 2, there's more information available from the Creative properties pop-up, available in the QA tab as well as the Preview tab.

5 different colors for 5 different statuses

These statuses appear in the Creatives screen:

• In development
• Published
• QA approved
• QA rejected
• Trafficked

The colors now match the colors you used to see in Studio version 1 for easier identification.

QA Failed status changed to QA Rejected

This change also matches what you saw in Studio version 1. And it distinguishes QA's rejection of the creative (correct) from QA's failure to occur (not what this status means).

Highlights

• Default to proper QA region
• "No publish" email sent to DoubleClick QA based on account setting or manual selection
• EULA: creation of new external users
• In-page with floating format
  • Public support date: February 23, 2102

How does this release affect me?

Default to proper QA region

Your account's QA region is now selected automatically in the Publish tab.

"No publish" email sent to DC QA based on account setting or manual selection

In Studio version 1, this was an Email QA check box in the Publish tab. Users had to choose to deselect it, regardless of whether or not they had the QA certified setting (“Can create QA users”) enabled for their company account.

In version 2, there are at least two notable enhancements:

• The check box is clearly marked as "Send a notification to DoubleClick's QA team."
• The check box defaults to "off" for clients with the QA-certified setting enabled on their accounts.

This is useful because it requires no further user action, and helps us ensure that errant requests don't waste anybody's time.

EULA: creation of new external users

This introduces an end-user license agreement (and associated logic for checking and enforcing acceptance for each user) to Studio Web UI version 2.

This means we can create new users in version 2. Hooray!

In-page with Floating format (DFA6 only)

And then there were five!

When you build a new creative in version 2, Inpage with Floating is now available in the Format drop-down, along with the four existing formats: In-page, Expanding, Floating, and Peel-down.

Highlights

• Newly released features
  • Peel-down format
  • Campaign and creative deletion
  • UI revamp
• Bug fixes

How does this release affect me?

Peel-down format

The Peel-down format in DoubleClick Studio version 2 works like it does in version 1.

You create an expanding creative using the Expanding component and select "Peel-down" as the format in the creative workflow. You can then preview the effect of the creative in internal and external preview.

Campaign and creative deletion

And then there were four! That is to say, four entities that you can delete from the DoubleClick Studio Web UI:

• Assets in a creative
• Creatives
• Campaigns
• Users

Still to come: Advertiser and account deletion.

UI revamp

It's kind of like "Inception"--a UI overhaul within a UI overhaul.

OK, so "Inception" comparisons are both easy and outdated, but it's true. The new Studio interface has a new look!

Buttons are cleaner, organization is better, and the UI is faster as well. Take a look today!

Bug fixes

• Counters are now detected when strict mode is off
• Fixed issues detecting reporting identifier set with APIs
• Fixed problem with DFA pixel-from-center setting for Peel-down and Floating creatives
• Fixed Peel-down creative sync issues

Highlights

• Support for peel-down creative format
• User deletion

How does this release affect me?

Peel-down format

Beta feature. Full support forthcoming.

User deletion

Exactly what it sounds like.

The first (well, the second) of many entity deletion abilities to appear in the Studio UI version 2. The rest are forthcoming.

For the record, here is what you can currently delete:

• Assets from a creative
• Users

This change achieves parity with previous functionality.

Highlights

• DoubleClick Studio MXP release version 2.1.3, including AS2 and AS3 component, released for download from the Studio Web UI.
• VideoEvent renamed StudioVideoEvent (details below)
• Key bug fixes
  • Better handling of video events (e.g., stop, replay)
  • Improved behavior of event listeners (e.g., hasPage Loaded)
  • Component Inspector UI enhancements (goodbye old logo!)

Bug fixes in DoubleClick Studio component version 2.1.2

• VideoEvent renamed StudioVideoEvent because of a conflict with a native Adobe class. This change is documented in the Rich Media help center, in API documentation, and on the home page of Studio Web UI version 1. (This solves AS3 component version 2 bug where VideoEvent threw an error when published in SWF version 10.2 using CS5.5.)
• Video no longer freezes in AS3 when Scrubber is dragged to the end.
• Show first frame option fixed in AS3.
• Fixed Advanced Video component version 2.1.1 error where making entries in Streaming buffer time field in the Flash CS5 Component Inspector caused compiler error #1067.
• Fixed error where, after replay, VideoEvent.COMPLETE didn't fire and video didn't return to first frame as specified in Component Inspector.
• Local Connect version 2 can now be instantiated programmatically.
• Loader version 2 calls are now traced in Flash output panel.
• Updated logo in version 2 Component Inspector.
• Import of Studio Loader version 2 no longer throws error.
• Roadblocks version 2 no longer throw unhandled security errors.
• Fixed error where pageHasLoaded method always returned false in AS2.
• Advanced Video Player no longer replays video.
• Instantiating VideoPlayerAdvanced no longer throws an error.
• StudioClassAccessor no longer throws error #1009 on publish in AS3.
• Fixed issue where a streaming URL played fine in version 1 components, but had trouble in version 2 components.
• Miscellaneous documentation improvements in version 2 API.
• Fixed streaming URLs in live tags.

New feature

Set backup exit link

How will this feature affect me?

This is a gap item that allows you to set which exit is used as the click-through destination URL for the Rich Media backup image. This setting is pushed along with the creative to the ad server.

You select the backup exit by clicking a radio button next to an exit in the Edit Events tab of the creative workflow in the Studio UI. You can only select one backup exit.

Highlights

• E-mail template changes
• Increased text limit for QA Console messages to 100,000 characters
• E-mail addresses stored at creative and campaign levels

How will these features affect me?

E-mail template changes

This change achieves parity with previous functionality.

There are five kinds of e-mails that DoubleClick Studio sends automatically:

• Invitation: Sent with a URL that lets users accept a new account
• Association: Sent with a code that lets ad-server administrators set up an association with a Studio advertiser for creative transfer
• Publish: Sent when one or more creatives are published to QA
• Notify: Sent with updates about one or more rejected or approved creatives, or a mix of both
• Notify & Submit: Sent with updates about rejected creatives and notification that approved creatives were pushed to the ad server

We overhauled the original versions of these emails which were part of the initial Studio Web UI version 2 launch in Spring 2011. Key changes include:

• More information: Entity IDs everywhere, publisher e-mail address entered in the Publish tab
• More generic descriptors: "Ad server" instead of "DFA," concessions for differences in regional processes
• Better formatting

Increased text limit for QA Console messages (100,000 characters)

This change is an enhancement of previous functionality.

Fun fact: x characters of plain text is roughly equivalent to x bytes. It's not exact, but it's pretty close. The limit for QA Console messages in Studio Web UI version 1 was 4,000 bytes. The limit in version 2 is 100,000 characters.

Based on real-world examples used in the QA process, we increased the limit significantly so that never again shall your QA feedback be hampered.

E-mail addresses stored at creative and campaign level

This satisfies one of the key needs of our QA process: storing the e-mail addresses that are used to send notifications in a creative's life cycle. This feature includes two parity aspects and one enhancement:

• The e-mail address of the user who publishes a creative is stored at the creative level, for pre-population in Notify and Notify & Submit messages sent from the QA console (parity)
• E-mail addresses added to the Notify: and CC: fields in the Publish tab get stored at the creative level, for pre-population in Notify and Notify & Submit messages sent from the QA console (parity)
• E-mail addresses added to the Notify: and CC: fields in the Publish tab get stored at the campaign level, for pre-population in Publish tab for subsequent creatives in that campaign (enhancement)