Mobile Web and Desktop HTML5

Rich Media QA guidelines

Quality Assurance testing conducts numerous tests that vary based on the format and features of each creative. These tests are meant to demonstrate the technical integrity of the creative, without assessing or judging any aspect of its design. Such questions are for the client to decide.

1. Use the QA tab

Use the DoubleClick Studio QA tab to review and test creative functionality before your creative goes live. The QA tab helps you give final approval or send creatives back to the developer to fix problems.

There are three lists of creatives in the side panel of the QA tab:

  • Pending: ready for QA processing
  • Approved: okayed by the QA specialist
  • Rejected: rejected by the QA specialist

To view a creative, click a creative in the Pending list.

QA from Preview

As an alternative to testing the creatives in Studio, you can QA the creative by reviewing an external preview.

To view an external preview:

  1. In the Creatives tab, click Campaigns, then select your campaign.
  2. Click the preview URL at the top. 

To share a preview externally, you can email the external preview link:

  1. In your campaign view, click Email preview link and enter the necessary information.
  2. An email containing the external preview link is sent to the email address provided in the "Notify" field. No edits can be made to the creative from an external preview.

Use the external preview URL to preview your creatives in each OS and browser combination without having to sign in to Studio each time.

Creatives can't be approved or rejected from an external preview. To approve or reject, use the QA tab.
2. Open the Event summary (output console)

Click Show details > Event summary (output console) to view events specific to the creative you're previewing. The Event summary logs the standard and custom events implemented in the creative. Events are displayed at the bottom of the event summary panel.

As you interact with the creative, the events fire in real time. Filter events using the options in the "Type" and "Show" fields.

Filter events by type:

  • All: List all events.
  • Custom: List only custom events added by the creative developer.
  • Standard: List Studio standard events, which are automatically added to the creative.

Filter events to show:

Using the "Show" filters, you can show:

  • All: List all events.
  • Triggered: Show only events that have been triggered in the current preview session.
  • Untriggered: Show events that haven't been triggered in the current preview session.

Click Event log to view each event logged by the creative with a timestamp. Click Clear log to clear out the log and start over.

3. Test creatives for basic functionality using test scripts

These checklists include basic tests and test cases, along with detailed checklists, specific to the format1 and features of each creative.


1Availability of creative formats varies, depending on your level of support.

2If you're building to DoubleClick specs or if you don't have a spec sheet but want to check against general guidelines, use the DoubleClick Best practices (LCDs) checklist (more below).

4. Test creatives against site specs (LCDs)

Many publishers provide their own creative specifications that you should use, if available, as QA guidelines. These specs can include file size, dimensions, video length, and frame rate.

If you don't have the publisher's specs for a creative, there's a set of recommended creative specs--also known as lowest common denominator specs (or LCDs)--unique to each creative that most publishers accept. These differ for the North America (NAM) and Europe, Middle East and Africa (EMEA) regions based on publisher practices. You can use these test scripts to verify DoubleClick's best practices (LCDs).

5. Test your creative in multiple browsers

The DoubleClick QA team doesn't test on every browser version listed in the supported browsers article, but we do test on the most commonly used browsers, operating systems, and Flash versions based on market penetration. We stay current with releases of new browser versions and test on the latest live versions to report possible bugs in our components.


Android-style image of the author of this page

Sarah is a DoubleClick Studio expert and author of this help page. Help her improve this article by leaving feedback below.

Was this article helpful?