Analytics APP Debugger

Loading Firebase Analytics Hex Decoder…
1

Capture the analytics request

Run your app through a debugging proxy and find the upload to app-measurement.com. That request body holds every event the SDK is about to send, which is the ground truth your reports are built from.

2

Paste the hex payload

Copy the body as hex and paste it in. Spacing and line breaks do not matter, and the payload never leaves your browser, the decoding runs locally because captures carry device and user identifiers.

3

Review events and parameters

Read the decoded timeline, expand any event to inspect its parameters, and filter to custom or standard events. Duplicates fired within three seconds are flagged so double-counting shows up before it reaches your reports.

What Is Analytics App Debugger?

Analytics App Debugger is a browser-based tool that converts captured Firebase Analytics or GA4 mobile application payloads into readable events, parameters, timestamps, and device details. It helps developers, analytics specialists, and quality assurance teams examine the data an application is preparing to send before that information appears in analytics reports.

Mobile analytics implementations can be difficult to validate using reporting interfaces alone. Events may arrive with missing parameters, incorrect values, unexpected names, or duplicate triggers. By decoding the original analytics request, you can review the transmitted data at its source and identify implementation problems more efficiently.

How to Decode a Firebase Analytics Payload

First, run the mobile application through a debugging proxy such as Charles, Proxyman, or mitmproxy. Locate the event upload request sent to app-measurement.com, then copy the request body in hexadecimal format.

Paste the complete hexadecimal payload into Analytics App Debugger. Spaces and line breaks do not affect the decoding process. The tool analyzes the payload and presents the captured events in chronological order, allowing you to expand each event and inspect its associated parameters.

The same process can be used for applications running the Firebase Analytics SDK on both Android and iOS because the transmitted data follows the same wire format.

What Information Does the Tool Display?

The decoded results include event names, timestamps, session information, device details, and event parameters. Parameters added by your implementation are separated from those automatically attached by the Firebase SDK, making custom tracking data easier to review.

Reserved Firebase event and parameter names are converted into more understandable equivalents. For example, abbreviated values such as _vs and _et are displayed as screen_view and engagement_time_msec. This makes the decoded payload easier to compare with the terminology used in GA4 reports.

Detect Duplicate Analytics Events

Analytics App Debugger flags events that are triggered with identical parameters within three seconds. These repetitions may indicate that the same event is being sent more than once because of an implementation issue.

Duplicate events can inflate conversions, purchases, registrations, and engagement metrics. Detecting them directly within the captured payload helps teams correct double-firing problems before inaccurate data accumulates in analytics and advertising platforms.

Decode Analytics Data Locally

Captured mobile analytics payloads may contain device identifiers, user IDs, and other sensitive implementation data. Analytics App Debugger performs the decoding process locally in your browser. The payload is not uploaded to another server, allowing you to inspect live application data without sending the captured information to a third party.

Track the digital heartbeat with Kriko

Subscribe to receive curated insights, news, and ideas shaping the digital landscape.