Targeting

In Adfox, targeting can be set up at different levels. Banner-level targeting takes priority over placement-level and campaign-level settings.

Let's say your entire campaign is geo-targeted to Russia, but for a couple of banners you've enabled redefined targeting to only some regions within Russia. In this case, banners with redefined targeting appear only in the selected regions, while all other banners follow the campaign settings and show across Russia.

To set targeting parameters of an:

  1. In the Campaigns tab, select an ad campaign or find one using the search bar.

  2. Next to the campaign name, click  → Targeting or select a campaign and go to Targeting.

  3. In the window that opens, add one or multiple targeting criteria.

  4. Make changes and click Save.

For a site, section, or placement.

  1. In the Campaigns tab, select an ad campaign or find one using the search bar.

  2. Go to the Placement tab and click the placement name in the row for the required level.

  3. In the window that opens, the Targeting profile field can have the following values:

    • No restrictions: Targeting isn't configured.
    • Not overridden: Targeting settings are inherited from the campaign level.
    • Custom: Custom targeting settings apply at the placement level.

    To set up targeting for the selected placement, choose Custom and click .

  4. In the window that opens, select the targeting type, enable the Settings redefined option, and configure the appropriate settings.

  5. Make changes and click Change.

  1. In the Campaigns tab, select an ad campaign or find one using the search bar.

  2. Go to the Banners tab, find the banner in the list, and click Targeting.

  3. In the window that opens, add one or multiple targeting criteria.

  4. Make changes and click Save.

If you frequently reuse the same targeting settings, consider targeting profiles.

User labeling

Adfox uses special Yandex IDs, including cookie files, to identify user interests and fine-tune targeting based on frequency, demographics, and Yandex Audience segments. These IDs can be used effectively with:

Advanced Matching

Advanced Matching is a Yandex Metrica technology that helps identify users on a site, even when cross-site cookies are restricted in browsers like Safari and Mozilla Firefox. It uses the information that users themselves enter when placing an order, registering, or subscribing to a newsletter. This data is hashed in accordance with ISO-27001 standards and sent to Yandex Metrica in an anonymized format. By analyzing the aggregated information, you can target ads more precisely and increase your ad revenue.

If your site collects data, you can use automatic or manual data transfer to Advanced Matching to better tailor your ads to user interests and increase your site's revenue.

Transfer of IDs via the API

Adfox supports the transfer of custom IDs via the API in the GET parameter of the request. This technology is most commonly used for targeting and setting up impression frequency in mobile apps. The following IDs are used:

Platform

ID

Engine parameter

Format

iOS (iPhone, iPad)

IDFA

&idfa=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

AEBE52E7-03EE-455A-B3C4-E57283966239

iOS (iPhone, iPad)

IDFV

&ifv=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

5A7D2D91-E1F2-4B3A-9C8D-1F6E4A2B5C3D

Android (including Android TVs)

GAID

&google_aid=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

38400000-8cf0-11bd-b23e-10b96e40000d

Android (including Android TVs)

App Set ID

&app_set_id=...

A 32-character UUID v4 hex string (lowercase), with or without hyphens.

For example

f81d4fae-7dec-11d0-a765-00a0c91e6bf6

Android without Google Play (Xiaomi, OPPO, Vivo)

OAID

&oaid=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6

Huawei without Google Play

Huawei OAID

&huawei_oaid=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

3c4e6a2f8b1d5e9a7c3f1b4d8e2a6c5f

LG Smart TV (webOS)

LGUDID

&webos-id=...

A 32-character UUID v4 hex string (lowercase), with or without hyphens.

For example

095f142a-ac5d-4e3b-8f2a-92c8be18d7f6

Samsung Smart TV

DUID

&tizen-duid=...

A 32-character UUID v4 hex string (lowercase), with or without hyphens.

For example

89f45b0f5b7ac1fe727fa04792b07c3e

Samsung Smart TV

TIFA

&tizen-tifa=...

A 32-character UUID v4 hex string (lowercase), with or without hyphens.

For example

00000000-34ab-cdef-1234-56789abcdef0

Samsung Smart TV

Tizen UUID

&tizen-id=...

28 characters (lowercase and uppercase), including +, -, and /, with up to three = characters at the end.

For example

DXlq4SiuR124eayZ31/lLwwww===

Samsung Smart TV

Extended DUID

&ext_duid=...

A 32-character UUID v4 hex string (lowercase), with or without hyphens.

For example

aebe52e7-03ee-455a-b3c4-e57283966239 or aebe52e703ee455ab3c4e57283966239

Any platform

Universal UUID

&uuid=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

AEBE52E7-03EE-455A-B3C4-E57283966239, AEBE52E703EE455AB3C4E57283966239, or aebe52e703ee455ab3c4e57283966239

Any platform

Device ID

&device-id=...

A 32-character hex string (uppercase or lowercase), with or without hyphens.

For example

AEBE52E7-03EE-455A-B3C4-E57283966239, AEBE52E703EE455AB3C4E57283966239, or aebe52e703ee455ab3c4e57283966239

20 or 24 characters (uppercase or lowercase).

For example

FC32D205fefF2f34FFFe or bc49ed40De6CFe5b7315Cb94

Contact support

Send an email

Levels in descending order of priority:

  • Banner.
  • Placement on the platform.
  • Placement in the section.
  • Placement on the site.
  • Campaign.
Previous
Ad label and banner menu in Adfox banners
Next
By time