Kadam FAQ en

Версия на русском языке

Important:

• All Kadam requests must include the sub8 = 2, 13 filter, otherwise data from transit pages will be included in the query result.
• When comparing Kadam and Kaminari stats, remember to use the same timezones.

Click types

Bots

BV — bot visits. Bots refer to programs or automated scripts that request web content (including digital ads) without user involvement.

Name	Description
Crawlers	These are legitimate bots that honestly identify themselves through the user agent. They crawl through web pages and gather content for various technical purposes. For example, they can be search engine bots indexing the internet; social media bots caching pages for previews or taking screenshots; scrapers collecting web pages for their own purposes, etc. These are not malicious bots, but they cannot convert and therefore we must ignore them.
Spoofing	These are bots whose information declared in the user agent does not correspond to reality. Normally, a browser does not lie about itself. Malicious actors force infected browsers to lie and visit links pretending to be different user agents. Most often, this concerns infected computers that are part of a botnet.
Automated	These are special browsers that are controlled by external scripts. Such browsers were originally created for automated software testing, but it turned out that they are also great for generating fraudulent traffic. They can be either virtual machine setups on which Headless Chrome or Phantom JS are installed, or huge click farms where real smartphones generate clicks without user involvement.
iFrame	To increase ad impressions, advertising is placed on the website in small or inconspicuous elements (iframes).

Suspicios visits

SV — suspicios visits. We see something suspicious in the data collected from the click, but it is not enough to confidently say that it is a bot. It is recommended to examine conversions in each specific case and make a separate decision.

Name	Description
Proxy	Users who change their location using an IP address (VPN, proxy, Tor). These are live clicks, they can even result in conversions, but they come from non-targeted geographies. If geo is important for your advertising, you need to pay attention to this metric.
Suspition of spoofing	We do not have a clear certainty that it is a bot, but we have suspicion. Possible reasons - the user has installed a harmless extension that affects our checks; some browsers and Android applications have a hard-coded (embedded, unchangeable) user agent.
Suspition of automated	We also do not have a clear certainty that we are dealing with a bot, but there is suspicion. Possible reasons - again, some harmless extensions that make us suspect that the browser is being controlled from the outside.
Suspition of fraud	There is a suspicion that the ad is located on the site beyond the screen.

Technical losses

Tech losses. These are clicks that we could not verify. Possible reasons - browsers with disabled JS; outdated browsers; click for some reason reached Kadam, but did not reach Kaminari.

Good clicks

These are clicks that we have checked and are 100% sure that they were not made by bots. That is, it is the total number of clicks minus technical losses minus bot clicks minus suspicious clicks. Plus, we unique these clicks by clickID (removing duplicates, because duplicates are a bad sign).

Click uniqueization

It is assumed that a clickable link can be accessed only once. Therefore, the first entry is unique, and subsequent ones are duplicates. Duplicates are either technical artifacts (for example, the link was cached in the browser) or fraud and we should ignore them in statistics.

Statistics are counted only for unique clicks. If you need to watch something with duplicates, you can do this by selecting Count with doubles in the Settings pop-up window.

Traffic back reasons

Reason	Russian name	English name
0	нормальный клик	ok
20	двойной клик в рамках одного аукциона	double click per one auction
80	более трёх кликов от одного юзера, на одной площадке за 30 мин	more than three clicks from one user on one macros in 30 minutes
90	user agent заблокирован	user agent is blocked
120	ошибка в записи уникального кэша	error recording unique cache
130	ошибка в получении уникального кликмаркера	error getting unique clickmarker
150	отсутствует user agent	user agent is empty
160	IP заблокирован	IP is blacklisted
170	клик с utm меткой «adv»	click from advancets
220	быстрый клик (менее 3 сек)	too fast click (less than 3 seconds)
240	клик с другого региона	click from different region
250	клик с другого IP адреса	click from different IP
260	клик пришёл спустя два дня после показа	click received two days after the view
270	клик с другого браузера	click from different browser
280	клик с другой платформы	click from different platform
290	клик с другого интернет-провайдера	click from different ISP
300	клик с другой организации интернет-провайдера	click from different ISP organization
310	клик пришёл с недоступного SSP	click from SSP which is not available
320	клик с другим user agent (отличным от user agent аукциона)	click with different user agent
330	клик пришёл после того как закончилось время жизни кликовой ссылки	click timed-out (more than lifetime of the clicked link)
340	клик пришёл после того как закончилось время жизни кликовой ссылки	click timed-out (more than 2 hours)
350	клик пришёл в течение 30 мин после аукциона и нет notice	click without nurl
360	Kaminari маркировал клик как фрод	Kaminari-detected fraud
370	кликовая ссылка повреждена	damaged clicked link
380	срез забанен (добавлен в blockedSites и не имеет blockedSitesGroupId ИЛИ добавлен в blockedSites и имеет blockedSitesGroupId, но у кампании не стоит флаг на выкуп этой группы)	Banned click
390	SSP отключена	SSP not enabled

Sub-tags

Name	Kadam's analog	Explanation
sub1	-	Traffic source (within Kadam integration, it is always equal to kdm).
sub2	sourceID	Traffic source ID - SSP (if utmCampaign in ('1', '2') - these are Kadam's direct webs, if other numbers, then these are external SSP).
sub3	blockTypeID	Ad block format ID: utmMedium in ('0','10') — teaser/banner, utmMedium in ('20') — on-site and classic push, utmMedium in ('30') — clickunder, utmMedium in ('60') — video, utmMedium in ('90') — catfish.
sub4	dspID	ID DSP, that is, who we sell this traffic to (utmTerm='1' - these are our direct ads, if other ID, then these are external DSP).
sub5	macrosID	Ad block ID on a specific domain, used to interact with advertisers, passed on to them in statistics.
sub6	adID	Ad creative ID.
sub7	userlong	Hash from the user's cookie, intended for user unification.
sub8	eventType	eventType in KadamProd.Clicks: 2 — paid click, 13 — unpaid click, 18 — transit page display, 19 — transit page click, -1 — click that came to Kaminari but not to Kadam. For example, direct requests to the Kaminari URL from the browser cache and other technical spam.
sub9	susReason or tbReason	susReason or tbReason (whichever is non-empty) from KadamProd.Clicks (filled in for event=ping and event=complete) (see table above).
sub10	Example	fraud if the click did not pass the verification, an empty string if it passed.

Other tags

Name	Kadam's analog	Explanation
clickID	clickID	Click's ID.
Placement ID	placementID	The ID of the page/location where the ad block is placed.
PID	extBlockID	pid (publisher id), which we receive from external SSPs and separate streams through it. That is, it is the ID of a certain revenue stream of the publisher.
Click link	-	Click link (URL of page, where Kaminari script is running).
SSP name	-	The sub2 tag as text.
Domain name	~domainID	Domain's name, which we receive from SSP.
Adv discrep	-	Technical losses, uniqueized by clickID.
Paid clicks	-	Number of paid clicks (with sub8='2').