Data Sources

Where CFBTrack data comes from and what each source category is used for.

CFBTrack mixes curated internal tables with synchronized external feeds and manually reviewed enrichments. Different public pages draw from different source sets, so this page groups the major inputs by the work they support.

Review data statusBrowse team pages

What this page covers

  • Curated core tables

    Teams, players, schedules, stadiums, and historical season facts anchor most public pages.

  • Synchronized feeds

    Stats, recruiting, roster, and game-level records are refreshed from supported source pipelines when available.

  • Page-specific enrichments

    Media, video, graphics, and geography surfaces can layer their own focused datasets on top.

Primary source categories

Most CFBTrack pages are built from a small set of repeatable source groups so data can be reused across teams, seasons, and analytics routes without one-off scraping logic on every page.

  • Curated CFBTrack team, player, venue, and conference tables.
  • Synchronized game, roster, stat, and recruiting feeds where coverage is available.
  • Official/source-backed box-score and game-stat rows are treated as source stats; CFBTrack maps, filters, and displays those fields rather than redefining the underlying categories.
  • Advanced team metrics such as PPA, success rate, explosiveness, and havoc are treated as source-provided CFBD fields; CFBTrack verifies local mapping, scale, filters, and display.
  • CFBTrack-owned models and display scores, including dominance, talent usage, player profile scores, and trend summaries, are documented as derived outputs rather than official NCAA or CFBD categories.
  • Reviewed media, video, and geography datasets for specialized route families.

How sources map to pages

Team pages usually combine program metadata, season records, recruiting, roster, and venue context. Player pages pull from player, roster, usage, and historical season tables. Analytics pages often blend traditional and advanced season stats into a compact route-specific view model.

  • Schedule and game pages prioritize date, venue, and result integrity.
  • History pages combine all-time record metadata, curated championship selector rows, and conference membership history.
  • Recruiting and transfer pages depend on the availability and freshness of those feeds.
  • Blog and video pages use their own publishing metadata in addition to the core football dataset.

Coverage and attribution

Unless a page states otherwise, CFBTrack public dataset outputs are intended for personal, editorial, and research use with attribution and a link back to the original page. Coverage varies by route, so the page-level data notes remain the most specific source statement.

  • When a page ships a structured-data block, the visible content should still match the public page.
  • Coverage years can differ between route families; check page-level notes when precision matters.
  • Some specialty pages intentionally hide or defer sections when a supporting source is missing.

Source notes by route family

Different route families depend on different inputs. Core team and schedule pages start from program, venue, conference, and game records. Stat leaderboards depend on player, team, season, and weekly stat tables. Recruiting, transfer, media, video, and graphics pages layer more specialized records on top of that core dataset.

  • Team and stadium pages use location, venue, conference, and season context together.
  • Stats pages use compact view models built from the fields needed for the selected leaderboard, chart, or comparison.
  • Championship pages group selector rows into title seasons and use historical conference membership where that route exposes conference share.
  • Recruiting and transfer pages depend on class, prospect, roster, and movement records whose coverage can vary by year.
  • Media, video, and graphics pages can use reviewed publishing metadata in addition to game and team data.

What to verify before citing a page

When precision matters, cite the specific CFBTrack URL and check the visible page context first. A team profile, a filtered leaderboard, and a state directory can all use overlapping data while answering different questions.

  • Keep query parameters when citing filtered pages so the same sample can be reproduced.
  • Use page-level labels to distinguish regular season, postseason, combined, weekly, and historical samples.
  • Use the corrections page when a public source and the CFBTrack page disagree in a way that affects the result.