Journey Discovery – Customer Guide
By Melurna
in Knowledgebase
(Version 1.0 – for external use)
1. What Journey Discovery shows you
Journey Discovery gives you a microscope-level view of where every piece of data leaves the digital property. It answers two critical questions in seconds:
-
- What exact data element was transmitted?
-
- Where did it go (domain, host, IP, country)?
With this context you can validate vendors, uncover shadow data flows, and prove compliance — or spot non-compliance — in minutes instead of weeks.
2. Page at a glance
| Area | Description | Why it matters |
| Identifier Filter (left column) | A ranked list of data elements (PII, PHI, metadata, order IDs, etc.) with a heat-bar showing how many unique destinations each element was observed reaching. | Prioritize the most widely shared, or riskiest identifiers first. |
| Tracking Data View (right panel) | The granular destination list for the element you select: domain, hostname, IP address, and country. | Observe whether data stayed domestic, crossed borders, or hit unvetted third parties. |
Quick example
If “Last Name” shows 23 on the left.
→ Click “Last Name” to see the 23 unique domains/hosts/IPs on the right that received that information.
3. How to use Journey Discovery
- Sort or search the Identifier Filter
- Default sort is by element_count (highest first).
- Use the filter at the left-hand sidebar of the page to jump to a specific company.
-
- You can further narrow your filter by choosing the Scan Date
-
- Click an element to investigate
-
- The Tracking Data View refreshes to display each destination observed for that element.
-
- Export or pivot
-
- Use the vertical ellipses “•••” menu to export the data for audits or to pivot into other Melurna dashboards.
-
4. Practical use cases
- Vendor vetting – Verify that only approved analytics or payment providers are receiving sensitive fields.
- Cross-border compliance – Confirm whether PII stays local or flows to restricted geographies.
- Shadow IT discovery – Surface unknown sub-processors quietly siphoning data.
- Incident response – Trace a compromised data element to every endpoint it touched.
5. FAQ
| Question | Answer |
| Why do I see similar labels such as “Email Address 1” and “Email Address 1_v10”? | Companies often transform or mask the same data element (hashing, salting, encoding, versioning) before transmitting it. Melurna recognizes each variant and tracks its journey separately, so you can see exactly where every form of that email address travels. |
| Does a higher “element_count” always mean higher risk? | Not necessarily. It indicates more unique endpoints. Combine this with Network Security and Geographical Risk scores to determine true exposure. |
| How often is the data refreshed? | The table updates after every scan, ensuring you always work with the latest traffic. |
| Can I filter by country or IP risk level? | Yes. Use the column filters in Tracking Data View or move to the Domain IP Analysis tab for enriched risk metrics. |
| What file formats can I export? | CSV and Excel are available from the Identifier Filter menu; PDF snapshots can be generated from the dashboard export controls. |
6. Tips for getting the most value
- Start with high-sensitivity fields (PII, credentials) to quickly surface critical issues.
- Compare scans over time to prove remediation or spot regressions.
- Pair Journey Discovery with Melurna’s Risk Score Guide to prioritize fixes that will raise your overall security posture fastest.
Need help?
Contact [email protected] or your Customer Success Manager for guided walkthroughs, API integration details, or bespoke reporting.