GA4 Request Decoder

GA4 sends your events as long, hard-to-read URLs. Paste one here to see each event with its parameters, items, user properties, session and consent, plus automatic checks for the mistakes that break revenue and ecommerce reports.

Press F12 → Network, filter by collect?v=2, click a request and copy the Request URL. If the request has a payload (several events in one request), paste the payload lines below the URL.

Private by design: everything is decoded in your browser. Nothing you paste is uploaded or stored.

INTERACTIVE DEMO Want to test how this tool works?
Save these results as a PDF report A clean, branded copy to share with your team or client.
Free PDF report

Where should we put your name on the report?

Your PDF downloads straight away. Your tool data never leaves your browser.

Jobair Mahmud, Web Analytics & Tracking Architect
Tool Creator

Jobair Mahmud

Founder & Tracking Architect

100% Top Rated
5.0 / 5.0

Events firing but reports still wrong?

I audit your GA4 events end to end, fix the data layer and tags, and make GA4 revenue match your store.

Get my GA4 fixed →

How to use the GA4 Request Decoder

GA4 sends events to /g/collect as URL parameters: en is the event name, ep.* are text parameters, epn.* are number parameters, up.* are user properties and pr1, pr2 … are items. This tool turns that into readable tables and checks the details that silently break reports, like a purchase without currency or a value sent as text.

Step by step

  1. Open the page where the event happens and press F12 → Network.
  2. Filter by "collect?v=2", trigger the event (for example complete a test purchase), then click the new request.
  3. Copy the Request URL. If the request has a Payload (GA4 often batches several events), copy those lines too and paste them under the URL.
  4. Click Decode and read the checks first, then the parameters and items of each event.

How to read your result

No problems found

The event has a name, a client ID and the parameters GA4 needs. Check in DebugView that it arrives with the same values.

Warnings

The event works but some data will be lost or misreported, for example text values over 100 characters or a value sent as text.

Errors

Something will break reports: purchases without transaction_id or currency, or items without an ID or name.

Common mistakes

  • Pushing value as a string with a currency symbol ("$49.00") instead of a number.
  • Leaving out currency, which makes GA4 ignore the revenue.
  • Reusing the same transaction_id on page reloads instead of firing the purchase once.
  • Parameter names longer than 40 characters, which GA4 drops without warning.

Questions

Why does one request contain several events?

GA4 batches events that happen close together into one request. The shared parameters are in the URL and each event is a line in the payload.

Can I decode server-side (sGTM) requests?

Yes. Requests sent to your own tagging domain use the same parameters, so paste them the same way.

What is the difference between ep. and epn.?

ep. parameters are text and epn. parameters are numbers. Revenue and other metrics must arrive as epn. to be summed correctly.

Events firing but reports still wrong?

I audit your GA4 events end to end, fix the data layer and tags, and make GA4 revenue match your store.