Skip to main content

Prices. Populations.
Informed analysis.

Connect catalog, prices and graded counts for market dashboards, card research and analytics.

Workflow
Define scope → Link prices & Population → Set data rules → Build analytics views
Analytics workspaceCard data insights

Charizard ex

223/197 · Holofoil

Same printing
Reference price · USD

$90.41

7-day change −3.87%

Past 30 days · Same-printing prices

Grade distribution

Grader

By grader and reporting date

PrintingPriceGrade

One consistent subject for every comparison.

Connect card identity, market records and grade counts to build a clear foundation for analytics.

Connect data for the same card

Define the target by card ID, language, and variant. Do not mix different editions with similar names or images.

Keep each price in context

Keep currency, price type, and date in trend and comparison views for a clear basis of comparison.

Counts for grading research

Organize Population by grader, grade and date to view graded supply alongside prices.

How to build trading card price and grading dashboards

Data services supply source records. Your platform defines analysis dimensions, display and calculations.

01

Define research scope

Select category, set, card, and variant from the catalog to define your analysis.

One card identity
02

Link prices & Population

Query market and grading data separately, retaining currency, company, grade, and snapshot dates.

Add a research dimension
03

Define data scope

Organize by version, price type and time range. Handle missing records and differing update times.

Build comparable datasets
04

Build analytics views

Show trends, grade counts or set comparisons with field definitions for reference.

Feed your analysis model

One subject. Two distinct data sources.

Card identity links the data. Prices and grading counts retain their own dimensions.

  • Filter by language and version to keep chart comparisons consistent.

  • Compare prices consistently by type, currency, and date.

  • Population counts by company and grade, with snapshot dates.

Analysis mappingBusiness data mapping
Charizard ex card

Charizard ex

Obsidian Flames · 223/197

Holofoil · English
Analysis subject
Charizard ex · 223/197
Version scope
Holofoil · English
Price dimensions
Type · Currency · Date
Grading dimensions
Grader · Grade · Population
Display
Price trend + Grade distribution

Start analysis with clear data scope.

Asks, sales and graded counts answer different questions. Preserve what each field means.

Population counts graded cards, not all surviving copies
Fields & business uses
Data dimensionsBusiness use
Card ID / Language / VariantDefine comparisons. Keep versions separate.
Price type / Currency / DateDistinguish asks, market references, and sales
Grader / Grade / CountCompare grade counts for a selected grader
Data date / SourceTrace every chart result

Clear logic behind every chart.

Explain every value, even when records are missing, updates differ or the target changes.

01Time alignment

Price and Population update at different times

Keep separate timestamps and date ranges for each source. Do not present data from different dates as one snapshot.

02Missing data

Missing data at a point in time

Mark missing records as unavailable or gaps in charts. Do not turn missing values into false price movements.

03Comparison scope

Different languages or versions

Keep language and version as filters. Label cross-version comparisons clearly so users can understand the differences.

Before you start, Good to know.

Plan how data flows through every step of your business.

More questions? Contact us

Can price and Population share an analysis page?

Yes. Link the same card, then display price records and grade distributions side by side. Keep currencies, companies, and timestamps distinct; your platform manages analysis.

How do I keep visually similar versions separate?

Define the card with catalog and card ID, then verify language and variant. Use the same definition for price, Population, and display filters.

Can reference prices, asks and sales be combined?

Define price type, currency and time range before comparing. Show different scopes separately and calculate only with records that meet your analysis rules.

Can I add Population counts across graders?

Define counting rules first. Records across graders may include resubmissions or crossovers. Combined counts do not directly represent print runs or surviving physical cards.

How should charts handle missing prices or Population?

Show gaps or No records alongside the available date range. Do not replace missing data with zero when calculating changes.

Can I connect data to existing BI or research tools?

Map catalog, price, and Population data to your fields and analytics flow. Your business manages storage, calculations, access, and charting.

Tell us about
card business.

Connect an API, request a key or discuss your data needs.
Tell us what you are building. Let us find the next step.

  • Start with your use case

    Define product goals, data scope, and API needs.

  • Find the right integration

    Combine recognition, imaging and data.

  • Discuss trial access

    Once the plan is agreed, we help you get an API key.

Services of interestSelect any

By submitting, you agree we may contact you about this inquiry.

Request submission is not connected in this preview.

Bring card data into your workflow.

Tell us what you are building. Let us find the next step.