Entities
Identifications, users and visitors are entities. Devices and IP addresses are anchors on an identification: each has an identifier, but neither is an entity of the same kind. Entities explains how a check connects them. Identifiers explains how each identifier is built.Identification
An identification is one visitor check on a website. The snippet collects device, browser and network characteristics; ShieldLabs determines which signals fired, calculates a Risk Score and saves the result. The check records the device, visitor, network and, when a User HID is supplied, the account at a registration, login, payment or other action. Each accepted identification consumes one check from the plan’s included volume. A repeated regular call for the same user in the same browser within five minutes of the previous identification creates no new check while site pages remain open. A force check bypasses this pause. A browser call does not mean the score has already been calculated. The completed result arrives inidentification.scored and is saved in History.
The dashboard’s identification card shows one Identification. User, visitor, device and IP cards show their identification history.
Identification ID
Identification ID identifies one check. It connects the browser call to the completed result and to an action on your site, such as a registration, login or payment. The scored webhook usesdata.identification_id. A History record with type: "identification" returns the same value as id; pass it as {resource_id} to read the identification card. The identifier is issued when the check starts, before the score is ready. Send it to your server to retrieve the result.
The identifier points to a check. It does not authorize an action.
Use event_id to recognize repeated delivery of the same notification. Identification ID continues to identify the check.
The dashboard shows it on the identification card.
User
A user is an account in your application, identified by the User HID you supply. ShieldLabs groups checks with the same User HID within one site and shows their history, linked devices, visitors and IP addresses. Your application determines which account the identifier represents. An anonymous check is not associated with an account. Signing in later does not move earlier anonymous checks onto that account. User risk is a category based on this identification history. High-Risk Events are detected for the account: Multi-accounting, Account sharing, Impossible travel and Account takeover. The user’s current risk category appears in Analytics and on the user card. The scored webhook does not return it. A History user card returns it inrisk.band when risk.state is ok, with risk.as_of showing the calculation time. A History identification card can include the linked user’s category in identity_risk.user.
User HID
User HID is a stable account pseudonym. Your application creates it and passes it when checking a signed-in user. The same value lets ShieldLabs group one account’s checks within one site. Pass a hash or another stable pseudonym instead of a raw email address, login or account number. The snippet accepts the value as supplied and does not verify that it contains a hash. Your application determines which account it represents. The snippet sends User HID in an encrypted request with the check’s technical data. Encryption protects that request body. The server stores the supplied value and uses it to group checks. Inidentification.scored and on a History identification record, the field is user_hid. The snippet uses anonymous for an anonymous check; History represents the absence of an authenticated account as user_hid: null.
Pseudonymization
Replacing a direct account identifier, such as an email or login, with a stable token before sending it to ShieldLabs. Generate the User HID on your backend and use the same token for the same account across sessions. A server-side HMAC can create this token without exposing the original identifier or its secret to the browser. A plain hash of a guessable email does not make it secret. Pseudonymization preserves the ability to link account activity; it does not make that activity anonymous. See User HID generation.Visitor
A visitor is a site visitor ShieldLabs distinguishes using cookies and a device. ShieldLabs groups one visitor’s checks within one site and shows their history. This count is not a count of people: a different cookie or device can represent a different visitor. One visitor can be associated with several accounts when their checks use the same cookies and device. Visitor risk is a category based on this identification history. The visitor’s current risk category appears in Analytics and on the visitor card. The scored webhook does not return it. A History visitor card returns it inrisk.band when risk.state is ok, with risk.as_of showing the calculation time. A History identification card can include the linked visitor’s category in identity_risk.visitor.
Visitor ID
Visitor ID identifies a visitor. The server determines it from the device, cookie and previously stored links. When a cookie or device characteristics change, ShieldLabs compares the available data to retain the previous identifier where possible. A private browsing session has a separate cookie, so its Visitor ID may differ from regular browsing. A check without JavaScript, where the device and cookie are unavailable, receives a separate Visitor ID. Inidentification.scored and History, the field is visitor_id.
Anchors on an identification
A device, public IP and local IP accompany an identification. They have identifiers, and the analytics dashboard can open a card for a device or public IP. They are not entities in the same sense as an identification, user or visitor.Device ID
Device ID is an identifier ShieldLabs calculates using its own device fingerprinting technology, which analyzes hardware and software characteristics of the browser environment. Activity from the same device remains recognizable after cookies are cleared, in private browsing and after IP changes. In account history, this identifier connects visits that would look new based on their cookie or network address. It helps identify related accounts and repeat activity involving bonuses or trial periods. For High-Risk Events, ShieldLabs also matches devices within the account using its own algorithms. The characteristic sets account for platform differences and help recognize one physical device across browser-environment changes, even whendevice_id values differ. For example, Chrome and Microsoft Edge on one computer have different identifiers. This matching supports device recognition and reduces the risk of incorrectly merging different devices.
The identifier is returned in device_id in both identification.scored and History. An empty or zero value means a usable device identifier could not be obtained.
Public IP
Public IP is the public network address from which the check’s HTTP request reached ShieldLabs. Use it to associate checks by network address and analyze traffic geography. With a VPN or proxy, this is usually the exit server’s address. The country is determined from Public IP and used when analyzing network signals. Inidentification.scored, the address and country are public_ip.ip and public_ip.country. An empty public_ip.ip means the address could not be obtained.
A History identification record returns the address in public_ip. The identification-list filter is named ip; use it to find associated checks. An IP card uses the address as its id.
Local IP
Local IP is an additional network address. ShieldLabs uses two separate network checks: its own WebRTC session on its servers, and a browser network check through a separate server. The result is recorded separately from the Public IP from which the HTTP request reached ShieldLabs. The address exposes the network exit discovered by the browser check. It can differ from the request address, for example when the page uses a VPN or proxy but the browser check sees another path. The Local IP country is resolved separately. Comparing it with the Public IP country helps identify different network paths and contributes to the IP Mismatch signal. Inidentification.scored, the address and country are returned in local_ip.ip and local_ip.country. An empty local_ip.ip means the address could not be obtained. History does not support searches by Local IP.
Country
Country is the country determined from an IP address for this check. Public IP and Local IP countries are determined separately and can match or differ. Use them to analyze traffic geography and compare the check’s network characteristics. With anonymization services, Public IP’s country usually belongs to the exit server. An empty value means country data is unavailable. Inidentification.scored, the public address’s country is public_ip.country and the local address’s country is local_ip.country.
In History, the public address’s country is country. On one identification record, the local address’s country is local_country.
Identifiers on a check
Session ID and Cookie ID describe a browsing session and browser storage. They do not name an entity.Session ID
Session ID identifies one browsing session on a website. The snippet stores it inlocalStorage. Open site tabs for the same user share the value.
Use it to group checks from one browsing session. It is not an application login session.
A new Session ID is created on the next site load after the last open page is closed or left. Navigation within a single-page application without a full reload preserves the identifier. With only one tab open, a full-page load can result in a new identifier.
The field is session_id in identification.scored and on one History identification record.
Cookie ID
Cookie ID is an identifier the snippet creates in the browser and stores in the site’s own cookie and inlocalStorage.
It helps recognize repeated checks in the same browser storage. The server uses it with the device to determine Visitor ID. It is not an application login cookie.
If Cookie ID remains in either the cookie or localStorage, the snippet reuses it and restores it to the other storage location. A new identifier is created when no saved value can be retrieved. Private browsing has separate storage, so its identifier may differ from regular browsing.
The field is cookie_id in identification.scored and on one History identification record.
Domain
The registered website scope for an identification and its results. Key:domain. History can also include site_domain, the registered site scope when supplied. Domain-scoped API keys restrict the results you can read. See Domains.
Browser
The detected browser family for an identification. Key:browser. It describes the observed environment; bot or AI attribution is returned separately.
Operating system
The detected operating system for an identification. Key:os. The operating-system mismatch and not-detected risk signals describe separate checks on this environment.
Device type
The detected device class, such as desktop or mobile. Key:device_type. It describes the kind of device, while Device ID distinguishes its observed identity.
Risk Score
Risk Score measures the risk of one check from its detected signals. A higher number means higher assessed risk. Use it when reviewing registrations, logins, payments and other user actions. The ordinary scale is 0–100. The weights insignals can sum to more than the final Risk Score: each group’s combined contribution is capped, and the overall score does not exceed 100. Group caps are 60 for Proxy, 30 for Check Incomplete and 90 for Bad bot. Use the final Risk Score returned by ShieldLabs.
The separate value 999 marks an address restricted for exceeding the request rate. It is outside the ordinary visitor-risk scale. A recognized good bot scores 0.
In
identification.scored, the field is data.risk_score; the webhook has no separate risk-band field. A History identification card returns risk.score and risk.band when risk.state is ok. Its score is 0–100; the separate webhook marker 999 is not a History card score.
On an identification card, the score describes that check. The same labels, Trusted, Suspicious and Dangerous, on a user, visitor, device or IP describe a category calculated from its identification history.
Risk band
Risk band is the range containing one check’s Risk Score. It maps the number to Trusted, Suspicious or Dangerous so you can apply consistent handling to checks in the same range during registrations, logins, payments and other user actions.
The
identification.scored webhook has no separate band field: derive the band from data.risk_score. A History identification card returns the label directly in risk.band as trusted, suspicious or dangerous when risk.state is ok, alongside risk.score.
The value 999 is outside these ranges. Handle it separately before mapping a number to a label. Node.js provides riskBand(score) for mapping an ordinary score.
On an identification card, the label corresponds to that check’s score. On a user, visitor, device or IP, the same labels describe a category based on its identification history.
Trusted
The risk band for an identification with a Risk Score of 0–29. The observed check has low risk. Read the associated identity’s history and account events when the action also depends on account context. For a user, visitor, device or public IP, Trusted means its recorded identification history has not raised the current category. It does not mean all its checks scored 0. See current identity categories.Suspicious
The risk band for an identification with a Risk Score of 30–59. The check contains elevated-risk observations. Use its signals and the action’s context to choose an additional verification or review step. For a user, visitor, device or public IP, Suspicious means the share of suspicious identifications indicates elevated risk. The label summarizes that identity’s history, rather than requiring every check to be suspicious. See current identity categories.Dangerous
The risk band for an identification with a Risk Score of 60–100. The check contains high-risk observations. Review the signals and evidence before granting a sensitive action. The category describes this check, rather than establishing that an account has been compromised. For a user, visitor, device or public IP, Dangerous means the share of dangerous identifications indicates high risk. It takes priority when the history also qualifies as Suspicious. See current identity categories.Current risk category
The current risk category within a domain. It is calculated separately for Visitor ID (visitor_id), User HID (user_hid), Device ID (device_id) and public IP (public_ip). The labels are the same as the risk bands of one check: Trusted, Suspicious and Dangerous. The category describes accumulated risk for that key, rather than the Risk Score of one identification.
Use the category to assess the accumulated risk of a visitor, account, device or IP address. The calculation uses all available identifications within 90 days, rather than only those in the selected reporting period. The visitor, account, device and IP associated with one check can have different categories.
ShieldLabs calculates the share of checks with a Risk Score of 60 or more separately from the share scoring 30–59. If at least 5% of checks are dangerous, the category is Dangerous. Otherwise, if at least 5% are suspicious, the category is Suspicious. The remaining category is Trusted. The effect of one check depends on the total history size.
The anonymous value has no account risk category.
The category appears in Analytics and on the entity card. A History user, visitor, device or IP card returns it in risk.band when risk.state is ok, with its calculation time in risk.as_of. A History identification card can return the four linked categories in identity_risk.visitor, .user, .device and .ip. These categories are not fields of the scored webhook. Missing history or an unavailable category is not displayed as Trusted. See History card.
Visitor risk
The current risk category based on identifications linked to the same Visitor ID within a domain. It summarizes the visitor’s activity over time, beyond the latest check.User risk
The current risk category of an account identified by its User HID within a domain. It considers the account’s identification history across its visitors, devices and IPs. Anonymous activity has no authenticated user risk.Device risk
The current risk category based on identifications linked to the same Device ID within a domain. A device can be associated with more than one visitor or account.IP risk
The current risk category based on identifications associated with the same public IP within a domain. It summarizes observed traffic from that address, which can be shared by several devices and accounts.Risk signal
A risk signal is a named result of a device, browser or network check. It explains which characteristic was found in this identification, beyond the final number. Signals distinguish, for example, VPN use, browser automation and a recognized bot so you can handle those cases differently. Some signals add weight to the Risk Score. Others report a fact with zero weight and do not increase it. Read the final value fromrisk_score: the server can cap a group’s contribution, so the sum of weights in signals does not always equal the result.
In an identification.scored webhook, detection_flags reports the detections and signals contains their names and weights. A dashboard label can group several related detections.
Signal weight
The contribution recorded for a detected risk signal in an identification’ssignals array. Each entry has name, the exported signal slug, and weight, its reported contribution. A weight is numeric; a detection flag is true or false. A zero-weight detection can still provide useful context. Use the returned Risk Score for the final result; weights are not independent scores to add across checks.
Detection flags
Boolean fields indata.detection_flags of a notification containing the calculated risk. A separate list is unnecessary here: these are the same detections listed in the signal catalog below.
Connection type
Connection type is the network connection classification ShieldLabs determines for one check. Theconnection_type field contains one value.
Use it to group and compare direct, mobile, VPN, proxy, Tor and private-relay traffic. The value direct reports the classification result; it does not guarantee the absence of all risk indicators. Read the Risk Score and signals for risk.
The field is named
connection_type in both identification.scored and History.
Risk signals
The analytics dashboard displays signals under labels. When a label matches one signal, that signal appears directly below. When a label groups several signals, they are nested under it. See Risk Score for the difference between a risk signal, its weight and a detection flag.VPN
VPN is a signal that a virtual private network is being used. The service routes traffic through a VPN server, hiding the user’s original public IP. The site sees the service’s exit address. This signal also covers VPNs built into a browser or provided through an extension. ShieldLabs uses its own analytical research and network research data to identify VPNs. It compares IP information with network connection characteristics, STUN-check results and the browser time zone. This distinguishes VPN use from ordinary proxying. Inidentification.scored, the detection is returned in detection_flags.vpn. The webhook’s signals array lists this check’s signals and their weights: VPN uses name: "vpn" and weight: 30.
Proxy — dashboard label
Proxy is the dashboard label for a group of proxy detections, network-latency mismatches, Public IP and Local IP country differences, and operating-system inconsistencies. Proxies can change the visible IP or region, provide privacy, or route traffic. In abusive activity, they can evade restrictions and hide network connections between accounts. This group includes Proxy, Latency test, IP Mismatch and Operating System Mismatch. The label appears if at least one detection in the group fires. Read the individual results indetection_flags.
The signals array returns the individual signal weights. Their combined contribution to the Risk Score is capped at 60, even if the weights sum to more. The grouping itself adds no points.
On Overview, the Proxy tile shows a possible contribution of 30–60. An individual identification card shows the calculated contribution of the group.
Proxy — signal
Proxy is a signal that a request reaches the site through an intermediary server. ShieldLabs uses its own analytical and network research, combining IP information with evidence that the address belongs to proxy infrastructure. Inidentification.scored, the detection is returned in detection_flags.proxy. The webhook’s signals array lists this check’s signals and their weights: Proxy uses name: "proxy" and weight: 30.
Latency test
Latency test detects signs of an intermediary server through differences in network latency. ShieldLabs uses its own measurement method to compare TCP connection latency with the time required for a WebSocket exchange with the browser. A substantial difference can indicate an additional network segment between an intermediary server and the browser. The check takes several measurements of one connection and complements IP analysis. It helps detect signs of proxying even when network reference data does not identify the address as a proxy. Inidentification.scored, the detection is returned in detection_flags.latency_test. The webhook’s signals array lists this check’s signals and their weights: Latency test uses name: "latency_test" and weight: 60.
IP Mismatch
IP Mismatch detects signs of an intermediary server when the Public IP’s country differs from the country of the Local IP found by a browser network check. ShieldLabs runs its own WebRTC check: the browser opens a separate network path, exposing an address that can differ from the HTTP request’s address. This result is compared with a second independent network check. A difference between IP addresses alone is insufficient: the signal does not fire if their countries match. Both countries must be known. The check complements IP analysis and helps expose a different network exit even if network reference data does not identify the address as a proxy. The signal is not set when a VPN has already been detected. Inidentification.scored, the detection is returned in detection_flags.ip_mismatch. The webhook’s signals array lists this check’s signals and their weights: IP Mismatch uses name: "ip_mismatch" and weight: 45.
Operating System Mismatch
Operating System Mismatch detects an inconsistency between the operating system reported by the browser and the operating system visible from the network connection. ShieldLabs compares browser information with the OS family identified from the TCP/IP fingerprint of the connection that reaches its server. An intermediary server can terminate the TCP connection itself. The browser’s reported OS can then differ from the OS family identified from that server’s network characteristics. This mismatch indicates possible proxying or environment spoofing and helps detect an intermediary connection even when network reference data does not identify the IP as a proxy. The signal is not set when a VPN has already been detected. Inidentification.scored, the detection is returned in detection_flags.os_mismatch. The webhook’s signals array lists this check’s signals and their weights: Operating System Mismatch uses name: "os_mismatch" and weight: 60.
Private Relay
Private Relay is a signal that a private relay service, such as iCloud Private Relay, is being used. The service passes requests through intermediary infrastructure to hide the user’s original public IP. The site sees the service’s exit address. ShieldLabs uses its own analytical and network research to analyze the IP and evidence that it belongs to the service’s infrastructure. This distinguishes private relay use from ordinary proxying. Inidentification.scored, the detection is returned in detection_flags.private_relay. The webhook’s signals array lists this check’s signals and their weights: Private Relay uses name: "private_relay" and weight: 30. The corresponding connection_type value is private_relay.
Tor Network
Tor Network is a signal that a request arrived through a Tor exit node. Tor routes traffic through a chain of nodes to hide the user’s original public IP. The site sees the exit node’s address. ShieldLabs uses its own analytical and network research to analyze the IP and evidence that it belongs to a Tor exit node. This distinguishes Tor from ordinary proxying. Inidentification.scored, the detection is returned in detection_flags.tor. The webhook’s signals array lists this check’s signals and their weights: Tor Network uses name: "tor" and weight: 99. The corresponding connection_type value is tor.
Check Incomplete — dashboard label
Check Incomplete is the dashboard label for a group of incomplete-check detections. It indicates that some checks did not finish or that the data was insufficient to identify certain environmental characteristics. Incompleteness alone does not establish proxying or environment spoofing. This group includes Check Incomplete, Network Check Incomplete and Operating System Not Detected. The label appears if at least one detection in the group fires. Read the individual results indetection_flags.
The signals array returns the individual signal weights. Their combined contribution to the Risk Score is capped at 30, even if the weights sum to more. The grouping itself adds no points.
On Overview, the Check Incomplete tile shows a possible contribution of 0–30. An individual identification card shows the calculated contribution of the group.
Check Incomplete — signal
Check Incomplete indicates that ShieldLabs did not receive expected browser data required for the device fingerprint, or received an error while collecting it. The check is saved with the available information. The signal has zero weight and does not increase the Risk Score. It is suppressed for recognized good bots. Inidentification.scored, the detection is returned in detection_flags.check_incomplete. The webhook’s signals array lists this check’s signals and their weights: Check Incomplete uses name: "check_incomplete" and weight: 0.
Network Check Incomplete
Network Check Incomplete indicates that ShieldLabs had not received confirmation of a successful STUN network check when it calculated the result. The browser sends a separate UDP STUN request to ShieldLabs, independently of HTTP, to check another network path and expose the address on it. If the exchange is unconfirmed, possible causes include network restrictions, blocked UDP, browser settings or connection interference. Missing confirmation alone does not establish proxying. The signal is not set when a VPN has already been detected. Inidentification.scored, the detection is returned in detection_flags.network_check_incomplete. The webhook’s signals array lists this check’s signals and their weights: Network Check Incomplete uses name: "network_check_incomplete" and weight: 30.
Operating System Not Detected
Operating System Not Detected indicates that ShieldLabs could not identify the OS family from browser information or the connection’s TCP/IP fingerprint. Without that information, the reported OS cannot be compared with the network characteristics. Possible causes include insufficient data, environmental characteristics, or interference with the browser or network connection. The signal does not establish the cause. The signal is not set when a VPN has already been detected. Inidentification.scored, the detection is returned in detection_flags.os_not_detected. The webhook’s signals array lists this check’s signals and their weights: Operating System Not Detected uses name: "os_not_detected" and weight: 30.
Anti-Detect Browser
Anti-Detect Browser is a signal of an anti-detect browser or device fingerprint spoofing. An anti-detect browser presents altered device and browser characteristics so a site cannot associate the visit with the original environment. ShieldLabs uses its own analytical research and technical signatures to compare characteristics from different components of the browser environment. When WebGL and WebGPU are available, the check compares the GPU vendor and architecture, reported hardware and graphics capabilities. It also analyzes characteristic environmental behavior. These comparisons help detect masking even when the reported browser characteristics have changed. Inidentification.scored, the detection is returned in detection_flags.anti_detect_browser. The webhook’s signals array lists this check’s signals and their weights: Anti-Detect Browser uses name: "antidetect_browser" and weight: 60.
Banned IP
Banned IP indicates a temporary IP-address restriction for exceeding the permitted request rate. ShieldLabs restricts an address that sends more than 15 requests to the identification ingestion service within a one-minute window. The restriction lasts 10 minutes. The value 999 marks this restriction; it is not an ordinary visitor risk score. Inidentification.scored, the flag is detection_flags.banned_ip. The same webhook’s signals array lists the check’s signal names and weights. Banned IP uses name: "banned_ip", and the check’s Risk Score is 999. HTTP 429 indicates that the rate was exceeded. A History record and webhook are not always created. A domain-wide restriction does not set this signal.
Incognito mode
Incognito mode indicates that a check ran in a private browsing session. Its storage is separate or temporary, and its cookies are not shared with regular browsing. ShieldLabs recognizes private sessions by checking the behavior and restrictions of browser storage. The signal is set when the check recognizes a private session. It is not set when the evidence is insufficient or when a good bot is recognized. The signal has a weight of 0. It describes the check’s context without adding to the Risk Score. In private browsing, ShieldLabs continues to recognize the device through its fingerprint rather than cookies. Device ID is calculated on the server from environment characteristics. Visitor ID also depends on the private session’s cookie and may differ from regular browsing. Inidentification.scored, the flag is detection_flags.incognito. The same webhook’s signals array lists the check’s signal names and weights. Incognito mode uses name: "incognito" and weight: 0.
Good bot — dashboard label
Good bot is the dashboard label for recognized search bots, AI bots and AI browsers. The group accounts for recognized search and AI traffic separately from suspicious automation and environment spoofing. It includes Search bot, AI Bot and AI Browser. The label appears if at least one detection in the group fires. Read the individual results fromdetection_flags.search_bot, detection_flags.ai_bot and detection_flags.ai_browser. There is no separate webhook flag for the group.
The signals array returns the individual signal weights. All three detections have zero weight. A recognized check receives a Risk Score of 0. Accompanying masking, automation and incomplete-check signals are suppressed. The grouping itself adds no points.
On Overview, these visits are counted separately from risky visitors. The identification card shows the specific detection. If the provider is known, its name is returned in search_bot_owner, ai_bot_owner or ai_browser_owner and displayed beside the detection.
AI bots
AI bots is a signal of a recognized AI bot: a program that retrieves site pages for artificial-intelligence tasks. It can collect content or request a page to prepare an answer for someone. Browsers with AI functionality belong to the separate AI Browser signal. ShieldLabs recognizes supported clients from the name presented in the request. Some supported clients can also be recognized through published provider IP addresses. AI search bots belong to Search bot. A client name alone does not prove that the request came from the named provider. Inidentification.scored, the detection is returned in detection_flags.ai_bot. The webhook’s signals array lists this check’s signals and their weights: AI bots uses name: "ai_bot" and weight: 0. If the provider is known, its name is returned in ai_bot_owner. The dashboard groups the signal under Good bot. A recognized check receives a Risk Score of 0, and accompanying masking, automation and incomplete-check signals are suppressed.
Search bot
Search bot is a signal of a recognized search crawler that visits site pages for indexing. It also includes supported bots that index pages or collect content when they are not classified as AI bots or AI Browser. AI search bots belong to Search bot. ShieldLabs recognizes supported clients from the name presented in the request. For some search bots, it also uses network information, comparing IP ownership data with the bot name or the address’s organization. A client name alone does not prove that the request came from the named provider. Inidentification.scored, the detection is returned in detection_flags.search_bot. The webhook’s signals array lists this check’s signals and their weights: Search bot uses name: "search_bot" and weight: 0. If the provider is known, its name is returned in search_bot_owner. The dashboard groups the signal under Good bot. A recognized check receives a Risk Score of 0, and accompanying masking, automation and incomplete-check signals are suppressed.
AI browser
AI browser is a signal of a supported browser platform through which a program can open pages, navigate a site and perform actions. A client that only retrieves pages to prepare an answer or collect content belongs to AI bots instead. ShieldLabs sets the signal after successfully verifying a cryptographic request signature against the platform’s keys. The signature establishes that the visit uses the platform’s infrastructure. A reported browser name is insufficient, as is provider information without confirmation of the platform’s infrastructure. The signature attributes the visit to the platform, rather than the person or model controlling it. Inidentification.scored, the detection is returned in detection_flags.ai_browser. The webhook’s signals array lists this check’s signals and their weights: AI browser uses name: "ai_browser" and weight: 0. If the provider is known, its name is returned in ai_browser_owner. The dashboard groups the signal under Good bot. A recognized check receives a Risk Score of 0, and accompanying masking, automation and incomplete-check signals are suppressed.
Timezone Mismatch
Timezone Mismatch detects inconsistencies between the browser’s time zone and the public IP location. ShieldLabs compares the browser’s reported time zone and time offset with the time zone, local time and country of that address. A matching UTC offset alone is insufficient: the signal can fire when time zones differ or the browser’s zone does not match the IP’s country. Alternative names for the same time zone are taken into account. The mismatch helps identify inconsistencies between browser settings and the visible network location that can accompany a masked connection. The signal is not set when a VPN has already been detected. Inidentification.scored, the flag is detection_flags.timezone_mismatch. The same webhook’s signals array lists the check’s signal names and weights. Timezone Mismatch uses name: "timezone_mismatch" and weight: 10.
Bad bot — dashboard label
Bad bot is the dashboard label for suspicious automation and environment spoofing. It indicates signs of programmatic browser control, altered device characteristics, or unavailable browser capabilities required for the check. This group includes Browser Automation, Device spoofing and JavaScript Disabled. The label appears if at least one detection in the group fires. Read the individual results indetection_flags.browser_automation, detection_flags.device_spoofing and detection_flags.javascript_disabled. There is no separate webhook flag for the group.
The signals array returns the individual signal weights. Each of the three detections has a weight of 90. Their combined contribution to the Risk Score is capped at 90, even if the weights sum to more. The grouping itself adds no points. Other signals retain their contributions to this check.
On Overview, the Bad bot tile shows a contribution of 90. These visits are counted separately from other visitors. An individual identification card shows the calculated contribution of the group.
Browser Automation
Browser Automation indicates detected programmatic control of a browser. ShieldLabs checks technical signs of automation in the browser environment. This helps identify automated activity, such as bulk registrations or repeated login attempts. The signal is suppressed for a recognized good bot. Inidentification.scored, the flag is detection_flags.browser_automation. The same webhook’s signals array lists the check’s signal names and weights. Browser Automation uses name: "browser_automation" and weight: 90.
The dashboard groups it under Bad bot with Device spoofing and JavaScript Disabled. The group’s combined contribution to the Risk Score is capped at 90, even if the weights sum to more. Grouping adds no extra points.
Device spoofing
Device spoofing detects altered device characteristics. ShieldLabs compares the reported operating system, browser and hardware with other evidence from the same environment: graphics, platform, fonts, voice components, browser audio-system parameters and the TLS connection fingerprint. The signal fires when these characteristics contradict each other and do not match the reported device. An ordinary difference between characteristics alone does not trigger it. One or more contradictions produce one Device spoofing signal with a weight of 90. Additional contradictions do not increase its weight. Inidentification.scored, the detection is returned in detection_flags.device_spoofing. The webhook’s signals array lists this check’s signals and their weights: Device spoofing uses name: "device_spoofing" and weight: 90. The dashboard groups the signal under Bad bot, whose combined contribution is capped at 90.
JavaScript Disabled
JavaScript Disabled indicates that JavaScript is disabled or browser capabilities required for the check are unavailable. ShieldLabs detects disabled JavaScript and restrictions in the browser environment, including an unavailable WebRTC API. The signal can appear even when JavaScript runs if required capabilities are restricted. It helps identify restricted environments that can accompany connection masking and automation. The signal is suppressed for a recognized good bot. Inidentification.scored, the flag is detection_flags.javascript_disabled. The same webhook’s signals array lists the check’s signal names and weights. JavaScript Disabled uses name: "javascript_disabled" and weight: 90.
The dashboard groups it under Bad bot with Browser Automation and Device spoofing. The group’s combined contribution to the Risk Score is capped at 90, even if the weights sum to more. Grouping adds no extra points.
AI traffic
AI agents and assistants describe how an AI application works. The AI Bot and AI Browser signals describe the supported traffic ShieldLabs recognizes.AI agent
An AI application that plans and performs tasks on someone’s behalf, such as navigating pages or completing a form. An agent can control a browser or retrieve content directly. ShieldLabs reportsai_browser when it recognizes a supported AI browser platform; a recognized AI bot or crawler uses ai_bot. These signals identify the detected client category, rather than the person or AI model controlling it. See AI agent detection.
AI assistant
An AI application that answers questions, summarizes information or helps with a task. It can request pages from your website to prepare an answer. ShieldLabs recognizes supported assistant retrieval traffic through theai_bot signal; activity through a supported AI browser platform can use ai_browser. An assistant can also perform agent-like tasks, so the application name alone does not determine the signal. Read the provider and identity evidence alongside the detection. See AI assistant detection.
High-Risk Events
High-Risk Events describe account activity across identifications. A scored webhook can include three account-event evaluations inhre; multi-accounting uses its own group-change event.
High-Risk Event
A High-Risk Event is an event ShieldLabs detects using more than 47 rules and heuristics, comparing device, browser and network characteristics with account history. There are four event types: Multi-accounting, Account sharing, Impossible travel and Account takeover. A detected event receives Medium or High confidence. This reflects the system’s confidence in the detection and is assessed separately from the Risk Score of an individual check. Pass the same User HID when checking the same authenticated account. Events and their supporting evidence are available in the analytics dashboard: open the account card to inspect event clusters and connection graphs. Account sharing, Impossible travel and Account takeover results are delivered inidentification.scored. Multi-account group changes use the separate hre.multi_account.changed webhook, which requires additional enablement. See High-Risk Events.
Cluster
A cluster is a group of related accounts, devices or checks that ShieldLabs automatically forms using its own matching algorithms, rules and heuristics. Connections are identified using ShieldLabs’ device fingerprinting technology, browser and network characteristics, and account history. A cluster’s contents depend on the event. For Multi-accounting, it shows related accounts; for Account sharing, devices used by one account. For Impossible travel, it shows the compared checks, distance and time between them. For Account takeover, it shows the current check and the historical observations used to detect the event. A cluster explains the detection: which connections or changes were found and which data supports the result. In the analytics dashboard, open an account card by User HID, select an event cluster and inspect its connection graph. See High-Risk Event clusters.Cluster ID
The identifier of a High-Risk Event cluster. Use it to associate information and updates that belong to the same cluster. In an event result insideidentification.scored, cluster_id can be null because no cluster reference was supplied. This does not, by itself, cancel the detection: interpret the result using status and level.
In hre.multi_account.changed, cluster_id identifies a multi-account group. The identifier stays the same when the group’s membership expands or contracts unambiguously. A split or merge can resolve previous clusters and create new clusters with different identifiers.
Use event_id to recognize a repeated delivery and revision to order changes to one group.
Multi-account group creation and updates
The creation, membership changes and resolution described here use theaction field of hre.multi_account.changed.
A multi-account group is created when a complete recalculation assembles an account group that did not previously exist, or when a previously resolved group becomes active again. This episode receives a new cluster_id. ShieldLabs sends hre.multi_account.changed with action: "detected", detected: true, level: "medium" or "high", and previous_revision: null. Both user_hids and added_user_hids contain the complete current membership. removed_user_hids is empty.
An account leaves a continuing group when the membership reduction is unambiguous: the remaining members still form the same group. The cluster_id stays the same. The event has action: "updated"; removed_user_hids lists the accounts removed by this change, and user_hids lists the current membership. This difference applies only to that notification. The next message does not repeat those removals, and there is no separate list of every account ever removed.
An unambiguous membership expansion also uses action: "updated", with new accounts in added_user_hids. If membership stays the same but confidence or the rules version changes, ShieldLabs also sends updated with the same cluster_id. Both change lists are empty in that case.
Multi-account group resolution, splits and merges
An account’s connection to a multi-account group remains for 90 days after its last observation on a shared characteristic. When a complete recalculation finds too few remaining members for the group to continue, the previouscluster_id is resolved. ShieldLabs sends hre.multi_account.changed with the same cluster_id, action: "resolved", detected: false and level: null.
Both user_hids and removed_user_hids contain the entire former membership, rather than one removed account. The notification is sent on the next complete recalculation if hre.multi_account.changed delivery is enabled. An incomplete calculation does not send a resolution. No separate updated message with a single removed account is sent in this case.
The same resolution is sent when a complete recalculation no longer confirms the previous group for another reason. An account from a resolved cluster can remain in another active cluster: inspect the state of each active cluster_id separately.
When a split or merge prevents an unambiguous continuation of the previous group, each replaced cluster sends its own resolved notification. Resulting groups send separate detected notifications and receive different cluster_id values. A new group’s notification does not include the previous identifier. These notifications are independent and can arrive in any order. Recalculating the same membership, confidence and rules version does not create another notification.
Account-sharing clusters
An Account sharing cluster contains devices used by one authenticated account. Devices observed on that account during the last 90 days are counted. A new device enters the cluster on the check where it appears. The result is delivered inidentification.scored, under account_sharing, with a cluster_id when a cluster reference has been published. Account sharing has no separate webhook.
A device stops counting 90 days after its last visit. No notification is sent at that moment. If the event no longer qualifies after the device is removed, the stored result is recalculated without an identification and without a cluster_id.
The account’s next check sends an ordinary identification.scored event for that check, with its current result in account_sharing. If Account sharing is no longer confirmed, status is evaluated and both level and cluster_id are null. The previous cluster_id is not included. Null level and cluster_id mean no active Account sharing result was found on this check.
If Account sharing remains confirmed and a cluster reference is published, the cluster_id corresponds to the new membership. After the device set changes, the next published reference has a different identifier.
Impossible-travel clusters
An Impossible travel cluster contains two checks of one authenticated account: the previous check and the current check. The identifier is calculated from that pair. Each new pair receives its owncluster_id.
The result is delivered in identification.scored, under impossible_travel, with a cluster_id when the event is confirmed. There is no separate webhook. The pair’s membership does not change over time, and no member-removal or cluster-resolution notification is sent. If no event is found on a check, level and cluster_id are null. The previous cluster_id is not included in that notification.
Account-takeover clusters
An Account takeover cluster contains the current check and the authenticated account history used for comparison. It does not assemble a group of other accounts. A cluster is created when the check detects the event. A return visit from an already familiar device does not, by itself, create a new cluster. The result is delivered inidentification.scored, under account_takeover, with a cluster_id when a cluster reference has been published. There is no separate webhook. Member removal and resolution after 90 days do not apply here. If no event is found on a check, level and cluster_id are null. The previous cluster_id is not included in that notification.
Multi-accounting
Multi-accounting detection identifies related accounts on the same site. ShieldLabs uses more than seven rules and heuristics developed by our data analytics team. They compare digital identifiers, device and network characteristics, and account activity history. Cluster. ShieldLabs’ system completely reassesses connections between all authenticated accounts on one site at least once every 10 minutes to detect Multi-accounting. Group changes are delivered through the separatehre.multi_account.changed webhook: a group is detected, updated or resolved. This webhook requires additional enablement.
Main signals. IP, Cookie and Device ID. ShieldLabs recognizes devices using its own Hardware ID technology, which analyzes hardware characteristics and helps match activity from one device across browser changes. Browser and operating system are additional characteristics.
Confidence. Medium and High reflect confidence in the connection between accounts. The level depends on the combination and consistency of the evidence.
Display threshold. In the analytics dashboard, select the minimum number of related accounts to display for an event, starting at three.
Connection graph. Open the user card by User HID to inspect related accounts and the data used to connect them into a cluster.
Account sharing
Account sharing detection identifies one account being used on different devices. ShieldLabs uses more than 10 rules and heuristics to detect Account sharing and reduce false positives. Cluster. Clusters are built only for authenticated accounts. Devices observed on the account in the last 90 days are counted. A new device being added to the account is the event. The result is delivered in that check’s webhook when the new check occurs. Account sharing has no separate webhook. Main signals. IP, Cookie and Device ID. Device ID uses ShieldLabs’ own Hardware ID technology, which analyzes device hardware characteristics. Browser and operating system are additional characteristics. Multiple browsers on one physical device count as one device to reduce false positives. Confidence. Medium and High depend on the system’s confidence that different devices are being used to access the account. Display threshold. In the analytics dashboard, select the minimum number of different devices to display for an event, starting at four. Connection graph. The account card, identified by User HID, provides a dashboard graph of the account’s devices and the evidence used to group them into a cluster.Impossible travel
Impossible travel detection identifies an account appearing in two places so far apart and so close in time that one person could not have traveled between them. ShieldLabs uses more than 10 rules and heuristics to detect Impossible travel and reduce false positives. Cluster. This event does not create a group of other accounts. It evaluates only the authenticated account. The event consists of two clean checks for that account, no more than 48 hours apart, whose distance and timing are inconsistent with travel. The signal appears whenever such a pair occurs and is delivered in the new check’s webhook. There is no separate webhook. If VPN, Proxy, Tor or Private Relay is detected, no Impossible travel event is created. Main signals. Address coordinates, time between checks, Cookie and Device ID. Device ID uses ShieldLabs’ own Hardware ID technology to analyze hardware characteristics. Browser and operating system also contribute to this comparison. A recognized same-device result is not shown as travel even if the mapped country changes, so geolocation errors and network changes are not mistaken for movement. Two different cookies that had already appeared on the account by the time of their respective checks count as two devices. Confidence. Medium or High requires a distance of at least 300 km and a speed above 800 km/h. High requires different devices plus additional supporting evidence: a speed above 1,000 km/h over at least 500 km, both checks within a 30-minute window, or a country change. If the devices cannot be compared, confidence is no higher than Medium. Connection graph. The account card, identified by User HID, provides a dashboard graph of the account and the two checks used for the event. Each evaluation of a qualifying pair forms a separate cluster.Account takeover
Account takeover detection identifies an account visit that differs from its usual activity and may indicate access by another person. ShieldLabs uses more than 20 rules and heuristics. They compare environmental changes with account history and help reduce false positives. Cluster. The event belongs to an authenticated account and does not form a group of other accounts. The check compares the current visit with account history in sequence, considering conditions that support or exclude the event. If the device is recognized as familiar from the available account history, a country or network change alone does not trigger Account takeover. If a visit from a new device meets the detection conditions, ShieldLabs creates an event card. Subsequent visits from an already familiar device do not, by themselves, create another event. A detected result is delivered in the current check’s webhook. There is no separate Account takeover webhook. Main characteristics. Device, Cookie, the account’s operating-system, country and IP history, and indicators of connection or browser masking. ShieldLabs uses its own Hardware ID technology to analyze hardware characteristics for device recognition. Changing browsers on the same recognized device does not, by itself, trigger Account takeover. Confidence. Medium and High reflect confidence in the event. The level depends on the combination of device, browser-context and network changes relative to account history. Connection graph. The user card, identified by User HID, provides a dashboard graph of the current check and the historical observations used in the evaluation.Medium / High confidence
Medium and High are confidence levels for a High-Risk Event. The level depends on the combination and consistency of supporting evidence. Interpret the evidence in the context of the event type: Multi-accounting, Account sharing, Impossible travel or Account takeover. A larger number of accounts or devices does not, by itself, explain High confidence. Confidence belongs to that event and is returned inlevel. It is separate from the 0–100 Risk Score of one check.
Analytics
Dashboard views and metrics for investigating traffic and identities. Read each metric’s scope: selected-period activity and current risk describe different things.Analytics dashboard
The Analytics dashboard is where you investigate traffic, checks and related accounts. It also lets you connect sites, manage keys and webhooks, and monitor identification usage and your plan. Overview summarizes the selected period and domain. Analytics lets you filter checks, visitors, users, devices and public IPs and open their cards. An identification card shows one check’s result. A user, visitor, device or IP card shows its history and current risk category. The user card includes High-Risk Events, their clusters and relationship graphs that help explain the detection. Viewing, filtering and exporting saved results does not consume identifications. Start with Overview.Overview
Overview summarizes the Analytics dashboard for the selected period and one domain or all domains in the account. Use it to notice changes in Traffic quality and open related checks or accounts in Analytics. Traffic quality uses a 0–100 scale: a lower value means less risky checked traffic. It measures how risk is concentrated across checks in the selected period. The screen also shows identification counts split into Trusted, Suspicious and Dangerous, users, visitors, Risk signals and High-Risk Events at Medium and High confidence. High-Risk Event counts represent accounts with saved positive evidence during the selected period. Incomplete coverage makes this a confirmed minimum. An unavailable metric or accumulating data does not mean no event occurred. Visitors are split into Trusted, Risky visitors, Good bots and Bad bots. Risky visitors combines Suspicious and Dangerous, excluding visitors already counted as Good bots or Bad bots. Traffic is also grouped by country, browser, operating system, connection type, channel and device type, with volume and Traffic quality for each group. Refresh the screen and compare with the previous period where data is available. Supported metrics and rows open the corresponding Analytics activity. The latest identifications scoring at least 60 are recent checks, rather than a ranking of the highest scores. See Dashboard overview.Entity card
An Entity card is the Analytics dashboard card for one User, Visitor, Device or Public IP. It combines the current risk category, checks in the selected period and related data, showing how one check relates to that account, visitor, device or address’s history. Open it from Analytics, an Identification card or a linked identifier. The header shows the identifier, First seen, Last seen and the current Trusted, Suspicious or Dangerous category. Current risk as of shows when the category was calculated, helping assess freshness, especially with incomplete data. If the category cannot be calculated, the dashboard shows Risk unavailable rather than Trusted. The current category uses the identifier’s history. First seen, Last seen, the Trusted, Suspicious and Dangerous split, and the Identifications list refer to the selected period. That split can differ from the current category. The current category is calculated separately from one check’s Risk Score. Details contains counters for linked identifiers, addresses and environment attributes. The available counters depend on the card: Session ID, Device, Visitor, User, Cookie ID, Public IP, Local IP, countries, Connection type, OS, Browser and Device type can appear. Expand a counter to inspect values and associated identification counts. Linked User, Visitor, Device and Public IP values open their own Entity cards. A shared Public IP alone does not establish that accounts belong to one person. User cards also show High-Risk Event labels at Medium or High confidence, event clusters and a relationship graph. The graph uses saved event evidence with a window of up to 90 days; changing the Analytics period does not rebuild it. Incomplete data can leave only part of the evidence visible. Read the completeness notice when investigating. An empty graph can mean no cluster is selected. Neitheridentification.scored nor the History API returns the dashboard card itself. See Entity cards.
Identification card
An Identification card shows one check in the Analytics dashboard: its Risk Score, detected signals, identifiers, device, network and traffic source. Open it by Identification ID from Analytics, the latest checks scoring at least 60 on Overview, or the Identifications list on an Entity card. The header shows Identification ID and the check time, Seen. The card shows that check’s Risk Score and Trusted, Suspicious or Dangerous label. The separate value 999 means Banned IP and is outside those ranges. Risk signals lists signal names and weights. If none fired, it shows No risk signal fired. A label such as Proxy or Bad bot can group several detections. The displayed group weight is already included in the Risk Score; do not add it again. A zero-weight signal provides context. A recognized good bot can have its company name beside the signal. Details shows Visitor ID, Device ID, Cookie ID, Session ID, User HID and Domain. Visitor ID, Device ID and User HID open the corresponding Entity cards. An anonymous check has no associated User. Visitor risk, User risk, Device risk and IP risk show the identifiers’ current categories, rather than their categories when this check occurred. A dash means the identifier is absent or its category is unavailable. These categories can differ from each other and from this check’s Risk Score. High-Risk Event labels appear separately. Open the user’s Entity card for account clusters and the graph. Device and network shows Device type, OS, Browser, Public IP, Country, Local IP, Local country and Connection type. Public IP opens its Entity card. Traffic source shows Channel, Referrer, Entry page, Click ID type, UTM Source, UTM Medium, UTM Campaign, UTM Content and UTM Term. An empty field means no value is available. Read the same check in History using its Identification ID. Neitheridentification.scored nor the History API returns the dashboard card itself. See Identification card.
High-Risk Event clusters
High-Risk Event clusters is the cluster list on a user’s Entity card and the graph of the selected cluster. It covers Multi-accounting, Account sharing, Impossible travel and Account takeover. The graph shows saved evidence connecting cluster participants. The Clusters list shows the event type, Medium or High confidence and domain. Confidence describes the event and does not contribute to the check’s Risk Score. Until a cluster is selected, the graph asks you to choose one from Clusters. The graph depends on the event. Multi-accounting shows related accounts and what connects them; a shared Public IP alone does not establish that they belong to one person. Account sharing shows device observations. Impossible travel shows the compared checks. Account takeover shows the current check and the historical observations used for the detection. Select a node to view available details or open a related Entity card or Identification card. The graph uses the latest saved evidence, with a 90-day evidence window. Changing the Analytics period does not rebuild it. Incomplete data can leave only part of the evidence visible; read the completeness notice when investigating. Webhooks and the History API do not return this graph. See High-Risk Event clusters.Traffic quality
Traffic quality is an aggregate traffic-risk metric on a 0–100 scale. A lower value means the checked traffic had less risk. The metric describes the selected period, and comparison with the previous period helps reveal changes in traffic quality. On Overview, the metric covers the selected domain or all domains in the account. It is also available by country, browser, operating system, connection type, channel and device type to help identify higher-risk traffic groups. Select a row to open the matching identifications in Analytics, then inspect individual Risk Scores and detected signals. ShieldLabs calculates the metric from the distribution of identifications across Risk Score bands. A check scoring 60 or more receives full weight; a check scoring 30–59 receives half weight. Checks below 30 do not increase the weighted sum but are included in the total number of checks. A weighted sum equal to half the total number of checks corresponds to the top of the scale, 100. The result is capped at 100 and rounded to a whole number. It describes the concentration of risk across checks, rather than the percentage of dangerous visitors. Read the metric together with the number of checks. If the selected scope contains no checks, the metric is 0. Risk Score describes one identification. Current identity categories and High-Risk Event confidence are calculated separately. Traffic quality is available in the dashboard; neither webhooks nor History returns it.Identifications
Identifications counts saved checks in the selected period for one domain or all domains in the account, with the active filters. Each saved check adds one. A repeated check of the same visitor also adds one; a call that creates no check is not counted. This is not a count of people or Visitor IDs. Unique visitors is counted separately. On Overview, the adjacent Trusted, Suspicious and Dangerous split uses these checks’ Risk Scores, rather than the current visitor or account category. The count and tiles open the matching checks in Analytics. On Users, Unique visitors, Devices and Public IPs, the Identifications column counts that identifier’s checks in the same period. The counter describes the reporting period, rather than remaining plan volume. This dashboard aggregate is not returned in webhooks or the History API.Unique visitors
Unique visitors counts distinct Visitor IDs in the selected period for one domain or all domains in the account, with the active filters. Repeated checks of one Visitor ID do not increase the count. This is not a count of people: one person can have several Visitor IDs. With all domains selected, each site’s visitor count is added separately. On Overview, the total appears in the Unique visitors panel, alongside a breakdown of those visitors into Trusted, Risky visitors, Good bots and Bad bots. On the Unique visitors tab, each row represents one Visitor ID within one site. Identifications shows how many checks that visitor has in the selected scope. This dashboard aggregate is not returned in webhooks or the History API.Risky visitors
Risky visitors counts Visitor IDs in Unique visitors whose highest Risk Score in the selected period is Suspicious or Dangerous. One such check is enough. Visitors already counted as Good bots or Bad bots are excluded and shown in their own tiles. The counter does not use the visitor’s current category. The Entity card’s category is calculated from the available history, so a visitor can be counted as Risky visitors for the selected period while its current category is Trusted. The counter uses the same period, domains and filters as Unique visitors. With all domains selected, each site’s risky visitors are added separately. The tile opens Unique visitors with the Suspicious and Dangerous ranges selected. This dashboard aggregate is not returned in webhooks or the History API.Risky users
Risky users counts accounts whose current category is Suspicious or Dangerous. It appears in Overview’s Users panel. Each account is counted once within one site. An account must have a check in the selected period. Its category uses the available account history on that site, rather than the period’s highest Risk Score. At least 5% of checks scoring 60 or more gives Dangerous priority. Otherwise, at least 5% scoring 30–59 gives Suspicious. Accounts on different sites are counted separately, even with the same User HID. The large number is the percentage of such accounts among accounts with checks in the selected period. It uses one decimal place; a positive share below 0.1% is shown as 0.1%. N of users below it gives the account count. Checks without a valid User HID are excluded. User risk categories are unavailable for this selection means the metric is unavailable. The message replaces the number; unavailable accounts are not automatically treated as Trusted. Zero means no accounts in the period have a current Suspicious or Dangerous category. Risky users can overlap with High-Risk Event users. A High-Risk Event does not change the account’s current risk category. This aggregate is not returned in webhooks or the History API.High-Risk Event users
High-Risk Event users counts accounts with saved positive evidence of a High-Risk Event during the selected period. It appears in Overview’s Users panel. Each account is counted once within one site. Both the saved positive evidence and an account check must fall within the period. Multiple positives, including different event types, do not increase one account’s count. Accounts on different sites are counted separately, even with the same User HID. The total can therefore differ from the sum of the four High-Risk Event counts. The large number is the percentage of these accounts among accounts with checks in the selected period. ≥ marks a confirmed minimum; the percentage is rounded down. N of users below it gives the account count. Checks without a valid User HID are excluded. Unavailable data or Data is accumulating after capture started means the metric has not yet been established. Zero means no positives were saved in the available data, rather than guaranteeing that no events occurred. High-Risk Event users can overlap with Trusted and Risky users. A High-Risk Event does not change the account’s current risk category. This aggregate is not returned in webhooks or the History API.Analytics chart
The Analytics chart shows how Identifications, Unique visitors, Users, Devices or Public IPs change over the selected period, with Analytics’ domain selection and filters. Identifications shows check counts. Other tabs count distinct identifiers in each time bucket. One identifier can appear in several buckets, so summing the points does not give the period’s unique total. When Trusted, Suspicious or Dangerous is selected, categories appear as separate lines. Checks are categorized by their Risk Scores; visitors, accounts, devices and IPs use their current risk category. A dashed line marks incomplete data, rather than no activity.Traffic attribution
Where traffic comes from and how it is grouped in reports.Traffic Source
Traffic source is the acquisition information associated with a check. Use it to understand where traffic comes from and compare its quality. The identification card’s Traffic source block contains Channel, Referrer, Entry page, Click ID type and UTM parameters. Inidentification.scored, these values are in data.traffic_source; a History identification card uses the traffic object. The card labels the page as Entry page, while the webhook uses landing_url.
Traffic source is not a risk signal and does not affect the Risk Score. Referrer can be empty when the referring page was not supplied.
Channel
Channel is the acquisition channel determined for one check. Use it to compare traffic volume and quality across sources. It appears in the identification card’s Traffic source block. Possible values are Google Ads, Meta, TikTok, LinkedIn, X, Pinterest, Microsoft Ads, Organic Search, Search bot, Referral, Direct and Other. Meta, TikTok, LinkedIn, X and Pinterest can mean either an ad or an organic social referral. Search bot identifies the visit’s source and is not equivalent to the Search bot signal firing. Inidentification.scored, the field is data.traffic_source.channel; on a History identification card, it is traffic.channel.
Channel is not a risk signal and does not affect the Risk Score.
UTM parameters
UTM parameters are URL tags saved with a check. Use them to associate traffic volume and quality with campaigns and ads. They appear in the identification card’s Traffic source block.
Values come from the link and do not by themselves establish Channel. In
identification.scored, these fields are inside data.traffic_source; a History identification card returns the same names inside traffic, such as traffic.utm_source. A missing tag appears as a dash on the card.
UTM parameters are not risk signals and do not affect the Risk Score.
Referrer domain
Referrer domain is the domain of the referring page, saved with the check. The identification card labels it Referrer in Traffic source. It stores the registrable domain without subdomains or a page path: for example,www.news.google.co.uk becomes google.co.uk. It is separate from Channel, which can be determined independently; Referrer records the site that referred the visit.
In identification.scored, the field is traffic_source.referrer_domain. A History identification card uses traffic.referrer_domain. A missing referrer appears as a dash on the card. It can be absent on a direct visit, because of browser or referring-site settings, or on a check without JavaScript.
For a recognized Search bot, AI Bot or AI Browser, the field can contain a bot name instead of a page domain.
Referrer domain is not a risk signal and does not affect the Risk Score.
Landing URL
Landing URL is the page address saved with a check. The identification card labels it Entry page in Traffic source. It is the page where the check ran, which is not necessarily the visit’s first page. Query parameters are retained; the fragment after# is not.
In identification.scored, the field is traffic_source.landing_url. A History identification card uses traffic.entry_url. A missing address appears as a dash on the card.
Landing URL is not a risk signal and does not affect the Risk Score. It is the check’s own page address, separate from the referring site’s domain.
Channel group
A broader grouping of a resolved traffic channel. History key:traffic_channel_group; the specific channel is traffic.channel. traffic_reason, when supplied, gives context for the attribution.
Click ID type
The type of click identifier recognized for traffic attribution. Webhook:traffic_source.click_id_type. History: click_id_type. The field describes attribution metadata, not a separate risk signal.