Skip to main content
The polygon.predictions.user_positions_daily view provides daily snapshots of user holdings across all prediction markets. Each row represents a user’s position in a specific outcome token on a given day, enriched with comprehensive market metadata. Use this view for portfolio analysis, position tracking, exposure calculation, and understanding user investment patterns across different market categories.

​
Table Columns

Unique Key: unique_id
Column NameData TypeDescription
projectVARCHARProject name (ex. polymarket).
protocolVARCHARProtocol name (ex. polymarket).
dayDATEDate of the position snapshot.
addressVARCHARUser wallet address holding the position.
token_addressVARCHARConditional Tokens contract address.
token_idVARCHARToken ID for the specific outcome token.
token_balanceFLOATNumber of outcome tokens held (cumulative balance), normalized by dividing by 1e6.
condition_idVARCHARUnique condition identifier for the market.
market_unique_idVARCHARUnique key for grouping related markets.
market_idVARCHARMarket identifier from onchain data.
market_nameVARCHARMarket name (uses question for single markets).
market_descriptionVARCHARMarket description from onchain events.
question_idVARCHARUnique question identifier.
questionVARCHARMarket question text.
question_descriptionVARCHARMarket description from API.
token_nameVARCHARCombined outcome and question name.
token_outcomeVARCHARToken outcome name (Yes/No).
is_winnerBOOLEANWhether this outcome won the market.
market_activeBOOLEANWhether market is currently active.
market_closedBOOLEANWhether market is closed.
market_accepting_ordersBOOLEANWhether market is accepting new orders.
categoryVARCHARMain market category.
sub_categoryVARCHARSpecific market subcategory.
tagsVARCHARAPI category tags.
neg_riskBOOLEANWhether this is a NegRisk market.
resolved_byVARCHAREntity responsible for resolution.
oracleVARCHAROracle contract address for market resolution.
resolution_outcomeVARCHARMarket resolution outcome if resolved.
resolved_atTIMESTAMP_NTZ(9)Market resolution timestamp.
unique_idVARCHARUnique identifier combining day, address, and token_id (format ‘day-YYYY-MM-DD_address-_token_id-’).

​
Understanding Position Data

  • Forward-filled positions: If a user had a position on a previous day but no activity on a given day, the position is forward-filled
  • Cumulative balance: The token_balance represents the cumulative balance of tokens held, not just the change