Skip to content
English
  • There are no suggestions because the search field is empty.

Advertiser & campaign's filters

Below is the list of available advertisers'/campaigns' filters. Users can add filters at the Advertiser or Campaign level, from the Filter & Targeting tab in the advertiser/campaign form.

Content


 

Filters table

 

Most Common

   

Filter Name

Description

Instructions

Source (App or Site)

Distinguishes whether the ad space lives inside a mobile native application environment or a standard web browser.

Multi Selection.

Example: Site, App

Device Type

Targets traffic based on the physical hardware form factor of the end-user device, like Desktop, Phone etc.

Multi Selection.

Media Type

Determines core format of eligible ad inventory, breaking traffic into Banner, Video, Native, or Audio.

Multi Selection.

Country

Filters incoming ad requests based on the specific country of the end-user (derived from their IP address or device GPS).

Multi Selection.

Ad Size

Filters layout constraints by standard pixel dimensions to match creative inventory.

Multi Selection.

Example:300x250, 728x90

Geographic & Location Targeting

   

Filter Name

Description

Instructions

Country

Filters incoming ad requests based on the specific country of the end-user (derived from their IP address or device GPS).

Multi Selection.

US State

Limits or targets delivery to specific states within the United States.

Multi Selection.

Zip Code

Provides granular, hyper-local targeting based on specific postal or zip codes.

Comma-separated list of values (zip codes).

In the USA, a 5-digit number

Example: 12658, 98765

Geo Location Type

Determines how the location is identified, such as choosing between GPS data (high precision) or IP address routing.

Multi Selection.

Geo Precision

Sets the number of decimal places for latitude/longitude coordinates. Higher values increase precision.

For example, a precision of 4 gives location accuracy within approximately 11.1 meters.

Number of decimal places.

Example 4.

GPS Accuracy

Sets a threshold (measured in meters) for device-reported GPS signals to filter out low-accuracy or spoofed location data.

The estimated location accuracy in meters, usually <=100

Example: 90

Media & Creative Formats

   

Filter Name

Description

 

Ad Size

Filters layout constraints by standard pixel dimensions to match creative inventory.

Multi Selection.

Example:300x250, 728x90

Media Type

Determines core format of eligible ad inventory, breaking traffic into Banner, Video, Native, or Audio.

Multi Selection.

Video Placement

Specifies where a video ad runs relative to editorial content.

Multi Selection.

Example: In-Stream, Out-stream, In-Banner

Video Mime Type

Filters by media container extensions supported by the publisher's video player.

Multi Selection.

Example: MPEG-4, OGG

Interstitial

Isolates full-screen ad units that appear during natural transition points inside apps or web pages.

Yes/No.

Rewarded Ad

Targets specialized in-app placements where users watch an ad in exchange for in-game rewards/incentives.

Yes/No.

Device & Operating System & Browsers

   

Filter Name

Description

 

Source (App or Site)

Distinguishes whether the ad space lives inside a mobile native application environment or a standard web browser.

Multi Selection.

Example: Site, App

Browser

Targets specific browsers for opening the ad placement.

Multi Selection.

Example: Chrome, Safari, Firefox, Edge

Device Type

Targets traffic based on the physical hardware form factor of the end-user device, like Desktop, Phone, etc.

Multi Selection.

Device Make

Filters traffic by the manufacturer of the device hardware, like Apple, Samsung, etc.

Comma-separated values

Example: Samsung, Apple

Device Model

Narrows targeting down to specific hardware editions.


Comma-separated values

Example: iPhone 15, Galaxy S24

Device Language

Filters by the primary language interface configured in the user's device settings.

Multi Selection.

Operating System (OS)

Targets traffic based on the operating platform running the device (e.g., ).

Multi Selection.

For example: iOS, Android, Windows, macOS

OS Version

Filters by the specific release version of the operating system.

A single value, number.

Example : >= 14

Hardware Version

Filters by the internal hardware build or generation specifications of the processing device.

Comma separated list of values

Example: 16,CE,16 Pro Max,14 Plus

Device ID (IFA)

Targets or excludes specific users using their hardware-level Identifier for Advertisers , IFA value.

IFA single value

Example: AEBE52E7-03EE-455A-B3C4-E57283966238,

39400000-8cf0-11bd-b23e-10b96e40001d

Device IP Range

Filters traffic based on specific corporate, institutional, or proxy IP blocks.

Must be a valid CIDR format.

For example: 198.51.100.0/24

Device/Browser IP

Targets or excludes individual, specific IP addresses from receiving bids.

The user IP. Single value.

Example: 3.3.3.3

Network & Connectivity

   

Filter Name

Description

 

Carrier

Targets users connected via specific cellular network operators.

Single string value

Example: Verizon, AT&T, Vodafone

Carrier MCC-MNC

Uses Mobile Country Code plus Mobile Network Code to accurately target cellular providers globally.

Comma-separated values.

Each value comprised of two numbers separated by '-'

Example: AT&T - USA ==> 310-410

Connection Type

Filters traffic by the active internet connection standard.

Multi Selection.

Example: Wi-Fi, CELL-2G, CELL-3G, 4G, 5G

Inventory Settings

   

Filter Name

Description

 

Impression TAG ID

Filters inventory by the unique tracking tag identifier generated by the ad placement setup.

Single Value.

for example google placement = /1234567/homepage_top

Publisher ID

Identifies and isolates individual publisher entities owning the inventory across multiple apps or sites.

String.

Values separated by commas.

Bid Floor Greater / Lower

Filters based on minimum cost requirements set by publishers, letting campaigns skip overpriced or low-quality supply.

Bid floor value, Number.

Example: >0.5

OM SDK

Filters inventory by support for the Open Measurement framework, required for third-party viewability.

String, one value.

Example: Google

OM Version

Specifies the minimal supported version of the Open Measurement SDK active on the supply side.

A single value, number.

Example: >= 14

SCHAIN Complete

Verifies if an ad request includes a fully populated OpenRTB SupplyChain object for absolute transparency.

Yes/No

Content & Categories

   

Filter Name

Description

 

IAB Category

Utilizes Interactive Advertising Bureau taxonomy tags to align ads with specific content genres.

Multi Selection.

Example: Sports (IAB17), Business(IAB3)

App Store Category

Targets applications based on their app store classification.

Multiple selection.

Example: Gaming, Finance, Health & Fitness

Content Context Type

Identifies the structural nature or category of the immediate digital environment where the ad placement lives.

Multiple selection.

Example: Application, Game, Music

Content Language

Matches the editorial language of the webpage or app text for contextual alignment.

Multiple selection.

Example: English, Spanish

Content Length (sec)

Filters video supply by the exact duration or the maximum allowed length of the video ad asset in seconds.

Seconds.

Example: <120

Privacy, Consent, & User Customization

   

Filter Name

Description

Instructions

Consent

Filters traffic depending on whether valid privacy consent strings (e.g., IAB TCF framework) are present.

Yes/No

COPPA

Ensures regulatory compliance by isolating or excluding traffic marked as child-directed under the Children's Online Privacy Protection Act.

Yes/No

Do Not Track

Respects or filters traffic based on whether the user has enabled the "Do Not Track" (DNT) privacy header in their browser or app.

Yes/No

GDPR Country

Isolates traffic specifically from nations bound by the General Data Protection Regulation (EEA/UK) for privacy compliance.

Yes/No

User Buyer ID

Isolates traffic matching custom cookie IDs synced directly between the exchange bidder and external platforms.

One string value.

Example: cookie value 95e475a8-c8e9-467b-92a1-2325d9502b01

User Custom Data

Allows filtering on proprietary audience attributes or custom tracking variables passed alongside the request stream.

Values separated by commas.



Location Targeting

What is Location Targeting?

Location targeting uses GPS coordinates to include or exclude specific geographic areas from your campaigns. This is perfect for local businesses or region-specific campaigns.

How to Set Up Location Rules:

Step 1: Choose Your Targeting Type

  • Include (In): Show ads only to users within the defined areas
  • Exclude (Not In): Hide ads from users within the defined areas

Step 2: Define Your Geographic Area.

   Enter the following coordinates to create a circular targeting zone:

Setting Description Valid Range
 Latitude  North-South position  -90 to 90 degrees
 Longitude  East-West position  -180 to 180 degrees
 Radius  Coverage area from the   center  point  Minimum 10 meters

Location Targeting Examples:

Example 1: Coffee Shop Promotion

  • Latitude: 40.7128 (New York City)
  • Longitude: -74.0060
  • Radius: 5000 meters (5km)
  • Type: Include (In)
  • Result: Ads show only to users within 5km of this NYC location

Example 2: Competitor Exclusion

  • Latitude: 37.7749 (San Francisco)
  • Longitude: -122.4194
  • Radius: 1000 meters (1km)
  • Type: Exclude (Not In)
  • Result: Ads won't show to users within 1km of this SF location

 

 

Device Hardware Version
Please note that using this filter will prevent any incoming request with missing hardware device data from being sent to your advertiser, which may significantly lower eligible traffic for your campaign.

Match & none-match filter operators
Match and none-match are used when you wish to compare one or more values with the array of values sent in the request.
Match: Selects items where at least one value matches any of the values in the request array.
None Match: Selects items where none of the values match those in the request array.