The pixel bridges the click, the site, and autostrategies
In the Yandex stack there are two different tools: the Yandex Audiences pixel (IDs for retargeting and look-alikes) and the Yandex Metrica tag (on-site analytics: visits, goals, ecommerce). Yandex Direct uses segments and goals in autostrategies — automated bid and reach optimization on historical data.
When bots hit the pixel and goals, algorithms learn from noise: CPC rises, real conversion falls, look-alikes pull junk profiles. Below — how the flow works and what ClikBy actually does (no product promises that do not exist).
How Audiences, Metrica, and Direct connect
- Yandex Audiences. Segment service for retargeting. IDs arrive after the pixel fires (or via hashed CRM list uploads).
- Yandex Metrica. Analytics on your site: visits, goals, ecommerce. Audiences segments are often built on Metrica goals — that is configured in Yandex, not in ClikBy.
- Yandex Direct. Uses Audiences segments for targeting and optimizes campaigns (including CPA/ROAS autostrategies) on conversion signals. Garbage in, garbage out.
Typical paid path: Direct ad → site → Metrica and/or Audiences pixel → segment such as «viewed product» → autostrategy scales look-alikes. A bot can complete the same path in seconds — no purchase, full trail in Yandex data.
Why bots poison autostrategies
Autostrategies do not tell apart an intentful human click from a headless browser on a residential IP. They maximize the chosen metric (clicks, Metrica goals, CPA). A bot farm can:
- Inflate retargeting audiences with fake visits — you pay for impressions to non-users.
- Skew look-alikes: the model finds bot-like profiles, not buyers.
- Fake «cheap conversion» on micro-goals (e.g. 10% scroll) if bots complete them.
Invalid-traffic filters inside Direct alone do not cover all acquisition: a click may be «valid» for the platform and useless for your business.
What the ClikBy «Yandex Audiences» pixel really does
ClikBy has a pixel type Yandex Audiences (yandex-audience). You attach the pixel ID to a smart link. When it fires, the browser loads a hidden image:
https://mc.yandex.ru/pixel/{ID}?rnd={timestamp}
This is not a full Metrica counter: no watch.js, no ym(), no goals, Webvisor, or ecommerce through ClikBy. Only an Audiences pixel request with the ID and rnd (cache-busting) goes to Yandex.
- Custom domain or Smart Traffic. If the link has pixels but neither a custom domain (
domain_id) nor Smart Traffic, the server issues a direct redirect — pixels do not fire. - Custom domain, no Smart Traffic: an intermediate redirect page shows the pixel image, then after ~500 ms sends the user to the destination. With cookie notice (
pixel_notification) enabled, pixels run only after consent (consent{linkId}=1); on decline — direct redirect without pixels. - With Smart Traffic: the user lands on your site with
_cb_token; the ClikBy SDK injects the same Yandex Audiences pixel after behavior checks. You need a Site Key and the SDK on the destination site. - Server-side bots. Requests the ClikBy redirect server marks as bots and blocks leave without the intermediate pixel page (exceptions: safe test mode and some soft bots with Smart Traffic that may reach the on-site SDK). That is not the same as «Yandex receives ClikBy confirmed status».
The ClikBy Audience section (confirmed / bot / pending) is separate click-quality analytics. ClikBy statuses are not sent to Yandex Audiences as a segment field. The practical value: fewer bots get a pixel hit (block / Smart Traffic) and you can compare bot share by link alias with Metrica and Direct reports.
Creating the pixel in Yandex UI and adding the ID in ClikBy: Yandex Audiences pixel guide (RU help).
Practical setup
- Step 1. Direct ads point to a ClikBy smart link (custom domain or Smart Traffic), not a setup where pixels cannot fire.
- Step 2. Attach the «Yandex Audiences» pixel type with your ID; enable the cookie notice on redirect if needed.
- Step 3. Install Metrica with goals on the site separately — ClikBy does not replace it. Direct autostrategies learn from Yandex goals and segments; ClikBy only affects who gets an Audiences pixel hit on the click path.
- Step 4. Every 1–2 weeks compare ClikBy bot share for the link with Metrica anomalies (bounce, 0-second sessions) and CPA trends in Direct.
Honest product scope
ClikBy is not part of Yandex and does not auto-clean Audiences segments. There is no setting «send only confirmed to Yandex». Value — early click classification, redirect without pixels for some bots, Smart Traffic with delayed pixel inject after on-site checks, and clear stats in Audience. For click-fraud signals in analytics: how to spot ad click fraud.
Common mistakes
- One «all visitors 30 days» segment with no quality filter at the door — autostrategies scale junk.
- Look-alike on a segment filled by bots via a bare link without domain and without Smart Traffic.
- Confusing the ClikBy Audiences pixel with full Metrica: ecommerce goals and purchase learning still live in Metrica/Direct on your site.
- Pixel only on-site while ads hit a pre-landing with no click-quality layer — budget burns before your analytics.
Set up smart links and pixels with ClikBy
When processing personal data in Belarus, follow Law No. 99-3 on Personal Data Protection.
