Overview

This section allows you to control all traffic scanners and their application to all SSP endpoints.

You can manage the scanners’ application to every endpoint from one place.

 

To open the section, select ‘Scanners’ in the upper-right corner menu:

 

In the Scanners section, you will see the list of scanners available on the platform:

 


Click on a scanner to expand its settings. You will see the settings on the left side, and on the right side, there are lists of companies and endpoints for which the scanner is applied at the moment:

 

 

 

Depending on a scanner, the left side contains the scanner’s general settings: user’s account credentials, email, etc.

Note: in the case of Protected Media Scanner, there are two options: Personal account and SmartHub account.

Personal account requires setting credentials (Account ID, Key, etc. - you can set it with Gmail Service account).

Now, after establishing a partnership between PM and SmartHub, you will have the opportunity to activate the scanner using your SmartHub account. SmartHub account doesn’t require additional settings and is configured automatically by built-in tools.

The right side contains two tabs, depending on a scanner:

SSP endpoints to Scan and DSP endpoints to apply Block.

 

'SSP endpoints to Scan' allows you to select specific SSP endpoints whose traffic should be scanned:

Endpoints are initially grouped by companies. Click on a company to expand its endpoints list. Tick the checkbox of each endpoint you want to scan. 

Note: In the picture above, you see that the Protected Media scanner requires to set the default traffic quality for those endpoints for which the scanner is not active.

Clean Traffic - we will consider traffic from this endpoint as high-quality and send it to all DSPs.

Fraud traffic - we will consider traffic from this endpoint as low-quality and send it just to DSPs with valid fraud of 100%.

 

'DSP endpoints to apply Block' allows you to select the DSP endpoints whose activity requires some traffic filtering or throttling based on fraudulency. So it can be blocked if a certain percentage of malicious advertising is detected.

Note: Protected Media allows to set acceptable percent of suspicious and fraudulent IVT, and Smarthub will not send to that DSP the requests from SSPs with the level of suspicious/fraud IVT higher than specified.

Endpoints are initially grouped by companies. Click on a company to expand its endpoints list. Tick the checkbox of each endpoint you want to scan. Set the suspicious and fraud IVT percentage of creatives after which the endpoints should be blocked.

 

Scanners Settings

TMT Scanner

 

TMT is a demand scanner that scans ads to detect malicious creatives.

When receiving a response, we check whether this CrID is in the TMT whitelists. If so, we send a response to the SSP. If not, we send it to the scan.

TMT sends reports with results on the CrIDs checking (both positive and negative) every hour. When a new CrID appears, it will not be sent to the SSP until it appears in reports.

Upon initial connection of TMT (partner), there will be no bidding within an hour, until reports received.

 

Note: TMT can only scan banner or native creatives, not video creatives.

 

How to set up:

TMT provides following credentials to establish connection:

New Key: d81f28****************c07fcdf8a

Endpoint: https://[xxxxx].api.themediatrust.com/v2/?  (for example, https://a094x.api.themediatrust.com/v2/?)

 

Settings:

API key - key hash value provided by TMT.

API EP - the [xxxxx] part of the endpoint link provided by TMT.

Scans Daily Limit - the maximum number of creatives that can be sent to scan within one day (the day begins at 00:00 UTC).

If value = 0, and scans have already been done before, then only CRIDS that were previously scanned by TMT will proceed trading. New ones will not be sent to the scan.

If value = 0, and there were no scans before (TMT was just connected recently), then we will not trade with SSP endpoints that have TMT scanner applied.

One tag scans limit - This value determines how many times one CRID may be scanned during the period specified in the 'Remove tag period (hours)' field.

Remove tag period (hours) - The frequency of updating the tables with the results of the TMT scan. After this amount of time, all SSP endpoints with the TMT scanner activated will stop trading until new TMT reports on CRIDS appear.


 

Forensiq scanner

 

Forensiq is a supply-side scanner that detects fraud traffic. However, it scans traffic using the link in a bid response, and the scan occurs during the impression.

 

How to set up:

To enable scanning, only one parameter is required:

User ID - An identifier provided by Forensiq (Org ID).

 

You may check if the scanner working at the moment: open the Supply side in the Main section, open an endpoint, and click 'Valid Response Sample'. If you see a 'new.fqtag.com' part in the response, that means the scanner is working.

If you haven't found such part, try another response sample.


 

Protected Media

 

Protected Media is a supply-side scanner that detects fraud traffic. However, it scans traffic using the link in a bid response. The scan occurs during the impression.

 

Pre-bid

In this case, Protected Media provides two values to establish connection: Customer PID, Customer Key, Host and Port to connect to, and the Scan limit:

Scan limit means the daily limit of scans. If set to 0, the scanner will scan all traffic.

The rest of the settings should be provided by Protected Media.

 

Post-bid

Protected Media usually provides only one value to establish connection: PID (Partner ID).

You have to set up the rest of the fields, for this purpose you may use a service account on Gmail.

Find instructions on how to create a Gmail service account here.

 

To ensure the scanner is working, open the Supply side in the Main section. Then open an endpoint and click 'Valid Response Sample'. If you see a 'ad-score.com' part inside the response, that means the scanner is working.

 

If found, that means the Protected Media is connected, traffic is being scanned.

Note: At the moment, we are not processing scan results on the server side. You yourself can manage traffic based on reports.

 

Pixalate scanner

Pixalate is a service for the detection and filtration of sophisticated invalid traffic (SIVT) across desktop and mobile web, mobile in-app. 

Despite the fact that Pixalate is a supply-side scanner, it scans traffic using the link in the response. The scan occurs during the impression.

Traffic types that can be scanned: Banner, Native, Video.

Pre-bid

 

  • Link - Link to FTP server with Pixalate reports
  • Login - Login for authorization
  • Password - Password for authorization

Post-bid

 

How to set up:

  1. Create an account in Pixalate.
  2. Select traffic types to scan (one or more) on your platform.
  3. Generate a pixel. There may be two types of pixel: <script> or img.
    The script link differs from img by a separator (';') and has an extension '.js'. In the img link, the separator will be &.

 

For example:

Script link:

https://q.adrta.com/s/wmg/aa.js?cb=[CB]#wmg;paid=sh;avid=[ADV];caid=[CID];plid=[CRID];publisherId=[PID];siteId=[SITE_ID];priceBid=[BID_PRICE];pricePaid=[CLEAR_PRICE];lineItemId=[LI_ID];kv1=[SIZE];kv2=[PAGE_URL];kv3=[UID];kv4=[UIP];kv7=[SELL_ID];kv11=[IMP_ID];kv12=[TAG_ID];kv15=[REGION];kv16=[LAT];kv17=[LON];kv18=[BUNDLE];kv19=[DEVICE_ID];kv23=[CARRIER];kv28=[DEVICE_MODEL];kv25=[APP_NAME];kv26=[OS];kv27=[UA];kv9=[C_LENGTH];kv10=[ISP];kv13=[CONTENT_ID];kv14=[MRAID_V];kv24=[TYPE]

 

img:

https://adrta.com/i?clid=vs&paid=ADK&dvid=v&avid=[ADV]&plid=[CRID]&siteId=[SITE_ID]&publisherId=[PID]&kv1=[SIZE]&kv2=[PAGE_URL]&kv4=[UIP]&kv11=[IMP_ID]&kv12=[TAG_ID]&kv13=[CONTENT_ID]&kv16=[LAT]&kv17=[LON]&kv18=[BUNDLE]&kv19=[DEVICE_ID]&kv20=[DEVICE_ID]&kv21=[DEVICE_ID]&kv23=[CARRIER]&kv28=[DEVICE_MODEL]&kv25=[APP_NAME]&kv26=[OS]&kv27=[UA]&kv9=[C_LENGTH]&kv24=[TYPE

 

  1. Copy the script/img link.
    Note: We recommend using the IMG pixel, as the script type can not scan video traffic and may work worse with the native type of traffic.

  2. Open Scanners section, find Pixalate Scanner settings and switch it on:
  3. Select the traffic types you want to scan.
  4. Paste the script link to the ‘Tag’ field in Pixalate Scanner settings.
    The <script> and other HTML tag keywords are not necessary. Just paste the link from the body of the tag.
    For example, you may have following tracking tag code:
    <script type='text/javascript' id='pixelscript' src='https://adrta.com/s/wmg/aa.js?cb=[CB]#wmg;paid=sh;avid=[ADV];caid=[CID];plid=[CRID];publisherId=[PID];siteId=[SITE_ID];priceBid=[BID_PRICE];pricePaid=[CLEAR_PRICE];lineItemId=[LI_ID]'></script>
    The part you need is enclosed within ‘’ quotes inside of the body of the tag:
    https://adrta.com/s/wmg/aa.js?cb=[CB]#wmg;paid=sh;avid=[ADV];caid=[CID];plid=[CRID];publisherId=[PID];siteId=[SITE_ID];priceBid=[BID_PRICE];pricePaid=[CLEAR_PRICE];lineItemId=[LI_ID]
    The tag link may contain macros specified in such format: cb=[CB].
    Remove all the macros from the tag link (macros from the tag pasted will not work, as we don’t support some of the macros generated on the Pixalate side).
    For example, having the source code of the form:
    https://adrta.com/s/wmg/aa.js?cb=[CB]#wmg;paid=sh;avid=[ADV];caid=[CID];plid=[CRID];publisherId=[PID];siteId=[SITE_ID];priceBid=[BID_PRICE];pricePaid=[CLEAR_PRICE];lineItemId=[LI_ID]
    leave only the following part:
    https://adrta.com/s/wmg/aa.js
  5. Add macros if needed. To do so, click on Macros field and click on each macro you need:

    Macros you have selected are displayed on the top and added to the link automatically.

Note: There are no mandatory macros, but we strongly recommend using [CB] macro to ensure the proper work of the pixel.

 

  1. After finished, click ‘Save’.

 

We will automatically define the type of the tag (img or script) and add the link to the responses (to adm). The scan takes place at the moment of impression.


 

To ensure the scanner is working, open the Supply side in the Main section. Then open an endpoint and click 'Valid Response Sample'. Find the adm field and look for adrta.com inside the response, which means the scanner is working.

 

In addition to the reports in the "Scanners statistics" section, you can also view statistics on the admin page on the Pixalate website.

 

GeoEdge

GeoEdge is a demand scanner that helps publishers to stop malicious and low-quality ads from reaching their audience. When sending a response to the SSP, GeoEdge wraps the content of adm with <header> and <footer> tags. If the creative contains a redirect inside, these tags will not allow it to work, but will send an alert about an attempt. All creatives containing redirects can be seen in the GeoEdge Admin panel.
 

  1. GeoEdge provides you with two files: header.txt and footer.txt.
  2. To use the scanner, go to Settings -> GeoEdge Scanner and switch it “On”.
  3. Set tag header (from GeoEdge header.txt file) and footer (from GeoEdge footer.txt file) in the appropriate fields. 

  1. Click “Save” button.

  2. Select endpoints to scan:



 

 

Statistics

You can view statistics on the use and performance of scanners. To do so, open Statistics->Scanners Statistics, or click ‘Go to Report’ in the Scanners section.

Note: Statistics are available only if at least one scanner is enabled.

 

To see the statistics you need, select the date and the scanner. Select the report type (Blocked sources, blocked IPs, etc.), if available for the selected scanner. Click [Generate].

 

TMT

For this scanner, you can generate reports of the following types:

  • Blocked domains
  • Blocked creatives

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • DSP Name – the name of the endpoint.
  • Ad Format – scanned ad format (Banner, Native).
  • Blocked domain

 

As a result of the scan, those domains or creatives detected as malicious will be blocked - they will be displayed in the corresponding column.

 

Forensiq

 

Statistics for Forensiq scanners contain the following fields:

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • SSP Name - endpoint name.
  • Ad Format - which ad format was scanned.
  • Impressions - the number of impressions that occurred at the endpoint.
  • Scans - the number of scans performed.

 

Forensiq statistics will only show the numbers of impressions and scans.

Currently, we do not automatically block anything using the data from Forensiq reports. They provide partners with statistics within their admin panel, so you can decide by yourself whether to block some traffic or not.

Protected Media

Pre-bid

 

You will see the following data:

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • Ad Format – Banner, Video, Native, Push, etc.
  • SSP Name – the name of SSP endpoint
  • Publisher ID
  • Bundle / Domain – bundle or domain from which traffic was scanned.
  • Suspicious IVT – the percentage of invalid traffic considered as suspicious.

Note: This field is available only for Protected Media post-bid scanner.

  • Fraud IVT – the percentage of invalid traffic that is considered fraudulent.

As a result of the scan, you will see the level of suspicious and fraudulent traffic (as a percentage of all impressions) for each source and you can decide whether to block any of that resources.


 

Post-bid

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • SSP Name - endpoint name.
  • Ad Format - which ad format was scanned.
  • Publisher ID
  • Bundle /Domain
  • Scans – the number of scans performed.
  • Fraud – percent of traffic identified as fraudulent.

 

As a result of the scan, you will see the level of fraudulent traffic (as a percentage of all impressions) for each source and you can decide whether to block any of that resources.

Pixalate

Pre-bid

For this scanner, you can generate reports of the following types:

  • Blocked IPs – user IP addresses blocked as a result of scanning
  • Blocked devices – devices blocked (by IFA) as a result of scanning

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • SSP Name - endpoint name.
  • Blocked IPs - IP addresses blocked as a result of scanning.

 

As a result of the scan, those IPs or devices detected as malicious will be blocked - they will be displayed in the corresponding column.

 

Post-bid

 

 

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • SSP Name - endpoint name
  • Ad Format
  • Impressions - the number of impressions that occurred.
  • Scanned Impressions – the number of scans performed.

 

Note: Pixalate post-bid scanner statistics will only show the numbers of impressions and scans.

Currently, we do not take any action using the data from this scanner statistics. They provide partners with statistics within their admin panel, so you can decide by yourself whether to block some traffic or not.

 

GeoEdge

 

  • Date – a date for which data is aggregated.
  • ID – endpoint identifier.
  • DSP Name – endpoint name.
  • Ad Format – scanned ad format
  • Impressions - the number of impressions that occurred.
  • Scans – the number of scans performed.

 

Note: GeoEdge scanner statistics will only show the numbers of impressions and scans.

Currently, we do not take any action using the data from this scanner statistics. They provide partners with statistics within their admin panel, so you can decide by yourself whether to block some traffic or not.