Find events

Use Request ID

If you have a Request ID, this is the most precise way to find it:

1. Click Advanced Filtering.
2. Select Request ID.
3. Enter the complete Request ID.
4. Click Apply Filter.

The Request ID usually comes from client server logs, Webhook delivery logs, or SDK debugging results. Using complete values ​​avoids returning irrelevant events.

Use Device ID

If you want to see a device's activity over time:

1. Select Device ID.
2. Enter the complete Device ID.
3. Set the time range.
4. View events related to the device.

Device ID is a device identification identifier and is not the same as the real user identity. Use it in conjunction with your account, order, and business logs when investigating registration, login, or transaction issues.

Using IP address

Filtering by IP address can help you investigate a network exit, proxy, or source of anomalies. The supported IPv4 and IPv6 range is based on the current console. IP addresses may change across mobile networks, corporate networks, VPNs, or proxies, so do not use IP alone to determine whether two requests are from the same user or device.

Use risk signals

Click Signals in the filter to select one or more risk signals. Available signals depend on current platform and product capabilities, common types include:

• Emulator or virtual machine.
• VPN or proxy.
• Browser or client tampering.
• Jailbreak, Root or clone the app.
• Developer tools or incognito mode.
• IP blacklisting or other network risks.

After selecting a signal, the event list will show only records that hit the selected signal. Click the signal name or description to see what the signal means.