• Admin > Sites > New Site

The following sections describe the main Setup fields for a new site.


Tag Settings





Determines whether the tag will be generated with a secure protocol (HTTPS) or non-secure protocol (HTTP).

  • For HTML5 and In-Stream ads, when a tag is generated with a secure protocol, the ad request and all subsequent Sizmek ad server calls will be over a secure protocol, regardless of whether the tag is placed on a secure page or a non-secure page.

  • For Adobe Flash Rich Media ads, because of Flash framework limitations, if a secure tag is placed on a non-secure page, the ad request is sent over a secure protocol; however, the ad's assets will use a non-secure protocol.

When generating a secure tag, make sure that you check that all other URLs, for example, 3rd party trackers, used by the ad are using the secure protocol.

Support Create iFrame

Adds the Create iFrame option to the publish settings for placements to run on this site. If you don't select this check box, only Script, iFrame, and Auto Detect options are enabled.

Tag Type

Enables you to select default tag type for placements a in this site:

  • Script: Generates code for serving ads by using a script.

  • iFrame: Serves the ads to an iFrame in the web page.

  • Auto Detect: Sizmek automatically determines whether the ad is being served into an iFrame, and then serves the ad appropriately. Please note that with this option, when iFrames are used to serve content, Auto Detect will identify the ad as an iFrame, and expand it beyond the content's boundaries.

  • Create iFrame: Creates the iFrame to which the ads will be served.

Escape NoScript Tags

Relevant for the Create iFrame option. For the NoScript part of the code, the tag URL (variable) will not be escaped.

Referring URL Token

Adds the Referring URL Token to the generated placement tags for the vURL (verification/page URL) parameter. The token will be replaced by the publisher with the Referring URL.

Tracking Placement

Tracking Tag Type

Code generated for tracking placements includes URLs for tracking impressions and clicks. This option determines whether to generate these URLs within IMG tags (required by certain ad servers) instead of within regular or script tags.

Impression Tracker Response

Determines whether for impression calls of tracking placements, the site requires an HTTP response status of 200 OK, Content-length: 0

Tracking & Targeting




Publisher Custom Parameter

Used for analytics purposes. Enables a custom parameter to be sent to Sizmek Ad Suite for every impression event. Data that is received is available in cookie-level data and custom reports.

Publisher Keywords Data

Enables you to collect publisher keyword data for this site.

Publisher keyword data allows the Sizmek Ad Suite platform to receive information about a search term that users have used in the publisher’s site, or about any other information the publisher has about the user or their preference. This information can be used for targeting audiences.

This option is selected by default for any campaign that is serving to this site.

Delimiters for Parsing Site Keywords

Enables you to override server default delimiters (|&) with user-provided delimiters. Enter all required delimiters without any spacing (for example, #$@&).


Note: Only standard U.S. ASCII characters are supported.

Line ID

A dynamic token that allows publishers to pass data to Sizmek on the ad request. Sizmek will use its value on 3rd party tracking URLs that Sizmek fires on impressions or clicks. This allows publishers to leverage URL tokens to transfer data to third parties that track the campaign.

Cache Busting Token

The cache busting token is used by the ad server to track impressions and clicks. If you did not select a publisher ad server, or need to change the existing token, enter it here. The token can be obtained from the publisher's ad server support.

The Random Number option allows Sizmek to include a random cache busting token in the generated code automatically. This is typically used for sites without ad servers.

Impression Tracking Token

Enables you to add the URL for tracking impressions by the selected ad server. The URL can be obtained from the publisher's ad server support.

Click Tracking Token

Enables you to add the URL for tracking clicks by the selected ad server. The URL can be obtained from the publisher's ad server support.

Ad Request

Enables the collection of ad requests on the site.

Zipcode Token/Country Token

Enables you to add a token with a country code/zip code on the publisher's site. The values are added to the tag during ad serving, and are used to override the Sizmek geo information for the impression.


Site X is sending a request for an ad, and Sizmek analyzes that the impression is from Germany. Because the user on the site is a registered user, site X knows that this user is from San Francisco. In this case, Sizmek should serve versions that match the publisher's geo data, San Francisco, and not theSizmek detected geo settings.

Inheritance Settings

You can also set these tokens on the Placement tag level.

Mobile Tokens


Important: Device tokens, for example, Device Advertising ID, must be populated by the publisher. Sizmek is not responsible for validating the data that publishers pass, or do not pass, through these tokens.

Mobile app tagging allows you to track information on mobile apps. This information can be used for the following purposes:

  • Sizmek can collect conversion information and provide more accurate data for frequency and conversion reporting.

  • Device IDs can be passed to 3rd party tags.

These tokens do not automatically capture the corresponding device IDs. Publishers must configure their ad server to pass the correct values into the applicable tokens. Before implementing these tokens, Sizmek recommends that the client contact the publishers on the media plan directly to confirm that they will provide this data.

After configuration, the generated publisher placement tags and tracking pixels will include dedicated mobile parameters, which may be replaced in real-time by the publisher ad server technology.

How Does it Work?

Each time Sizmek gets a call with a device ID token, Sizmek checks whether a corresponding Sizmek user ID exists. We use the Sizmek user ID as the unique identifier. If a corresponding Sizmek user ID does not exist, we store it for the next time the device ID is received.

Each token appears as a unique value in the tag.


Ad Tag Placeholder



Device Advertising ID


Unique, anonymous ID that ensures positive ID of user.

It is a best practice to use the Device Advertising ID, even if you do not use any other tokens.

Google Advertising ID


Google Advertising ID

Sizmek uses this ID, based on availability on the publisher side, to determine the source of impressions.

iOS Advertising ID Raw


Raw iOS Apple identifier

Sizmek uses this ID, based on availability on the publisher side, to determine the source of impressions.

iOS Advertising ID SH1


SH1 hash of the Apple identifier

Sizmek uses this ID, based on availability on the publisher side, to determine the source of impressions.

iOS Advertising ID SH2


SH2 hash of the Apple identifier

Sizmekuses this ID, based on availability on the publisher side, to determine the source of impressions.

iOS Advertising ID MD5


MD5 hash of the Apple identifier

Sizmek uses this ID, based on availability on the publisher side, to determine the source of impressions.

Windows Advertising ID


Windows Advertising ID

Sizmek uses this ID, based on availability on the publisher side, to determine the source of impressions.


Note: You can add the following tokens manually in Sizmek Ad Suite:

  • ebappid=$$[%Publisher_Macro_AppID%]

  • ebappname=$$[%Publisher_Macro_AppName%]

Then you can use them in 3rd party tracking URLs:[%tp_appid%]&app_name=[%tp_appname%]. Note that [%tp_appid%] and [%tp_appname%] are unescaped formats.

Ad Delivery




Avoid Document.Write

Generates placement tags when client JavaScript code does not contain the document.write command.

Minimum Z- Index

The default minimum Z-index for the site or section. Determines the ad’s position in the order of layers on the page. For example, type 11000 for the ad to appear in front of the page that has a value of 10000.

AddinEye File Location

The location of the addineyeV2.html file. This file is usually located in the root directory of the site domain.

Disable Auto-Expand Panels

The system will not auto-expand ads. This option is appropriate for cookieless environments.

Enable the Dynamic Expansion Direction

Enables the system to automatically detect the direction in which HTML5 expandable ads should expand during serving. This is required in a programmatic environment, where the location of the ad that will be displayed is not known in advance. For example, if an expandable ad that is set to expand downwards is served to a placement at the bottom of a web page, the system identifies this and changes the behavior of the expandable panel, ensuring that the panel expands upwards. Only new placements inherit this setting from the site.

  • If you select this check box, the system creates placements for this site that instruct HTML5 expandable ads to automatically detect the best direction in which to expand when the ad is served. Selecting this check box overrides the expansion direction that was set in the ad creative.

  • If you do not select this check box, HTML5 expandable ads expand in the predefined direction that was set for the creative. This is the default setting.

Enable CORS on Response Headers

For sites that require Cross-Origin Resource Sharing (CORS) response headers to be provided in the server response.

Filter Out Unknown User Agent Calls

Determines whether the ad server should accept impression calls with unknown or empty user agents from this site. Some sites are not capable of passing user agents on the impression tracking requests to the server, or they pass non-standard user agents. This option helps avoid filtering out empty or non-standard user agent impression requests.

Server-Side Ad Insertion

For sites that deliver ads to a user's device through the publisher's server. When a site is using Server-Side Ad Insertion (SSAI), interactions are sent to the Sizmek platform in one of the following ways:

  • Direct Client-initiated: Ad request comes from a server and not from a specific device, but all of the interactions and the impressions come from the user's device.

  • Indirect Client-initiated: The device transmits a signal back to the publisher server. The publisher server redirects the information to the Sizmek server.

  • Server-initiated: If the device is unable to fire beacon events, the publisher server might infer ad event activity, and fire the events on behalf of the device.


VPAID Support

Instructs the platform to convert VAST linear ads into VPAID units when served on sites that support Flash VPAID or HTML5 VPAID. By serving the VPAID units on certified sites, Sizmek can add either their own or 3rd party Verification and Viewability scripts, without the need for a creative developer to produce a VPAID creative. For sites that do not support VPAID, the linear VAST video ads are served as is.

For more information , see Build an In-Stream VAST Enhanced Ad in the Sizmek Ad Suite.


In-App SDK

SDK on the mobile app that serves the ad. The value that you select is passed to placements. You can modify the value at the placement level.

Privacy & Publisher Whitelist




Publisher Whitelist


Note: This feature is protected by the following permission:

  • Edit Approved 3rd Party Vendors for Sites

One of the concerns that publishers have today is how to protect their data and how to set rules that govern how their data can be used. Some publishers want to limit an agency's ability to target and create segments that are based on publisher data, or limit access to raw level data from privacy regulations. For more information about working with publisher whitelists, see Publisher Data Policies (Data Governance)


Sizmek clients must comply with all applicable laws when using the Sizmek Ad Suite.

By selecting this check box, you confirm that this site complies with the U.S. Children’s Online Privacy Protection Act (COPPA), according to which cookies are not permitted. When a placement's site is COPPA-compliant, the placement setting inherits the privacy setting from the site.

This check box is permission-protected and only the Sizmek Site Certification team can select it.


Note: When you select this check box, the Disable Cookies check box is disabled.

Disable Cookies

For new campaigns, placements, and advertisers on this site, cookies and their tracking capabilities are disabled by default.


Note: If you select this check box, some delivery group serving logic capabilities, (such as sequencing, frequency capping, retargeting, and state-based rotation) and reporting capabilities (such as counting unique impressions, and path to conversion) won't work anymore.






Used as a filter for the site's placement list. When a user sets up a placement, the sites within the user's market are displayed first.

Email Notifications Time Zone

Determines the time zone to use when sending email notifications.

In-Stream Rules


Enables the certification manager to select the required In-Stream template to use in the site, which can be used for all sections or for a specific section in the site.

After selecting a template, changes can be made to the template variables. Changes made to variables on the site level override the definitions on the template level and on the ad level. When master ads are attached to the site's placements, the VAST XML is created according to the template logic and then applied to the placement ads.

Publisher Reports





Reports include standard delivery and interaction metrics in the placement level, in addition to delivery rate metrics (delivery rate, ordered impressions, expected impressions) of the placement (if the media cost setup was done on the placement), or of the package (if the media cost setup was done on the package).

For more information about Publisher reports, see Publisher Report Fields.

Email Address List

Determines the email recipients for the selected reports. For multiple recipients, email addresses must be separated by commas.



  • Sizmek Support can subscribe a site to one or both of the automatic daily reports. These reports include data from the campaign lifetime date range for all live campaigns. Every row in the report includes data for the complete report date range. A campaign is considered live if one of the following conditions is met:

    • The end date for a placement is the current date or a future date.

    • A placement is still delivering but the end date has passed. In this case, the placement status changes to live when it passes the 1000 impression threshold within the last 24 hours.

  • The time zone for the reports is UTC.

  • Calculations refer to ordered impressions.


Enables a site to connect to an account. When a site is connected to an account and placements are published, site users from the account can perform actions such as, view their relevant campaigns and generate tags.


Note: Generating reports is available only if the site is managing the campaign in the account.



Contacts enable campaign participants to receive relevant email notifications about the campaign. For more information, see Campaign Contacts and Email Notifications.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request