Metrics and groups - Revision history

Admin: /* Device */

2026-01-26T09:51:14Z

Device

← Older revision		Revision as of 09:51, 26 January 2026
Line 205:		Line 205:
	\|-		\|-
	\| Device type from UA \|\| Device type (desktop, smartphone, smart TV, etc.) obtained from user agent.		\| Device type from UA \|\| Device type (desktop, smartphone, smart TV, etc.) obtained from user agent.
			\|-
			\| Android app \|\| The name of the Android app from which the click came.
	\|-		\|-
	\| Connection type \|\| The type of connection that the device uses to connect to the network (Bluetooth, Wi-Fi, mobile internet).		\| Connection type \|\| The type of connection that the device uses to connect to the network (Bluetooth, Wi-Fi, mobile internet).
	\|}		\|}

	~~<!--T:20-->~~
	=== Screen ===		=== Screen ===
	{\| class="wikitable"		{\| class="wikitable"

Admin: /* Feature */

2025-12-01T11:36:00Z

Feature

← Older revision		Revision as of 11:36, 1 December 2025
Line 111:		Line 111:
	\|-		\|-
	\| Push notifications \|\| Number of visits from browsers that support push notifications.		\| Push notifications \|\| Number of visits from browsers that support push notifications.
			\|-
			\| Hidden Page \|\| Indicates whether the ad page opened in a hidden tab (popunder) — True; in an active tab — False. Actions outside the browser (e.g., app switching) do not count. The metric tracks browser tab visibility only.
	\|}		\|}

	~~<!--T:21-->~~
	=== Behavioral analysis ===		=== Behavioral analysis ===
	Metrics based on the analysis of how the user behaved on the page.		Metrics based on the analysis of how the user behaved on the page.

Admin at 08:45, 7 November 2024

2024-11-07T08:45:45Z

← Older revision		Revision as of 08:45, 7 November 2024
Line 171:		Line 171:
	\| Language \|\| User's preferred language, i.e. UI language set in the browser settings.		\| Language \|\| User's preferred language, i.e. UI language set in the browser settings.
	\|-		\|-
	\| Timezone \|\| ~~Browser time zone, actually the user~~'s ~~operating system time zone~~.		\| Timezone \|\| User's timezone data obtained from IP address.
	\|-		\|-
	\| Country \|\| Country data obtained from IP address.		\| Country \|\| Country data obtained from IP address.
Line 178:		Line 178:
	\|-		\|-
	\| Provider \|\| Internet service provider data obtained from IP address.		\| Provider \|\| Internet service provider data obtained from IP address.
			\|-
			\| IP \|\| IP without the last octet, i.e. there will always be zeros at the end, for example: 192.168.1.00.
	\|}		\|}

Line 186:		Line 188:
	! Name !! Description		! Name !! Description
	\|-		\|-
	\| ~~Browser \|\| Browser name and version taken from user agent.~~		\| Real browser engine \|\| All modern browsers are based on three open-source engines:
	\|-
	~~\| Browser~~ engine \|\| All modern browsers are based on three open-source engines:
	# Blink (Chrome, Chromium, Yandex Browser, Samsung Browser, modern Opera and MS Edge, most Android browsers);		# Blink (Chrome, Chromium, Yandex Browser, Samsung Browser, modern Opera and MS Edge, most Android browsers);
	# WebKit ((Safari; versions of Chrome, Yandex Browser, Firefox, etc. for iOS; browsers in PlayStation);		# WebKit ((Safari; versions of Chrome, Yandex Browser, Firefox, etc. for iOS; browsers in PlayStation);
Line 195:		Line 195:
	We can determine all 6 engines by their characteristic features, as well as determine the specific version of the engine. It is the browser engine that we write this data to.		We can determine all 6 engines by their characteristic features, as well as determine the specific version of the engine. It is the browser engine that we write this data to.
	\|-		\|-
	\| OS \|\| ~~Operating system and its~~ version ~~taken from user agent~~.		\| Real OS \|\| The current OS without version.
	\|-		\|-
	\| ~~Real~~ OS \|\| ~~The current OS without~~ version.		\| Browser from UA \|\| Browser name and version taken from user agent.
			\|-
			\| OS from UA \|\| Operating system and its version taken from user agent.
	\|-		\|-
	\| Device \|\| Mobile device manufacturer obtained from user agent.		\| Device from UA \|\| Mobile device manufacturer obtained from user agent.
	\|-		\|-
	\| Device type \|\| Device type (desktop, smartphone, smart TV, etc.) obtained from user agent.		\| Device type from UA \|\| Device type (desktop, smartphone, smart TV, etc.) obtained from user agent.
	\|-		\|-
	\| Connection type \|\| The type of connection that the device uses to connect to the network (Bluetooth, Wi-Fi, mobile internet).		\| Connection type \|\| The type of connection that the device uses to connect to the network (Bluetooth, Wi-Fi, mobile internet).

Admin at 09:20, 23 August 2024

2024-08-23T09:20:33Z

← Older revision		Revision as of 09:20, 23 August 2024
Line 30:		Line 30:
	\| Hits \|\| Total number of checks.		\| Hits \|\| Total number of checks.
	\|-		\|-
	\| Unique users \|\| Number of unique users counted based on IP ~~and~~ user agent.		\| Unique users \|\| Number of unique users counted based on IP, user agent and client hints.
	\|-		\|-
	\| Good \|\| Number of checks resulting in non-bot, non-suspicious, and non-technical loss traffic.		\| Good \|\| Number of checks resulting in non-bot, non-suspicious, and non-technical loss traffic.

Admin at 15:51, 3 January 2024

2024-01-03T15:51:45Z

← Older revision		Revision as of 15:51, 3 January 2024
Line 66:		Line 66:
	\|-		\|-
	\| Bad reputation IP \|\| IPs from which only technical losses come. For example, someone set up a server in a data center, and using CURL, or another tool for http requests (and they are found in all programming languages), parses pages, and then clicks on advertising links using the same tool.		\| Bad reputation IP \|\| IPs from which only technical losses come. For example, someone set up a server in a data center, and using CURL, or another tool for http requests (and they are found in all programming languages), parses pages, and then clicks on advertising links using the same tool.
			\|-
			\| Blocked hits \|\| Hits that were blocked according to integration settings.
	\|}		\|}

Admin at 12:25, 13 October 2023

2023-10-13T12:25:16Z

← Older revision		Revision as of 12:25, 13 October 2023
Line 39:		Line 39:
	<!--T:8-->		<!--T:8-->
	=== Invalid traffic (IVT) ===		=== Invalid traffic (IVT) ===
	Invalid traffic consists of bot and scammers traffic.		Invalid traffic consists of bot traffic and scammers traffic.

	<!--T:23-->		<!--T:23-->

Admin: Marked this version for translation

2023-10-13T12:07:49Z

Marked this version for translation

← Older revision		Revision as of 12:07, 13 October 2023
Line 41:		Line 41:
	Invalid traffic consists of bot and scammers traffic.		Invalid traffic consists of bot and scammers traffic.

			<!--T:23-->
	A bot is a program or automated script that requests web content (including digital advertising) without user involvement. It could be, for example, a browser on an infected computer that is part of a botnet, or a script written by a programmer that scrapes websites for some purpose.		A bot is a program or automated script that requests web content (including digital advertising) without user involvement. It could be, for example, a browser on an infected computer that is part of a botnet, or a script written by a programmer that scrapes websites for some purpose.

			<!--T:24-->
	Scammers traffic is traffic generated by real people who are tricked into requesting web content (including digital advertising) without knowing about it.		Scammers traffic is traffic generated by real people who are tricked into requesting web content (including digital advertising) without knowing about it.

Line 60:		Line 62:
	\| Incorrect requests \|\| During the analysis, we found that the impression came from an invisible element. For example, a user clicked on a link, but this click ended up in an invisible iframe that was located on top of the link. So the impression will be counted, but the real user did not see the advertisement and did not know where he was clicking.		\| Incorrect requests \|\| During the analysis, we found that the impression came from an invisible element. For example, a user clicked on a link, but this click ended up in an invisible iframe that was located on top of the link. So the impression will be counted, but the real user did not see the advertisement and did not know where he was clicking.

			<!--T:25-->
	Or we found that the impression was not initiated by the user, but by a script without the user’s knowledge..		Or we found that the impression was not initiated by the user, but by a script without the user’s knowledge..
	\|-		\|-

Admin at 12:03, 13 October 2023

2023-10-13T12:03:28Z

← Older revision		Revision as of 12:03, 13 October 2023
Line 38:		Line 38:

	<!--T:8-->		<!--T:8-->
	=== ~~Bot visits~~ (BV) ===		=== Invalid traffic (IVT) ===
			Invalid traffic consists of bot and scammers traffic.

	A bot is a program or automated script that requests web content (including digital advertising) without user involvement. It could be, for example, a browser on an infected computer that is part of a botnet, or a script written by a programmer that scrapes websites for some purpose.		A bot is a program or automated script that requests web content (including digital advertising) without user involvement. It could be, for example, a browser on an infected computer that is part of a botnet, or a script written by a programmer that scrapes websites for some purpose.

			Scammers traffic is traffic generated by real people who are tricked into requesting web content (including digital advertising) without knowing about it.

	<!--T:9-->		<!--T:9-->
Line 46:		Line 50:
	! Name !! Description		! Name !! Description
	\|-		\|-
	\| BV total \|\| Number of ~~clicks~~ made by bots ~~of all types~~.		\| IVT total \|\| Number of hits made by bots or caused by scammers.
	\|-		\|-
	\| Crawler \|\| Legitimate bots that honestly declare their botness through the user agent. These could be search engine bots indexing the web, social media bots, etc. Despite not having malicious intent, they cannot convert and are not the target audience, so they should be ignored.		\| Crawler \|\| Legitimate bots that honestly declare their botness through the user agent. These could be search engine bots indexing the web, social media bots, etc. Despite not having malicious intent, they cannot convert and are not the target audience, so they should be ignored.
Line 54:		Line 58:
	\| Automated \|\| Bots using headless browsers or automation tools like Selenium. The original purpose of such solutions is to automate software, website, application testing, etc. Then bot operators realized they could also use them for click fraud, view fraud, etc., and added them to their inventory.		\| Automated \|\| Bots using headless browsers or automation tools like Selenium. The original purpose of such solutions is to automate software, website, application testing, etc. Then bot operators realized they could also use them for click fraud, view fraud, etc., and added them to their inventory.
	\|-		\|-
	\| ~~iFrame~~ \|\| During the analysis, we found that the ~~page is~~ located on the ~~site in a small or inconspicuous element~~. ~~That is,~~ the impression will be counted, but the real user ~~will~~ not see, for ~~example~~, ~~the ad~~ and ~~will never be able to click~~ on it.		\| Incorrect requests \|\| During the analysis, we found that the impression came from an invisible element. For example, a user clicked on a link, but this click ended up in an invisible iframe that was located on top of the link. So the impression will be counted, but the real user did not see the advertisement and did not know where he was clicking.

			Or we found that the impression was not initiated by the user, but by a script without the user’s knowledge..
			\|-
			\| Bad reputation IP \|\| IPs from which only technical losses come. For example, someone set up a server in a data center, and using CURL, or another tool for http requests (and they are found in all programming languages), parses pages, and then clicks on advertising links using the same tool.
	\|}		\|}

Admin at 15:24, 4 October 2023

2023-10-04T15:24:51Z

← Older revision		Revision as of 15:24, 4 October 2023
Line 111:		Line 111:
	\| Visible page \|\| The number of visits when the page received focus, meaning it was open in the foreground rather than in the background tab of the browser.		\| Visible page \|\| The number of visits when the page received focus, meaning it was open in the foreground rather than in the background tab of the browser.
	\|-		\|-
	\| Active page \|\| The number of visits when there was at least minimal activity on the page. Activity is defined as clicks, touches, scrolls, ~~and~~ mouse movements.		\| Active page \|\| The number of visits when there was at least minimal activity on the page. Activity is defined as clicks, touches, scrolls, mouse movements.
	\|-		\|-
	\| Accepted page \|\| The number of visits when the time from page opening to its closure exceeded 15 seconds.		\| Accepted page \|\| The number of visits when the time from page opening to its closure exceeded 15 seconds.

Admin: Marked this version for translation

2023-10-04T15:13:53Z

Marked this version for translation

← Older revision		Revision as of 15:13, 4 October 2023
Line 100:		Line 100:
	\|}		\|}

			<!--T:21-->
	=== Behavioral analysis ===		=== Behavioral analysis ===
	Metrics based on the analysis of how the user behaved on the page.		Metrics based on the analysis of how the user behaved on the page.

			<!--T:22-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-