Free example · MuninCompare
Find what changed in a tracking journey
Open a missing event, a repeated request or a changed currency. These fixed fictional examples are a separate teaching diagram, not the paid Chrome extension.
Free practice · Fictional data
Open a case, compare the requests, then reveal what to investigate. These are fixed examples from the free HAR practice kit.
01Missing event1 → 0 requests
An event disappeared
The same add-to-cart step is meant to happen in both journeys. Compare the request counts.
Before
baseline.harpage_view- 1 request
view_item- 1 request
add_to_cart- 1 request
4 total requests · 3 supported
1 outside scope · 0 unsupported · 0 malformed
After
missing.harpage_view- 1 request
view_item- 1 request
add_to_cart- 0 requests
3 total requests · 2 supported
1 outside scope · 0 unsupported · 0 malformed
Show what to investigate
add_to_cart appears once before and zero times after. The CLI reports removed.
Next check. Check that both journeys included the same click and consent choices. Then inspect the tag or handler on the changed page. The files alone cannot tell you why the request disappeared.
02Repeated request1 extra repeat
One request became two
The fictional after file contains an extra identical add-to-cart request. Find the row that changed.
Before
baseline.harpage_view- 1 request
view_item- 1 request
add_to_cart- 1 request
4 total requests · 3 supported
1 outside scope · 0 unsupported · 0 malformed
After
duplicate.harpage_view- 1 request
view_item- 1 request
add_to_cart- 2 requests
5 total requests · 4 supported
1 outside scope · 0 unsupported · 0 malformed
Show what to investigate
add_to_cart grows from one to two supported requests. The CLI reports changed and repeated_after: 1: one extra identical occurrence, not one event group.
Next check. Inspect the click handler and tag triggers for an unintended second send. Repetition may also be intentional. This request evidence does not prove that Analytics recorded a duplicate conversion.
03Changed parameterEUR → USD
Same count. Different currency.
The number of requests stays the same. Look at the currency annotation on view_item.
Before
baseline.harpage_view- 1 request
view_itemFictional cu: EUR- 1 request
add_to_cart- 1 request
4 total requests · 3 supported
1 outside scope · 0 unsupported · 0 malformed
After
parameter-change.harpage_view- 1 request
view_itemFictional cu: USD- 1 request
add_to_cart- 1 request
4 total requests · 3 supported
1 outside scope · 0 unsupported · 0 malformed
Show what to investigate
view_item stays at one request, but its fictional cu parameter changes from EUR to USD. The CLI reports changed; it does not print those parameter values.
Next check. The currency annotations here come from the authored HAR files. Check whether the currency change was intended, then inspect the payload. Equal request counts alone would miss this difference.
Each supported request in these examples carries one event. The narrow GA4-style comparison excludes Adobe, batches and custom collectors. The files use invented .example hosts and responses; these are not browser captures. Request counts do not prove delivery to Analytics, tracking correctness or consent.
Four fictional HARs, a local Node CLI, source, tests and a worked lesson. Run the examples yourself with Node; tested on Node 22.22.2 / Linux. This browser example is a teaching diagram, not the MuninCompare extension.
Need to compare your own captures?
MuninCompare is $9.99 once. It runs as an unpacked desktop Chrome extension for its documented GA4 and Adobe Analytics scope. It does not certify tracking correctness or anonymize every report.