Step-by-step guide
MuninCompare
Install the unpacked Chrome extension and compare two fictional analytics HAR captures.
For analysts or QA teams reviewing an authorised before/after browser journey.
See it in use
Compare two fictional checkout journeys
A screenshot walkthrough with fictional practice data. Select a step to explore.
1. Start with
Compare two fictional checkout journeys
The included before and after HAR files represent the same test journey.
Sample files and contents
The included fictional changes-before.har and changes-after.har, captured as equivalent test journeys.
Practice files and guides are free. The complete app is included only where the product page says so.
2. In the app
Try it in three steps
- Load the fictional HAR pair.
- Review changed groups and unsupported traffic.
- Open export preview and save the redacted report.
Show every click and setting
- Load fictional example in the extension.
- Review changes and unsupported traffic.
- Open export preview and download the redacted HTML report.
3. The result
Inspect the result
The report groups removed, added, changed and unchanged requests. The exported HTML is self-contained and uses fictional traffic.
What to check in the practice result
The fictional change pair produces nine groups: one removed, one added, three changed and four unchanged. One changed group is also repeated. Review changes shows five groups. Six unsupported requests remain counted but unanalysed. The result does not certify correct tracking or consent.
This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.
See the workflow at a glance
Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.
Review the tracking differences after a release.
Repeat an authorised journey, then inspect what changed in its supported analytics traffic. MuninCompare compares two local HAR captures for added, removed, changed and repeated GA4 or Adobe Analytics events, with HTML, CSV and JSON exports. The fictional checkout example shows the review flow without exposing customer traffic. It does not capture requests or certify correct tracking or consent. Installation requires an unpacked Chrome extension and Developer mode; inspect exported reports before sharing because redaction does not guarantee anonymity.
View the illustrated card
Try the Fictional Journey First
Start with the fictional HAR comparison in the free Perunlight guide. It shows the kind of event differences to review before you decide whether you need MuninCompare for your own authorised captures. The paid extension costs $9.99 once and requires manual installation in Chrome. Check unsupported traffic and review every export; redaction is not guaranteed anonymisation. The free exercise is a learning example, not a Chrome Web Store installation or proof that your tracking is correct.
View the illustrated card
Before you start
- Google Chrome 120+ with Developer mode and Load unpacked allowed; tested in Chrome for Testing 152 on Linux. Managed browser policy may forbid this.
- MuninCompare-1.0.2.zip; this is not a Chrome Web Store listing.
- Two HAR files from an authorised, comparable journey; start with the fictional examples.
Your first result
Install unpacked
Extract MuninCompare-1.0.2.zip to a permanent folder. Open chrome://extensions in Chrome, enable Developer mode, click Load unpacked and select the extracted extension folder containing manifest.json.
Open and load
Click its toolbar icon or press Alt+Shift+M. Choose Load fictional example, or load your own before and after HAR files.
Review and export
Start in Review changes to see removed, added, changed or repeated groups. Choose All for unchanged groups too. Expand Coverage to inspect unsupported traffic; its totals remain visible when closed. Open Explain for the reason behind a difference. Preview and download HTML, CSV or JSON. View filters do not restrict exports, which are capped at 2,000 groups with omissions stated. Review content before sharing.
Uninstall
In chrome://extensions remove MuninCompare and delete its extracted folder. The extension stores no files or browser data.
A worked example
Find changes in a fictional checkout journey
Input: The included fictional changes-before.har and changes-after.har, captured as equivalent test journeys.
- Load fictional example in the extension.
- Review changes and unsupported traffic.
- Open export preview and download the redacted HTML report.
Expected result: The fictional change pair produces nine groups: one removed, one added, three changed and four unchanged. One changed group is also repeated. Review changes shows five groups. Six unsupported requests remain counted but unanalysed. The result does not certify correct tracking or consent.
More application screens
From a change list to an explained report
Actual MuninCompare 1.0.2 screens in Chrome for Testing 152 on Linux, using fictional analytics captures.
1. Start with the changes
2. See why an event changed
3. Preview what you will share
4. Take a readable report away
Troubleshooting
Some event groups are not shown
Review changes hides unchanged groups. Choose All, clear search and turn off Repeated only to inspect the full comparison. Exports ignore these view filters.
Load unpacked is unavailable
A managed Chrome policy can block Developer mode or unpacked extensions. Ask your administrator or use a profile you control.
Events are missing
Check unsupported-traffic counts. Custom collection domains, Adobe Target and Adobe Web SDK are not supported.
Compatibility & limits
- No network requests or automatic capture; selected HAR data is processed in tab memory. HAR files can contain secrets, so handle originals carefully.
- Redaction is not guaranteed anonymisation. Review exports before sharing.
- Chrome for Testing 152 on Linux was tested; other Chromium browsers and real customer journeys were not.
Need a hand?
Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.