• Admin > Sites > New Site


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.

Creating a Whitelist

A whitelist helps publishers define who can use their data. Sizmek works with publishers to maintain a list of all vendors (partners) and authorized hostnames that are allowed to track 3rd party events for ads served on a publisher's site. As a publisher, you can use this list to create and manage a whitelist for your own site.

By default, the whitelist allows all vendors to track 3rd party events. However, you can choose to whitelist a specific set of vendors, and only allow them to track 3rd party events. In addition, you can add/remove vendors from the whitelist at any time.




  • Sizmek URLs are always whitelisted; therefore, these URLs are excluded from the list of vendors.

  • The vendors list is maintained in the Sizmek platform on the Partners tab.

How Does it Work?

Whitelist validation occurs when a placement ad is created/updated and trafficked in the Sizmek platform. Sizmek verifies that the 3rd party URLs (for example, impression tracking, click tracking, or custom scripts) that are not permitted by a specific publisher are not fired by the creative when the ad serves on that publisher's site. Note that Sizmek does not block the ad, but blocks the specific URL that did not pass validation. An indication appears on the placement ad when a URL is blocked.


Adding Exceptions to a Whitelist

In some cases, a publisher may allow exceptions to their general rules and permit specific accounts and advertisers to use any of the vendors on the approved list. Adding the account and advertiser to the exceptions list exempts them from the whitelist.


Allowing Access to Raw Data Feed Reports

A publisher can determine what raw level data is extracted and passed to the raw data feed and path to conversion reports. Accounts and advertisers inherit the privacy settings from the site; however, you can modify these fields for each entity.

In some cases, a publisher might want to override their global policies regarding raw level data, and permit specific accounts and advertisers to receive additional information in their reports.

For example, a publisher could decide to allow a specific account and advertiser to receive user identifiers in their reports.

Adding the account and advertiser to the exceptions list, and selecting a policy exempts them from the global policy.

Options include the following:

  • Allow: This is the default setting. All events served on this site are extracted and passed to the relevant reports.

  • Remove User Identifiers Only: All events are extracted and passed to the reports except for UserID, AdvertiserDeviceID, and AdvertiserDeviceType, which are empty.

  • Allow Click Events Only: With the exception of click events, no other data served on this site is extracted and passed to the reports.

  • Do Not Allow: Events served on this site are not extracted and passed to the reports.

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