The pixel is a bridge between the click, the site, and auto-strategies

In the Yandex ecosystem people usually mean two different things: the Yandex.Audience pixel (collecting identifiers for retargeting and similar audiences) and the Yandex.Metrica counter (on-site analytics: visits, goals, ecommerce). Yandex.Direct uses segments and goals in auto-strategies — automatic bid and reach optimization on historical data.

If bots land in the pixel and goals, the algorithm «learns» from noise: cost per click rises, real conversion falls, similar audiences pull in junk profiles. Below — how the data flow is built and what ClikBy actually can do (without promises that are not in the product).

How Audiences, Metrica, and Direct are connected

• Yandex.Audience. A segments service for retargeting. Identifiers land there after the pixel fires (or via upload of hashed contact lists).
• Yandex.Metrica. Analytics on your site: visits, goals, ecommerce. Segments in Audience are often built on Metrica goals — that is a Yandex-side setting, not ClikBy.
• Yandex.Direct. Takes Audience segments for targeting and optimizes campaigns (including auto-strategies on CPA/ROAS) on conversion signals. Garbage in — garbage in training.

Typical paid-click path: Direct ad → site → Metrica and/or Audience pixel firing → a segment like «visited a product card» → auto-strategy scales similar users. A bot can take the same path in seconds — without a purchase, but with a full trail in Yandex data.

Why bots spoil auto-strategies

Auto-strategies do not distinguish «a person with intent to buy» from «a headless browser with a «home» IP». They maximize the chosen metric (clicks, Metrica goals, CPA). A bot farm can:

• Inflate the retargeting audience with fake visits — you pay for impressions to users who do not exist.
• Distort similar audiences: the model looks for people similar to bots, not buyers.
• Give a false «cheap conversion» signal on micro-goals (for example, 10% scroll) if bots complete them.

Invalid-traffic filters in Direct alone do not cover the whole buy: a click can be «valid» for the placement but useless for the business.

What the «Yandex.Audience» pixel actually does in ClikBy

In the ClikBy cabinet there is a pixel type «Yandex.Audience» (yandex-audience). A pixel ID is attached to the smart link. On fire, the browser loads a hidden image:

https://mc.yandex.ru/pixel/{ID}?rnd={time}

Это не a full Metrica counter: no watch.js, there are no calls ym(), goals, webvisor, or ecommerce through ClikBy. Only an Audience pixel request with the ID and the parameter goes to Yandex rnd (so it is not cached).

• Custom domain or Smart Traffic. If pixels are attached to the link, and there is neither a custom domain (domain_id), nor Smart Traffic enabled, the server does a direct redirect — pixels do not fire.
• Without Smart Traffic, with a custom domain: the intermediate redirect page shows the pixel (image), then after ~500 ms sends the user to the destination URL. If the cookies notice is enabled (pixel_notification), pixels are shown only after consent (cookie consent{link_number}=1); on decline — a direct redirect without pixels.
• With Smart Traffic: the user goes to the site with a token _cb_token; the ClikBy script on the site, after a behavior check, inserts the same Yandex.Audience pixel. You need a Site Key and the SDK installed on the destination site.
• Server-side bots. Requests that the ClikBy redirect server marks as a bot and blocks leave without an intermediate pixel page (exceptions: safe test mode and some «soft» bots with Smart Traffic — they may reach the SDK on the site). This is not the same as «Yandex receives a confirmed status from ClikBy».

Раздел «Audience» section in the ClikBy cabinet (confirmed / bot / pending statuses) is separate click-quality analytics. ClikBy statuses are not passed to Yandex.Audience as a segment field. The value of the pairing: fire the pixel for bots less often (blocking / Smart Traffic) and watch the bot share by link alias next to Metrica and Direct reports.

Step-by-step pixel creation in the Yandex interface and adding the ID in ClikBy: the «Yandex.Audience pixel» guide.

A practical scheme for the team

• Step 1. Direct ads go to a ClikBy smart link (custom domain or Smart Traffic), not «into nowhere» without conditions for pixels.
• Step 2. On the link — a «Yandex.Audience» type pixel with your ID; if needed, enable the cookies notice on the redirect.
• Step 3. On the site, separately install a Metrica counter with goals — ClikBy does not replace it. Direct auto-strategies learn from Yandex goals and segments; ClikBy only affects кому the Audience pixel managed to fire for on the hop.
• Step 4. Every 1–2 weeks, compare the bot share in ClikBy for the link with anomalies in Metrica (bounces, 0-second sessions) and CPA dynamics in Direct.

Common mistakes

• A «all visitors in 30 days» segment with no quality cleanup at the intake — the auto-strategy scales junk.
• A similar audience based on a segment that bots filled via the pixel on a «bare» link with no domain and no Smart Traffic (the pixel may not have fired as needed — or conversely fired for everyone on the intermediate page).
• Confusing the Audience pixel in ClikBy with full Metrica: ecommerce goals and auto-strategy training on purchases are still configured in Metrica and Direct on the site.
• Pixel only on the site, while ads go to someone else's prelander with no click-quality control — budget burns before your analytics.

Set up smart links and pixels in ClikBy

When working with personal data in Belarus, follow the requirements of the Republic of Belarus Law No. 99-3 “On Personal Data Protection”.