View event details

Click any row in the event list or Details to open the event details.

The event details are used to answer: where did the request come from, what was identified, and whether there is a risk.

Basic request information

You can see:

Request ID.
Event time.
Belonging application and Region.
Access or client platform.
Request processing status.

The Request ID is the most important correlation identifier when troubleshooting. It is recommended to save it with the customer server log, business order or webhook delivery ID.

Device and Visitors Information

Details may include:

Device ID.
Device type.
Operating system and version.
Browser and version. -Mobile device model.
Visitor history portal.

Different platforms return different information. Native SDK scenes typically do not have browser properties; when no value is available, the page may display "Unknown" or "—".

Device ID represents the device identification result and does not represent the identity of a natural person. Do not identify or permanently ban a user based on their Device ID alone.

Network and location

Details may include:

IPv4 or IPv6 address.
The country, region or city the IP resolves to.
Internet service provider or autonomous system information.
VPN, proxy or other network risks.

IP geolocation is a reference and may not be accurate due to mobile network, proxy or database errors. Please handle and share IP addresses in accordance with your corporate privacy policy.

Risk Signal

The risk signal area will list the signals hit by this event. An event can hit multiple signals.

When viewing signals, it is recommended to:

Read the Signal Code and localized description.
Confirm whether the signal is applicable to the current platform.
Make judgments based on device, network and business behavior.
When you need to investigate similar requests, filter the return list according to this signal.

Hitting a risk signal does not equate to confirmed fraud. You can choose to release, enhance verification, restrict operations, or block based on business risks.

JSON or raw data

If the details provide a JSON view, you can see the complete structure of the event for:

Return results against the Server API.
Find fields not directly displayed on the page.
Compare with development environment logs.
Provide desensitized troubleshooting information to technical support.

Raw data may contain device identification, IP address, or other sensitive fields. Please do not post the complete JSON directly to public tickets, chat groups, or code repositories.

Illustration: Event details

View visitor history

After opening visitor history from event details, you can view other events with the same Device ID within the current query range to help identify:

Whether there are repeated login or registration attempts from the same device.
Whether risk signals persist.
Whether the device environment has changed.
Whether the device is associated with multiple business operations.

Visitor history is subject to the current application, region, and data retention period. It does not represent a complete record of the activities of that natural person.