Skip to main content
Skip table of contents

Campaign Parameters

The Campaign Parameters section within Forecaster aims to mirror Zeta DSP's Campaign Targeting, but only supports a subset of all available options. Navigate to the Channels tab and select the channels your campaign will deliver on. Channels are grouped via Display, Mobile, and Video

Use the Channels feature to study how restricting your campaign to particular channels affects the audience and the campaign's ability to show them ads. 

  • When you first encounter the Channels feature, nothing is checked. This means that the graph and numbers are based on delivery to all channels.

  • Once you click a single channel, this notion changes and as long as even one is checked, the DSP indicates delivery to only those channels. 

Sometimes you may see the graph disappear. This means that the DSP simply has too little data available for the choices you made. In this case, re-think your plan and remove some of the channels and/or restrictions.

In order to determine if there is adequate inventory, you can apply specific channels, targeting, and goal-type restrictions for the duration of your campaign. Additionally, there is an option to implement Cross-Device.

Cross-Device Options

  • When set to DSP HOUSEHOLD, it will forecast avails based on using the Cross-Device in Audience Targeting.

  • Generally increases avails 20-30% when using the DSP Household Option.

  • For Best Results. use this Feature for Mobile App and CTV Delivery Channels when forecasting Audience Targeting.

Available Channels

Channel

Description

Display - Standard

Typical static impression opportunities in a web browser running on a desktop computer. Pixel sizes: 300x250, 728x90, 160x600.

Display - Special

Static impression opportunities in a web browser running on a desktop computer at the 300x600 pixel size.

Display - Expandable

Static impression opportunities in a web browser running on a desktop computer for ads whose size may expand as required.

Mobile Display: In-App

Static impression opportunities inside a mobile device application.

  • Smartphone sizes: 300x250, 320x50

  • Tablet sizes: 300x250, 160x600, 728x90

Mobile Display: Web

Static impression opportunities in a web browser running on a mobile device.

Mobile Display: Interstitial

Interstitial impression opportunities on a mobile device whether in an app or browser. Pixel sizes: 320x480, 768x1024
(An interstitial is a full-screen ad that covers the interface of its host application.)

Desktop Video

Video served on desktop sites. Make sure to consider Video targeting when using this channel. Select the Include only VPAID requests to filter only IAB-verified VPAID inventory.

Mobile Video

Video served on mobile sites. Make sure to consider Video targeting when using this channel.

CTV Video

Video served on connected television devices. Make sure to consider Video targeting when using this channel.

Note that this channel is based on device type 3, 7 from OpenRTB spec

Goals

Navigate to the Goals tab to apply Viewability and/or Video Completion goals to your forecast. These goals only apply to Zeta's post-bid products.

If you'd like to apply Pre-Bid targeting, select Traffic Quality under Targeting.

Goal 

Description

Viewability

Viewability refers to whether or not an Ad is given the chance to be seen (“chance” is currently defined by the MRC as 50% of pixels in-view for one second for display, or for two seconds for video).

Enter the percentage of Ads that should be viewable.The maximum Viewability Rate the DSP allows is 80%. Careful analysis of past Zeta campaigns has revealed that rates above this number are impractical in terms of cost.

Video Completion

Percentage of visitors who watched a video ad to completion. 

 

Best Practices

If you are using a post-bid Viewability goal at any level, make sure to use the Viewability Goal in the Forecaster. This goal can have a significant effect on the amount of inventory available to a campaign or line item.

Targeting

Navigate to the Targeting tab and click on + Add Targeting to apply restrictions relevant to your campaign.

Restriction

Description

Ads.txt

Use Ads.txt targeting to ensure you are bidding on inventory authorized by a publisher.

App

Enable App targeting for a placement in particular applications, in both the iOS and Android environments.

Audience

Identify and show ads to audiences based on data collected from internal and third-party sources.

Browser

Target or exclude web browsers such as Chrome, Safari, Firefox, etc., including mobile device browsers.

Content Categories

Identify and show ads to audiences based on data collected from Peer39's proprietary content categories.

Devices

Devices enable targeting or exclusion of particular devices, including by operating system of mobile devices.

Fold

Target based on the position of the Ad on the screen when the viewer first encounters it.

Inventory

Target by Inventory to permit the inclusion or exclusion of particular Ad exchange marketplaces.

Language

Target web and mobile users who have their browsers set to one or more particular languages.

Location

Target by Location (also known as geofencing or geo-targeting) to restrict where your Ads are shown.

New User

Enable New User targeting to target only those that Zeta has not yet delivered pixels to or recorded attributes for previously.

Sites

Include or exclude particular sites that may display your ads. 

The Forecaster can support a site list of 150 sites. Submitting a site list beyond this value can cause the Forecaster to stop working and the query will return no results.

Traffic Quality

Apply Traffic Quality when using Peer39, Integral Ad Science (IAS) or Double Verify data to avoid displaying ads alongside certain undesirable categories of content and more.

Video

Enable targeting based on the video Ad placement opportunities and characteristics.

Ad Sizes

View inventory for a particular Ad Size.

When entering Ad Sizes into the Forecaster you must use the following format and separate the ad sizes by a comma - 728x90,160x600,300x250

Examples of entering in the wrong format are noted below:

728x90,
160x600,
300x250

and

728x90
160x600
300x250

Frequency Cap

Set a Frequency Cap to limit the impressions delivered within a given number of hours. 

Zeta suggests avoiding Frequency caps as it makes it much more difficult for the Zeta AI to find the optimal device for conversion.

Best Practices

Include Ad Sizes in Targeting:

  • Make sure to input all of the planned targeting settings for your campaign into the Forecaster. If using HTML or Image ads, utilize the "Ad Size" restriction. The amount of available inventory will change depending on which ad sizes are being used for the campaign.

    • Also note, when entering Ad Sizes into the Forecaster you must use the following format and separate the ad sizes by a comma - Correct WAY - 728x90,160x600,300x250

      Examples of entering in the wrong format are noted below:

      728x90,
      160x600,
      300x250

      and

      728x90
      160x600
      300x250

  • For example, as of July 6th, 2018, the Forecaster sees 458,000,000 avails for the whole United States. However, if a US-targeted campaign uses only 300x250 ads, the avails pool will only be 154,400,000 - just 34% of the total possible inventory.

Video Ads:

  • If you select any video channel, make sure to consider Video Duration targeting.

Location Targeting:

  • To input DMAs into the Forecaster, you can either use the Nielsen DMA Codes or the name of the specific city that defines the DMA (i.e: Denver). 

  • The DMA codes are available in the Resource Materials section below. 

Language Targeting:

  • Language targeting requires the use of the 2 letter ISO Language Code.

  • The Language Codes are available in the Resource Materials section below. 

Sites Targeting:

  • For checking inventory for a list of Sites using the "Domains" restriction, the easiest way to upload a site list is to upload a plain text file (.txt) with no headers and have all site URLs separated by line breaks.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.