A Marketplace Match Report measures how well a supplier’s data overlaps with — and enriches — your first-party identity data. This guide walks through the five-step builder that produces a report.Documentation Index
Fetch the complete documentation index at: https://docs.narrative.io/llms.txt
Use this file to discover all available pages before exploring further.
Marketplace Match Reports run on Snowflake data planes. The builder generates a workflow that materializes the report as a dataset; the dataset appears in the Reports listing once the workflow’s final step completes.
Prerequisites
- A first-party edge dataset built with Graph Studio. The match report uses these edges as its starting inventory of identifiers.
- An access rule granting you access to a supplier dataset that has been mapped to Rosetta Stone identifier attributes and (optionally) demographic attributes.
- A Snowflake data plane selected in the data plane switcher.
Open the builder
Navigate to My Data > Reports and click New report. The builder loads with a five-step left rail:- Source dataset — your first-party edge dataset.
- Supplier dataset — the third-party access rule you are evaluating.
- Match identifiers — which identifier types to match on.
- Supplier enrichment — which identifiers and demographic attributes to pull from the supplier for matched people.
- Finalize — name and schedule the report.
Step 1: Select a source dataset
Pick the edge dataset that holds the customers you want to evaluate. Only datasets eligible to act as a graph source — those with Rosetta Stone identifier mappings and statistics that the report can read — appear in the picker.Step 2: Select a supplier dataset
Choose the access rule for the supplier you want to evaluate. Only access rules that the report builder can join against your source dataset appear in the list. The builder shows an inline message when a supplier is ineligible — typically because it has no overlapping identifier types with your source. You can select one supplier access rule per report. To compare multiple suppliers, build one report per supplier.Step 3: Choose match identifiers
Match identifiers determine which identifier types the report uses to match your people to the supplier. The grid lists every identifier type your source dataset has in common with the supplier; all are selected by default. Deselect a type to exclude it from matching. The match rate the report reports is the share of your people who matched on any selected identifier type, so a broader selection generally raises the match rate but may include lower-confidence matches.You must keep at least one identifier type selected to continue.
Step 4: Configure supplier enrichment
Supplier enrichment defines what the report pulls from the supplier for the people who matched in step 3. Two selections live on this step:- New identifiers — additional identifier types the supplier contributes for your matched people (e.g., a hashed email the supplier has that you do not). These drive the Enrichment card and the ID Enrichment KPI.
- Demographic and behavioral attributes — categorical attributes from the supplier (e.g., gender, education level, income range). Each attribute you select becomes a panel in the Demographic & Behavioral Enrichment section of the rendered report.
Step 5: Finalize the report
Name the report, optionally describe it, and choose a refresh schedule.Set the unique name
The unique name is the NQL-safe identifier for the generated dataset. The builder uppercases the name on blur and surfaces a conflict warning if another dataset already uses the same name.
Set the display name and description
The display name is what readers see in the Reports listing and at the top of the rendered report. If you leave the display name blank, the builder copies the unique name into it when you finish editing.
Choose a refresh schedule
The default is Daily. Match reports are materialized views under the hood, so the schedule controls how often the underlying workflow re-runs and the report’s numbers update.
Review the workflow preview
The collapsible workflow preview shows the multi-step workflow the builder will submit — including the intermediate datasets it creates and the final materialized view that backs the report. Use this to sanity-check what will run on your data plane.
After submission
The report appears in the Reports listing immediately. While the producing workflow runs, the row shows the workflow’s run state (pending, running, or failed) and is not yet clickable. Once the workflow’s final step has materialized the dataset, the row becomes a link to the rendered report.Related
- Viewing a marketplace match report — how to read the rendered report once the workflow finishes
- Building an identity graph — produce the edge dataset that feeds the report’s source step
- Access rules — how supplier datasets become available to the builder

