Overview
The Explorer page — Explore your data model and the relations between datasources — validates the Datagraph model and measures the real overlap of every relation. Open DataHub → Datagraph → Explorer.Before You Begin
A Datagraph Schema must exist. Without one, the Explorer shows No schema found and offers Go to schema. See Datagraph Schema.Tabs
Validation Summary
The Explorer validates the model whenever it loads and reports three kinds of finding.
Fix structural issues first: relation analysis only runs once the definition is structurally valid.
Join Match
For each relation column pair, the Datagraph counts the distinct values on both sides and compares them.
Relations are then grouped, and the Relations tab can be filtered accordingly.
A match percentage of
— means the analysis could not run. Check that both Datasources have a Live version, then reload the Explorer.Inspecting a Join
Click Inspect join match on a relation to open the Join match analysis dialog — How well the join keys overlap between the two datasources. It reports the status (Good, Weak, Invalid, or Unavailable), the Table, Column, and Datasource ID on the From and To sides, and the join metrics above.Reading a Weak Result
A purchases table joined to a product catalogue on the product reference returns 12,000 distinct references on the purchases side and 400,000 on the catalogue side. The match percentage is 3%. That is expected: only a small share of the catalogue has ever been bought. A weak result is a signal to interpret, not always a defect. Investigate when you expect the two sides to overlap closely, for example a customer identifier shared between a CRM Datasource and a website events Datasource.What’s Next?
Schema
Correct the relations flagged by the validation summary.
Entities
Query the validated model.
Logs
Check whether a Datasource import is stale.
Datagraph in the DataHub
Share the UI walkthrough with campaign teams.