--- metadata: - name: generator content: Diplodoc Platform v5.52.0 alternate: - https://yandex.com/support/adfox/en/campaigns/bind.md - https://yandex.com/support/adfox/ru/campaigns/bind.md - href: en/campaigns/bind.md type: text/markdown title: Markdown version - href: ../llms.txt type: text/markdown title: llms.txt --- > **Documentation Index:** Fetch the complete configuration index at https://yandex.com/support/adfox/en/llms.txt # Aiming You can use aiming to preview a banner added to Adfox on the site regardless of any set limits or targeting. This feature comes in handy when you need to: - Test banner placements on a site, mobile app, or a Smart TV. - Take screenshots of creatives. - Debug the banner code, SDK integration, or video player. - Check the campaign behavior from the user's perspective. You can aim at: - Flights within a supercampaign. - Banners. - Ad campaigns (on the **OLD** tab). ## Aiming methods {#methods} Select a method based on where you want to test the banner. #| || **Aiming method** | **Where it works** | **Use cases** || || Browsers | Desktop browsers with cookies enabled | Quickly testing the banner on a site in your current browser || || URL parameters | Any browser, including Safari, as well as S2S integrations | Cookies are unavailable or blocked, or you need to share the link with your team || || On devices | Mobile apps (in-app banners), Smart TVs, CTVs | Testing the banner in a mobile app or on a TV || |# ### In-browser aiming {#browser} In-browser aiming sets cookies. Adfox uses these cookies to identify your browser and deliver the aimed object to you. Here's how it works: 1. Select **Aiming in browser** on the object's page or from the campaign list. This sets an aiming cookie in your current browser. 1. Go to the site where the banner is placed. The aimed object will show up there for 30 minutes. Alternatively, copy the aiming link and share it with your team so they can preview the banner in their browsers. You can generate a link anytime over a 24-hour period, with no limit on the number of ad requests. Once generated, the aiming link is active for 30 minutes. {% note warning %} Cookie-based aiming won't work in browsers that block cookies (like Safari or privacy-focused browsers). In these cases, use aiming via URL parameters. {% endnote %} ### Aiming via URL parameters {#url} Aiming via URL parameters doesn't require cookies because the parameters are added right to the page address. This method is perfect for browsers that block cookies (like Safari or privacy-focused browsers) and for S2S integrations. Here's how it works: 1. Select **Aiming via URL parameters** on the object's page or from the campaign list. 1. In the window that opens, enter the URL of the page where the banner is placed. A preview link with aiming parameters will appear below, for example: `https://example.com?adf_aimed_campaign_id=12345&adf_aimed_banner_id=67890`. 1. Copy the link and open it in the browser you're using for testing, or share it with your team. You can also click **Follow the link** to open the page with the aimed object right away. {% note tip %} If you already know the page URL, you can manually add the parameters `?adf_aimed_campaign_id=XXX&adf_aimed_banner_id=YYY` to the address. {% endnote %} ### On-device aiming {#device-id} On-device aiming uses a device ID so you can test banners in mobile apps or on Smart TVs where browsers and cookies aren't an option. {% note alert %} For aiming to work, your app or the SDK needs to pass the device ID in the ad request to Adfox using the correct GET parameter. For example, if you set up aiming using GAID, the request must include the parameter `&google_aid=38400000-8cf0-11bd-b23e-10b96e40000d`. If this parameter is missing or doesn't match your settings in the interface, aiming won't work. Check with your app developer to see exactly which ID is being passed in the request, and use the same type when setting up your aiming. {% endnote %} #### Supported ID types #| || **Platform** | **ID** | **Engine parameter** | **Format** || || iOS (iPhone, iPad) | IDFA | `&idfa=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `AEBE52E7-03EE-455A-B3C4-E57283966239` {% endcut %} || || iOS (iPhone, iPad) | IDFV | `&ifv=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `5A7D2D91-E1F2-4B3A-9C8D-1F6E4A2B5C3D` {% endcut %} || || Android (including Android TVs) | GAID | `&google_aid=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `38400000-8cf0-11bd-b23e-10b96e40000d` {% endcut %} || || Android (including Android TVs) | App Set ID | `&app_set_id=...` | A 32-character UUID v4 hex string (lowercase), with or without hyphens. {% cut "For example" %} `f81d4fae-7dec-11d0-a765-00a0c91e6bf6` {% endcut %} || || Android without Google Play (Xiaomi, OPPO, Vivo) | OAID | `&oaid=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6` {% endcut %} || || Huawei without Google Play | Huawei OAID | `&huawei_oaid=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `3c4e6a2f8b1d5e9a7c3f1b4d8e2a6c5f` {% endcut %} || || LG Smart TV (webOS) | LGUDID | `&webos-id=...` | A 32-character UUID v4 hex string (lowercase), with or without hyphens. {% cut "For example" %} `095f142a-ac5d-4e3b-8f2a-92c8be18d7f6` {% endcut %} || || Samsung Smart TV | DUID | `&tizen-duid=...` | A 32-character UUID v4 hex string (lowercase), with or without hyphens. {% cut "For example" %} `89f45b0f5b7ac1fe727fa04792b07c3e` {% endcut %} || || Samsung Smart TV | TIFA | `&tizen-tifa=...` | A 32-character UUID v4 hex string (lowercase), with or without hyphens. {% cut "For example" %} `00000000-34ab-cdef-1234-56789abcdef0` {% endcut %} || || Samsung Smart TV | Tizen UUID | `&tizen-id=...` | 28 characters (lowercase and uppercase), including `+`, `-`, and `/`, with up to three `=` characters at the end. {% cut "For example" %} `DXlq4SiuR124eayZ31/lLwwww===` {% endcut %} || || Samsung Smart TV | Extended DUID | `&ext_duid=...` | A 32-character UUID v4 hex string (lowercase), with or without hyphens. {% cut "For example" %} `aebe52e7-03ee-455a-b3c4-e57283966239` or `aebe52e703ee455ab3c4e57283966239` {% endcut %} || || Any platform | Universal UUID | `&uuid=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `AEBE52E7-03EE-455A-B3C4-E57283966239`, `AEBE52E703EE455AB3C4E57283966239`, or `aebe52e703ee455ab3c4e57283966239` {% endcut %} || || Any platform | Device ID | `&device-id=...` | A 32-character hex string (uppercase or lowercase), with or without hyphens. {% cut "For example" %} `AEBE52E7-03EE-455A-B3C4-E57283966239`, `AEBE52E703EE455AB3C4E57283966239`, or `aebe52e703ee455ab3c4e57283966239` {% endcut %} 20 or 24 characters (uppercase or lowercase). {% cut "For example" %} `FC32D205fefF2f34FFFe` or `bc49ed40De6CFe5b7315Cb94` {% endcut %} || |# #### How to set up aiming by device ID 1. Select **Aiming by Device** on the object's page or from the campaign list. 1. In the window that opens, enter the device ID or pick one from your saved IDs. Adfox stores your last 10 device IDs, so next time you can just select your device from the list without typing the ID again. If you've already used a device ID for aiming, you'll see an **Aimed** label next to it. 1. Click **Save**. 1. Open the app or play some content on your Smart TV, and the aimed banner will appear on the device right away. #### Where to find the device ID on your device {% list tabs radio %} - IDFA (iPhone or iPad) You can't look up the IDFA directly in the settings on Apple devices. Here's how to find it: 1. Install a free app from the App Store — for example, **My Device ID by AppsFlyer** or **FindMyIDFA**. 1. Open the app, and your IDFA will show up on the screen. Copy the ID and paste it into the device ID field in Adfox. Make sure that tracking is enabled on your device: **Settings** → **Privacy & Security** → **Tracking** → **Allow Apps to Request to Track**. - IDFV (iPhone or iPad) If a user hasn't granted ATT (App Tracking Transparency) permission and the IDFA is unavailable, use the IDFV (Identifier for Vendor) instead. This is an ID that iOS assigns to a group of apps from the same developer on a device. Unlike the IDFA, it doesn't require user permission and remains available as long as at least one of the developer's apps is installed on the device. Device settings don't show the IDFV, so you can't look it up manually like the IDFA. You can only access it programmatically through the property `UIDevice.current.identifierForVendor` in the iOS SDK. To get an IDFV: 1. Check with the app developer: they can call the IDFV retrieval API and give you the ID. 1. Copy the ID and paste it into the device ID field in Adfox. The IDFV is passed as a 36-character string. {% note warning %} The IDFV resets if the user deletes all of that vendor's apps from their device. When the user reinstalls any app, they'll get a new IDFV. {% endnote %} - GAID (Android smartphone or tablet) 1. Open **Settings** on your device. 1. Go to the advertising ID section. The exact path depends on your Android version and device manufacturer: - Android 14 and above (Pixel and others): **Settings** → **All services** → **Privacy & security** → **Ads**. - Android 12 and 13: **Settings** → **Privacy** → **Ads**. - Android 11 and below (or Xiaomi and some other UIs): **Settings** → **Google** → **Ads**. - Samsung (One UI): **Settings** → **Security and privacy** → **More privacy settings** → **Ads**. 1. Your advertising ID (GAID) will show up on the screen. Copy the ID and paste it into the device ID field in Adfox. {% note tip %} If you can't find the section, just type “ads” or “advertising” into the search bar in your device settings. {% endnote %} {% note warning %} Starting with Android 12, users can delete their advertising ID instead of simply resetting it. If the GAID is deleted, apps will receive a string of zeros: `00000000-0000-0000-0000-000000000000`. If this happens, use the App Set ID instead. {% endnote %} - GAID (Android TV) Unlike mobile devices, the advertising ID on Android TV devices (TVs and streaming boxes) is located in a different place: 1. Go to the Android TV home screen. 1. Select the **Settings** icon at the top of the screen. 1. Select **Device** → **Preferences** → **About**. 1. Choose **Legal information** → **Ads**. 1. Your advertising ID will show up at the bottom of the screen, right next to the text “This device ID”. 1. Copy the ID and paste it into the device ID field in Adfox. {% note tip %} On some devices, the exact path might vary depending on the manufacturer and OS version. If you can't find the section, try looking for the ID under **Settings** → **About** → **Legal information** → **Ads**. {% endnote %} {% note warning %} You can also reset or delete the ID right from this section. Once you delete the ID, the device won't be assigned a new one. Instead, apps will just receive a string of zeros. {% endnote %} - App Set ID Use the App Set ID if you need to test the banner inside an app where the user has opted out of personalized ads and reset or disabled their GAID. The App Set ID is a unique identifier that Google Play Services assigns to a group of apps from the same developer on a device. The App Set ID doesn't appear in the device settings, so you can't look it up manually like the GAID or IDFA. You can only access it programmatically through **App Set ID API** (`com.google.android.gms.appset`). To get the App Set ID: 1. Check with your app developer: they can retrieve the ID by calling `AppSetIdClient.getAppSetIdInfo()`. 1. Copy the value and paste it into the device ID field in Adfox. {% note warning %} The App Set ID is shared by all apps from the same developer on a device. If you're testing aiming in someone else's app, its App Set ID will be different from your test ID. {% endnote %} - OAID (Android without Google Play) The OAID (Open Advertising ID) is an advertising identifier for Android devices that don't have Google Play Services. It's used on Xiaomi, OPPO, Vivo, Realme, Meizu, and others. The OAID standard was developed by the MSA (Mobile Security Alliance). {% note warning %} On devices with Google Play (even those from Chinese vendors), GAID still takes priority. Only use OAID if GAID is unavailable. {% endnote %} The OAID doesn't show up in standard Android settings. On some devices, you can look it up like this: {% list tabs %} - OPPO (ColorOS) **Settings** → **Privacy** → **System services** → **OAID advertising**. - Vivo (Funtouch OS / OriginOS) **Settings** → **More settings** → **Privacy** → **Ads**. - Xiaomi (MIUI) Check with your app developer, or just type “ads” or “OAID” into the search bar in your device settings. {% endlist %} {% note tip %} If you can't find the section, just type “ads” or “OAID” into the search bar in your device settings. If the OAID doesn't show up in the settings, you can retrieve it programmatically via the **MSA OAID SDK** — check with your app developer. {% endnote %} - Huawei OAID (Huawei without Google Play) The Huawei OAID is the advertising identifier for Huawei devices running on HMS Core (Huawei Mobile Services) without Google Play. These devices have been on the market since 2019: Mate 30, P40, Mate 40, Nova 8, and newer models. {% note tip %} Huawei devices with Google Play support GAID as well. Which ID to use depends on the SDK your app was built with. {% endnote %} To look up the Huawei OAID on the device: 1. Open **Settings**. 1. Go to **Privacy** → **Ads**. The exact path may vary depending on your EMUI or HarmonyOS version. 1. The advertising ID will show up on the screen. Copy the ID and paste it into the device ID field in Adfox. If the ID doesn't appear in the settings — for example, on older models with Google Play — you need to retrieve it programmatically via the **HMS Core Identifier Service** (check with your app developer). {% note warning %} When you reset the advertising ID in the settings, the Huawei OAID value changes, so you'll need to fetch the new ID after the reset. {% endnote %} - DUID/TIFA (Samsung Smart TV) You can look it up via the TV's menu (DUID): 1. Press **Menu** on the remote control. 1. Go to **Support** → **Contact Samsung** or **Settings** → **Support** → **About This TV**. 1. The device ID (DUID) will show up on the screen. Copy the ID and paste it into the device ID field in Adfox. You can access the advertising ID (TIFA) programmatically using the **Samsung AdInfo API**. If your app uses the [Samsung Ads SDK](https://developer.samsung.com/SmartTV/develop/api-references/samsung-product-api-references/adinfo-api.html), the TIFA is passed automatically. - Tizen UUID (Samsung Smart TV) In addition to DUID and TIFA, Samsung Smart TVs also support the Tizen UUID. This is a unique identifier that Tizen generates individually for each app on the device (a per-app UUID). Go with the Tizen UUID if your app doesn't support TIFA, or if the user resets their TIFA and you need a stable ID for testing. The Tizen UUID doesn't show up in the TV's menu, so you can't look it up manually. You'll need to access it programmatically using the **Tizen Device API** (`tizen.systeminfo.getCapability("http://tizen.org/system/tizenid")`) or through `GetUuid()` in the **Tizen TV API**. To get the Tizen UUID: 1. Check with your app developer: they can call the UUID retrieval API and give you the ID. 1. Copy the ID and paste it into the device ID field in Adfox. {% note warning %} Each app has a unique Tizen UUID on the same TV. This means an ID obtained from a test app won't work for testing banners in a different app. {% endnote %} - LGUDID (LG Smart TV, webOS) LG Smart TVs run on the webOS platform. These devices are identified using the LGUDID (LG Unique Device ID). It's a unique ID you can fetch programmatically using the [webOS Device Unique ID API](https://webostv.developer.lge.com/develop/references/device-unique-id). To fetch the ID, the app sends a request: `luna://com.webos.service.sm → deviceid/getIDs → idType: ['LGUDID']`. This returns a standard UUID-formatted string: `095f142a-xxxx-ac5d-xxxx-92c8be18xxxx`. If you're integrating the LG SDK, ask your app developer to give you the LGUDID from the test TV. {% note warning %} IDs found under “TV information” (such as ESN, Widevine, or VSN) are not the LGUDID. You can't use them for aiming in Adfox. {% endnote %} {% endlist %} ## Aiming features {#bind-features} ### Enable aiming {#start} - You can't aim at multiple campaigns or banners from different ad campaigns. The last object aiming is valid. - You can aim at objects with the **active** status, including objects with a start date in the future and with any set of targetings and limits at any level. - The necessary object is shown only with its ad codes. If your code can return multiple banners from the campaign you're aiming at, the banners are displayed at random. ### Statistics {#statistics} Statistics (ad responses, impressions, clicks, events) for the aimed object aren't included in reports. ### Finish aiming {#finish} - You can't disable aiming forcibly: the aiming time must expire. - After the end of the aiming time for the user that's aiming at the object, running continues as usual: targeting and restrictions apply, and statistics continue to be calculated. {% note info %} For all other users (not aiming at the object) banner running continues as usual. {% endnote %} ## Contact support Send an email