Metrics and groups - Revision history

Admin: /* Suspicious visits (SV) */

2026-09-30T11:08:13Z

Suspicious visits (SV)

← Older revision		Revision as of 11:08, 30 September 2026
Line 82:		Line 82:

	<!--T:36-->		<!--T:36-->
	SV is shown as five concrete reasons~~. The previous categories Suspicion of spoofing, Suspicion of automated and Suspicion of fraud are no longer shown. Proxy stays~~.		SV is shown as five concrete reasons.

	<!--T:12-->		<!--T:12-->
Line 102:		Line 102:
	\|}		\|}

	~~<!--T:26-->~~
	=== Viewability ===		=== Viewability ===
	Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).		Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).

Admin: Marked this version for translation

2026-09-30T11:03:31Z

Marked this version for translation

← Older revision		Revision as of 11:03, 30 September 2026
Line 6:		Line 6:
	https://www.loom.com/share/7ac94e262f1f4000a99decd8fe39fac7		https://www.loom.com/share/7ac94e262f1f4000a99decd8fe39fac7

			<!--T:35-->
	== User agent ==		== User agent ==
	User agent is a header that a browser, program, or application sends to a server when accessing a website. The user agent typically contains the browser name, its version, the engine on which the browser is based, the operating system and its version. The user agent can also contain the name and model of the mobile device on which it is running and some other information. In other words, it is a browser's business card.		User agent is a header that a browser, program, or application sends to a server when accessing a website. The user agent typically contains the browser name, its version, the engine on which the browser is based, the operating system and its version. The user agent can also contain the name and model of the mobile device on which it is running and some other information. In other words, it is a browser's business card.
Line 80:		Line 81:
	Suspicious clicks need an individual look. Conversions are the practical way to decide whether this traffic belongs with fraud or with good traffic.		Suspicious clicks need an individual look. Conversions are the practical way to decide whether this traffic belongs with fraud or with good traffic.

			<!--T:36-->
	SV is shown as five concrete reasons. The previous categories Suspicion of spoofing, Suspicion of automated and Suspicion of fraud are no longer shown. Proxy stays.		SV is shown as five concrete reasons. The previous categories Suspicion of spoofing, Suspicion of automated and Suspicion of fraud are no longer shown. Proxy stays.

Admin at 11:02, 30 September 2026

2026-09-30T11:02:43Z

← Older revision		Revision as of 11:02, 30 September 2026
Line 75:		Line 75:
	<!--T:10-->		<!--T:10-->
	=== Suspicious visits (SV) ===		=== Suspicious visits (SV) ===
	We see something suspicious in the analysis results, but it is not enough to confidently state that it is a bot. Possible reasons include ~~the user having~~ a harmless extension that ~~somehow~~ affects ~~our~~ checks, or ~~the user accessing~~ through a VPN.		We see something suspicious in the analysis results, but it is not enough to confidently state that it is a bot. Possible reasons include a harmless extension that affects the checks, or a visit through a VPN.

	<!--T:11-->		<!--T:11-->
	Suspicious clicks ~~require~~ an individual ~~approach, for example,~~ to ~~determine where to attribute suspicious~~ traffic ~~based on conversions - to fraudulent~~ or good traffic.		Suspicious clicks need an individual look. Conversions are the practical way to decide whether this traffic belongs with fraud or with good traffic.

			SV is shown as five concrete reasons. The previous categories Suspicion of spoofing, Suspicion of automated and Suspicion of fraud are no longer shown. Proxy stays.

	<!--T:12-->		<!--T:12-->
Line 87:		Line 89:
	\| SV total \|\| Number of suspicious clicks.		\| SV total \|\| Number of suspicious clicks.
	\|-		\|-
	\| Proxy \|\| Users accessing through VPN, proxy, or Tor. These are live clicks, but they come from non-targeted geo. ~~If you are buying traffic from a specific geo, and there are a lot of proxies on it, then~~ the ~~traffic is bad~~.		\| Proxy \|\| Users accessing through VPN, proxy, or Tor. These are live clicks, but they come from non-targeted geo.
			\|-
			\| Maybe automated \|\| Suspicion that the browser uses automation tools or user-agent spoofing techniques.
	\|-		\|-
	\| ~~Suspicion of spoofing~~ \|\| ~~We suspect that user agent spoofing techniques are being used in~~ the browser~~. If this metric is low, there is nothing to worry about. But if its percentage is high and you are not buying any specific mobile traffic, then there is a reason to think about it~~.		\| Timezone mismatch \|\| The time zone determined by the IP address does not match the time zone reported by the browser.
	\|-		\|-
	\| ~~Suspicion of automated~~ \|\| ~~We suspect that automation tools are being used in~~ the ~~browser~~.		\| Language mismatch \|\| The browser language does not match the Accept-Language header.
	\|-		\|-
	\| ~~Suspicion of fraud~~ \|\| ~~Other types of suspicious activity, such as a too-wide screen, can be the result of poor layout or an attempt to hide ads outside the screen~~.		\| Screen problems \|\|Screen resolution parameters are inconsistent.
	\|}		\|}

Admin at 07:37, 2 September 2026

2026-09-02T07:37:28Z

← Older revision		Revision as of 07:37, 2 September 2026
Line 3:		Line 3:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
			For a walkthrough of the statistics interface, watch the short video:
			https://www.loom.com/share/7ac94e262f1f4000a99decd8fe39fac7

	== User agent ==		== User agent ==
	User agent is a header that a browser, program, or application sends to a server when accessing a website. The user agent typically contains the browser name, its version, the engine on which the browser is based, the operating system and its version. The user agent can also contain the name and model of the mobile device on which it is running and some other information. In other words, it is a browser's business card.		User agent is a header that a browser, program, or application sends to a server when accessing a website. The user agent typically contains the browser name, its version, the engine on which the browser is based, the operating system and its version. The user agent can also contain the name and model of the mobile device on which it is running and some other information. In other words, it is a browser's business card.

Admin: Marked this version for translation

2026-06-24T13:52:56Z

Marked this version for translation

← Older revision		Revision as of 13:52, 24 June 2026
Line 93:		Line 93:
	\|}		\|}

			<!--T:26-->
	=== Viewability ===		=== Viewability ===
	Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).		Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).

			<!--T:27-->
	=== Viewability — display quality ===		=== Viewability — display quality ===
	Metrics in this group record whether the creative was rendered in the browser and whether the impression met the MRC viewability standard.		Metrics in this group record whether the creative was rendered in the browser and whether the impression met the MRC viewability standard.

			<!--T:28-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 112:		Line 115:
	\|}		\|}

			<!--T:29-->
	=== Attention ===		=== Attention ===
	Engagement metrics measure how long the creative or page stayed in the user's focus.		Engagement metrics measure how long the creative or page stayed in the user's focus.

			<!--T:30-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 126:		Line 131:
	\|}		\|}

			<!--T:31-->
	=== Video consumption ===		=== Video consumption ===
	Viewing-depth metrics apply to video creatives and show how much of the video the user watched.		Viewing-depth metrics apply to video creatives and show how much of the video the user watched.

			<!--T:32-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 176:		Line 183:
	\|}		\|}

			<!--T:33-->
	=== 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.
Line 272:		Line 280:
	\|}		\|}

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

Admin at 13:50, 24 June 2026

2026-06-24T13:50:43Z

← Older revision		Revision as of 13:50, 24 June 2026
Line 41:		Line 41:
	Invalid traffic consists of bot traffic and scammers traffic.		Invalid traffic consists of bot traffic and scammers traffic.

	<!--T:9-->		<!--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:10-->		<!--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.

	<!--T:11-->		<!--T:9-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 62:		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:12-->		<!--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..
	\|-		\|-
Line 70:		Line 70:
	\|}		\|}

	<!--T:13-->		<!--T:10-->
	=== Suspicious visits (SV) ===		=== Suspicious visits (SV) ===
	We see something suspicious in the analysis results, but it is not enough to confidently state that it is a bot. Possible reasons include the user having a harmless extension that somehow affects our checks, or the user accessing through a VPN.		We see something suspicious in the analysis results, but it is not enough to confidently state that it is a bot. Possible reasons include the user having a harmless extension that somehow affects our checks, or the user accessing through a VPN.

	<!--T:14-->		<!--T:11-->
	Suspicious clicks require an individual approach, for example, to determine where to attribute suspicious traffic based on conversions - to fraudulent or good traffic.		Suspicious clicks require an individual approach, for example, to determine where to attribute suspicious traffic based on conversions - to fraudulent or good traffic.

	<!--T:15-->		<!--T:12-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 93:		Line 93:
	\|}		\|}

	~~<!--T:16-->~~
	=== Viewability ===		=== Viewability ===
	Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).		Viewability is an assessment of the quality of ad creative display (banner, native, or video): whether it was actually rendered and seen by the user, how long it stayed in the visible zone, and how the user watched the video. Technically, Viewability runs inside the same script as antifraud: the user is checked for fraud first, then the fact and quality of the creative impression are recorded. Below are all Viewability metrics, grouped into three categories: display quality (Viewability), engagement (Attention), and viewing depth (Video consumption). Most metrics are counted per impression; rate metrics are calculated in aggregate and shown as percentages (0–100%).

	~~<!--T:17-->~~
	=== Viewability — display quality ===		=== Viewability — display quality ===
	Metrics in this group record whether the creative was rendered in the browser and whether the impression met the MRC viewability standard.		Metrics in this group record whether the creative was rendered in the browser and whether the impression met the MRC viewability standard.

	~~<!--T:18-->~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 115:		Line 112:
	\|}		\|}

	~~<!--T:19-->~~
	=== Attention ===		=== Attention ===
	Engagement metrics measure how long the creative or page stayed in the user's focus.		Engagement metrics measure how long the creative or page stayed in the user's focus.

	~~<!--T:20-->~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 131:		Line 126:
	\|}		\|}

	~~<!--T:21-->~~
	=== Video consumption ===		=== Video consumption ===
	Viewing-depth metrics apply to video creatives and show how much of the video the user watched.		Viewing-depth metrics apply to video creatives and show how much of the video the user watched.

	~~<!--T:22-->~~
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 161:		Line 154:
	\|}		\|}

	<!--T:23-->		<!--T:13-->
	=== Feature ===		=== Feature ===
	Some browser features that we detect.		Some browser features that we detect.

	<!--T:24-->		<!--T:14-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 183:		Line 176:
	\|}		\|}

	~~<!--T:25-->~~
	=== 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:26-->		<!--T:22-->
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 199:		Line 191:
	\|}		\|}

	<!--T:27-->		<!--T:15-->
	== Groups ==		== Groups ==
	Groups are parameters that allow you to answer the question "which?". From which countries were the clicks? Which browsers did users use?		Groups are parameters that allow you to answer the question "which?". From which countries were the clicks? Which browsers did users use?

	<!--T:28-->		<!--T:16-->
	=== Time ===		=== Time ===
	{\| class="wikitable"		{\| class="wikitable"
Line 218:		Line 210:
	\|}		\|}

	<!--T:29-->		<!--T:17-->
	=== Tags ===		=== Tags ===
	{\| class="wikitable"		{\| class="wikitable"
Line 233:		Line 225:
	\|}		\|}

	<!--T:30-->		<!--T:18-->
	=== Geo ===		=== Geo ===
	{\| class="wikitable"		{\| class="wikitable"
Line 252:		Line 244:
	\|}		\|}

	<!--T:31-->		<!--T:19-->
	=== Device ===		=== Device ===
	{\| class="wikitable"		{\| class="wikitable"
Line 280:		Line 272:
	\|}		\|}

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

Admin: Добавил Viewability

2026-06-24T13:32:51Z

Добавил Viewability

Show changes

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).