Home
ClikBy
ClikBy Knowledge Base
Product and trust

Glossary

A dictionary for the ClikBy marketer and user — 73 terms in plain language, with links to guides.

12–20 min Updated: July 2026
73terms
A–Яindex
help articles

How to use

  • In the glossary 73 terms: the ClikBy product, antifraud, analytics, advertising, and compliance.
  • Wording is based on the account and the knowledge base — without invented modules.
  • Some terms have a «Read more» link to a help article.

Alphabetical index

Jump to a letter — or scroll the blocks below.

A

A/B test

Comparing two variants (ad, landing page, button) on different parts of traffic to pick the more converting one. In ClikBy, A/B can be tied to smart links and rotation.

Read more →

AI Selena

An account section with traffic-quality settings: HVT/MVT/LVT thresholds, Sensitivity, Smart Filter Mode, Conversion Score profile, audience interests, and integration fields. Live click detection also relies on the server bot-check and Smart Traffic.

Read more →

Alias

A short unique link tail on your or a shared domain (for example clik.by/promo). QR and print look at the alias — changing the destination is possible without reprinting; changing the alias breaks an already printed code.

Read more →

Audience (tab)

A visit-stats section: statuses bot_server / pending / confirmed / bot_filter and average conversion_score on confirmed clicks.

Read more →

B

bot_filter

Visit status: stayed pending without SDK confirm (around an hour) and was marked as a filtered bot/unconfirmed.

Read more →

bot_server

Visit status: the server immediately recognized a bot (isBot) and processed the click without full tracking/pixels (in non-safe modes).

Read more →

C

CCPA / CPRA

California personal-data rules: personal information categories, sale/share, opt-out. In ClikBy help — an overview tied to the Cookie Consent banner and controller/processor roles; not a substitute for legal advice.

Read more →

CNAME

A DNS record by which a custom domain or subdomain points to ClikBy infrastructure. Until CNAME/A have converged, a link on your own domain is unstable.

Read more →

confirmed

Visit status after a successful SDK confirm (or a scenario without Smart Traffic, if the click is not a bot). Usually these clicks are the ones that matter for pixels and a «clean» audience.

Read more →

Controller / Processor

GDPR/policy roles: for clickers of a client's link the controller (operator) is the account client, ClikBy is the processor (authorized person). Data-subject requests about clicks go to the link sender.

Read more →

Conversion Score

A 0–100 quality score of a confirmed visit: events, frequency, time on site, scroll, behavior, fingerprint (weights in the scoring service). Configured via ideals on the Selena tab.

Read more →

Conversions API (Meta)

Server-side event sending to Meta. When a Facebook Ads account is connected, ClikBy can send negative FraudDetected signals with fbclid of bot visits.

Read more →

CPA

Cost per Action / cost of a target action (lead, purchase). Fraud and junk traffic inflate CPA: there are clicks, no actions.

Read more →

CPC

Cost per Click — the price of a click in an ad system. CPC alone does not speak to quality: a confirmed click and conversion after the click matter.

Read more →

CTR

Click-through rate — the share of clicks from impressions. A high CTR with bots is misleading: look at quality in ClikBy, not only CTR in the Ads account.

D

Datacenter IP

An IP from datacenter/hosting ranges. In ClikBy isBot such addresses are marked ip:datacenter; with Smart Traffic a soft_pass is possible.

Read more →

Destination (target URL)

The long address the user finally goes to after the short link. UTM parameters are appended to the destination; it can be changed without changing the alias.

Read more →

DNS

The system that turns a domain name into a server address. For a custom domain in ClikBy you need correct A/CNAME records per the «Domains» section instructions.

Read more →

DPA

Data Processing Agreement — a processing mandate contract between the controller (client) and the processor (ClikBy). Relevant when working with clicker data.

Read more →

E

EU representative

The operator's representative in the EEA for GDPR. The ClikBy Policy lists an address in Barcelona (Av. Diagonal, 468).

Read more →

F

fbclid

Meta click identifier in the URL after a click from Facebook/Instagram Ads. Written into the visit; for bots it may go as a negative signal into Conversions API.

Read more →

Fingerprint

A technical browser/device fingerprint (hash). It participates in conversion_score; a too «poor» fingerprint lowers the quality score.

Read more →

FraudDetected

The event name ClikBy sends to Meta Pixel via Conversions API as a negative signal on bot fbclid (when the option is on in the Ads section).

Read more →

G

GA4

Google Analytics 4 — Google's event analytics. In ClikBy you can attach a google-analytics type pixel to a link; the GA4 field in Selena is not a substitute for that pixel.

Read more →

GDPR

The EU General Data Protection Regulation. The ClikBy Policy relies on GDPR along with Belarus Law 99-3; for clickers the client is the controller.

Read more →

GTM

Google Tag Manager — a tag container. The google-tag-manager pixel type on a link loads gtm.js; further tags are configured inside GTM.

Read more →

H

HVT / MVT / LVT

High / Medium / Low Value Traffic — «value» thresholds in the AI Selena UI (scores). Stored in settings; in the current redirect runtime clicks are not themselves banned by them.

Read more →

I

Invalid traffic (IVT)

Invalid / low-quality traffic in advertising-industry terms: bots, fake clicks, non-human clicks. Close to the notion of fraud in performance.

Read more →

IP exclusion / block list

A list of IPs the ad system should not count/show. ClikBy uploads fraud IPs to Google Ads and Yandex.Direct for selected campaigns.

Read more →

L

Look-alike

A look-alike audience in ad accounts, built on «seeds» (for example pixel visitors). The cleaner the seed (confirmed, without bots), the more useful the look-alike.

Read more →

M

MCC

Manager Customer ID — the ID of a Google Ads manager account. In the ClikBy account card it is filled optionally if access goes through MCC.

Read more →

Meta Ads (Facebook Ads)

Meta advertising. In the Ads section the platform is called Facebook Ads: OAuth, Pixel ID, negative signals on fbclid. There is no IP blocking in this integration.

Read more →

N

Noscript

A fallback pixel tag (often a 1×1 img) if JavaScript is off. Present in a number of ClikBy pixel blades (Facebook, Google Ads, LinkedIn, and others).

Read more →

O

OAuth

An access-delegation protocol: you log into Google/Meta/Yandex and give ClikBy a token for actions in the account (for example IP upload), without passing the Ads password.

Read more →

P

pending

Visit status under Smart Traffic: waiting for confirmation by the client SDK. Pixels are usually deferred until confirm.

Read more →

Pixel notification

A notice/consent on the redirect before pixels. The decision is written to the cookie consent{link_id}. Separate from the Cookie Consent banner on your site.

Read more →

Prefetch / prerender

A technical browser pre-request. In ClikBy, on Sec-Purpose prefetch a visit may not be created — this is not «fraud», but a service hit.

Read more →

Pulse

An account menu section: Ads (ad accounts), Domains, Pixels, and related tools. In Smart Filter texts it is sometimes written «Pulse/Ads».

Read more →

Q

QR-код

A two-dimensional code that leads to a ClikBy smart link. Created together with the link; PNG/SVG/PDF export; analytics = clicks on the linked link.

Read more →

R

Referrer

The address of the source page of the click. Written into the visit (if the browser sends it) and helps you see where traffic came from.

Read more →

ROI / ROAS

Return / revenue on ad spend. ClikBy does not pull ROAS from accounts automatically; click quality helps keep junk from inflating the denominator.

Read more →

S

Safe mode (Smart Filter)

The sf_mode=safe mode: suspicious clicks are logged as would_block without a hard block. Convenient for calibration; they do not enter FraudDataCollector (action=blocked).

Read more →

Sensitivity Level

Conservative / Balanced / Aggressive in AI Selena settings (AISelenaBalance). A profile UI field; it does not directly switch the isBot signal list.

Read more →

Site key (sk_)

A key for the Smart Filter SDK on the client site (format sk_…). Generated in Selena / conversion settings.

Read more →

Smart Traffic / smart filtering

A setting on the link: delay, events, client SDK, pending→confirm. Needed (or a custom domain) for pixels to fire on the redirect.

Read more →

soft_pass

Passing a soft-bot (reasons ip: / rate:) on to the SDK when Smart Traffic is on and the mode is not-safe — instead of an immediate hard-block.

Read more →

SSL / HTTPS

Encryption of the connection between browser and server. The ClikBy site uses protected connections; the footer also notes 256-bit SSL.

Read more →

U

User-Agent (UA)

The browser/client string in the HTTP request. An empty UA, bot libraries, and headless patterns are the main server isBot signals.

Read more →

UTM tags

The parameters utm_source, utm_medium, utm_campaign, utm_term, utm_content in the URL. In ClikBy the builder appends them to the destination; on the click they are written to visits.

Read more →

V

Visit / visit

A record of the click: IP, geo, device, UTM, fbclid, status, score, and others. Stats aggregates are built without IP.

Read more →

W

would_block

An action in the bot decision log in safe mode: «would have blocked», but they do not block. For observation without a hard cut-off.

Read more →

З

Law 99-3

Law of the Republic of Belarus of 07.05.2021 No. 99-3 «On Personal Data Protection». A foundation of the ClikBy Policy along with GDPR.

Read more →

Golden audience

A practice, not a separate module: a retargeting segment from people who clicked an offer and passed filtering (confirmed) into the pixel.

Read more →

К

Custom domain

Your domain/subdomain for short links. Together with Smart Traffic — a condition for pixels to work properly on the redirect.

Read more →

Click fraud

Paying for clicks with no value: bots, fake clicks, competitors. See «ad fraud» and detection in ClikBy.

Read more →

UTM parameter builder

A modal in the account: five UTM fields → append to the destination. Access by the option_utm right; the link has no separate UTM columns in the DB.

Read more →

М

Tag (Space)

In the Russian UI Spaces = «Tags»: grouping links by campaigns inside the account (do not confuse with UTM in the URL).

Read more →

О

Personal data operator

For the ClikBy service — Proactive Technology LLC (UNP 193648169, Minsk). Contacts and the EU representative are in the Privacy Policy.

Read more →

П

Пиксель

An ad-platform tracking code on the redirect/site. In ClikBy types from config/pixels.php are bound to the link; fire conditions — a domain or Smart Traffic + consent.

Read more →

Р

Ad accounts

Pulse → Ads: connecting Google Ads, Yandex.Direct, Facebook Ads to upload antifraud signals (IP / fbclid), not to import spend.

Read more →

Retargeting

Showing ads again to people who already interacted (site, pixel, offer). In ClikBy a typical path: link → filter → pixel → audience in Ads.

Read more →

С

Link expiry

ends_at, click limit expiration_clicks, expired page, and a 5 s auto-redirect with expiration_redirect.

Read more →

Subdomain

A domain part of the form go.brand.com. Often used as a branded short-link domain via DNS.

Read more →

У

Ф

Ad fraud

Clicks/visits with no real interest that you pay for. ClikBy catches signs on the click and can signal into Ads accounts.

Read more →

Я

Yandex Direct

Yandex's advertising platform. In ClikBy it is connected via OAuth with a verification code; upload of fraud IPs/subnets into selected campaigns (slot limit).

Read more →

Yandex Metrica

Yandex web analytics. Separate from the «Yandex.Audiences» pixel on the link and from connecting Direct in the Ads section.

Read more →

What’s next?

Didn't find a term?

Write to support or look at the FAQ and product map — we will extend the glossary.