Skip to content

Forecast reference

Data dictionary

Understand the columns in your forecast downloads and the matching fields returned by the API and AI agents.

Keep this reference alongside your spreadsheets: download definitions as CSV or JSON. Version: dv-data-dictionary-v2.

Daily DSI forecast

CSV headingAPI / MCP fieldMeaningUnit / valuesExample
cbsacbsaU.S. Census metro code.5-digit text14460
metro_namemetroNameOfficial metro name.textBoston-Cambridge-Newton, MA-NH
datedateForecast date.YYYY-MM-DD2026-10-07
lead_dayleadDayForecast day; 1 is the issue date.1–71
forecast_confidenceforecastConfidenceConfidence label; reduced from day 6.standard / reducedstandard
dsidsiModeled indoor drying stress on skin; higher means drier.index, 0–105.92
dsi_lowdsiLowLower end of the forecast range.index, 0–104.88
dsi_highdsiHighUpper end of the forecast range.index, 0–107.17
covered_populationcoveredPopulationPopulation covered by the metro forecast.people4917438

Seven-day DSI summaries

CSV headingAPI / MCP fieldMeaningUnit / valuesExample
rankrankRank within the requested sort; present only for ranked results.integer, 1 = highest1
cbsacbsaU.S. Census metro code.5-digit text14460
metro_namemetroNameOfficial metro name.textBoston-Cambridge-Newton, MA-NH
first_datefirstDateFirst date included in the summary.YYYY-MM-DD2026-10-07
last_datelastDateLast date included in the summary.YYYY-MM-DD2026-10-13
daysdaysNumber of daily values summarized.days7
mean7mean7Arithmetic mean of daily DSI values in this issue.index, 0–105.2
peak_dsipeak.dsiHighest daily DSI.index, 0–106.2
peak_datepeak.dateDate of the highest DSI; earliest date if tied.YYYY-MM-DD2026-10-09
excess_above_4excessAbove4Sum of max(DSI − 4, 0) across the forecast days.index-days above 48.4
population_65pluspopulation65plusMetro-wide population aged 65+, from 2023 ACS 5-year B01001.people; null if unavailable100000
exposure_65plusexposure65plusCumulative excess above 4 multiplied by population aged 65+. Blank if population is unavailable.65+ person-index-days840000
trend_slope_per_daytrend.slopePerDayLeast-squares slope of daily DSI over the window.DSI per day0.2
trendtrend.labelRising at slope ≥ 0.15/day; falling at ≤ −0.15/day; otherwise steady.rising / falling / steadyrising

Additional internal producer fields

These additional fields appear in internal producer files. They are not included in customer CSV downloads; other producer columns share the definitions above.

CSV headingAPI / MCP fieldMeaningUnit / valuesExample
category—Search category in the producer artifact.dry_skin / humidifierdry_skin
dma_coderegionCodeLegacy producer name for the Google Trends identifier; customer CSV uses Google Trends id.3-digit text501
dma_nameregionNameProducer name for the Google Trends metro area name; customer CSV uses region_name.textNew York
weather_search_multiplier—Expected interest relative to normal weather. 1.10 means +10%; 0.90 means −10%.ratio1.10
cohort_complete—Whether all required regions in the supported category cohort were produced.true / falsetrue
prior_issue_change—Reserved change-from-prior-issue field. Currently required to be null; no usable change value or unit is defined.null; blank in CSVblank

Marketing signal guidance

Historical search data source: Google Trends. Search outlooks are Dermal Vectors modeled estimates using historical search data and weather-derived DSI, not forecasts supplied by Google or Google Ads search volume. Data source: Google Trends.

DSI forecasts use U.S. Census metro areas (5-digit CBSA codes); search forecasts use Google Trends metro areas (Google Trends ids). Their urban areas have different geographies and are not directly comparable. A shared city name does not establish matching boundaries or populations. Do not join, substitute or make paired local comparisons by name or code. No approved mapping is currently provided. Discuss complementary signals with each geography clearly identified, without implying they describe the same local population.

Version: dv-search-signal-guidance-v4. Use two complementary signals to explain where and when to test category messaging.

weather_search_change_pct

Where does unusual dryness suggest a category messaging or timing opportunity?

Baseline: Same Google Trends metro area and week with training-normal dryness features, retaining seasonality.

Modeled percentage difference associated with dryness versus normal weather; not causal advertising lift.

seasonal_planning_ratio

Where is this week's expected category interest above the Google Trends metro area's average week?

Baseline: The Google Trends metro area's arithmetic mean search index in model training.

Includes both seasonality and weather. 1.20 means 20% above that Google Trends metro area's average week, not 20% weather lift.

Agent workflow

  1. Identify the manager's category, markets and planning objective; clarify missing context before tailoring an action.
  2. Read get_product_dictionary and check available products with list_forecast_products; retrieve a current category outlook.
  3. For weather-related timing use sort=weather_change; for overall weekly interest use sort=seasonal. Show both signals together and explain the chosen baseline.
  4. Do not invent a composite score or significance threshold. The default top 10 is a shortlist selected by the requested sort, not the entire category universe.
  5. Cite issueId, targetWeek, category, Google Trends ids, selection scope and sorting metric; reuse that issue when comparing results.
  6. Propose a messaging, timing or geographic test. Ask for brand campaign performance, inventory and media costs before recommending spending changes; manager approval precedes campaign action.

Illustrative combinations

  • 12% weather change; 1.2 seasonal ratio: Both signals are above their baselines: consider a weather-relevant timing test; neither establishes incremental sales.
  • 0% weather change; 1.2 seasonal ratio: An above-average seasonal week without an additional modeled dryness effect; use seasonal context rather than a weather-rise claim.
  • 12% weather change; 0.8 seasonal ratio: Above normal-weather interest but still below the Google Trends metro area's average week; describe the relative increase without calling it a high overall opportunity.

Qualifications

  • Keep dry-skin and humidifier categories separate; their index scales cannot be compared or added.
  • WeatherRank remains the category-wide weather rank, even in seasonal sorts or filtered results; it is not a confidence score.
  • PredictedSearchIndex is not search counts, market size or audience size. Lower values alone do not justify campaign cuts.
  • Flag extrapolation and explain dsiPopulationCoverage as weather-input coverage, not people searching or forecast confidence.
  • There are no calibrated per-metro-area search prediction intervals; small differences may be noise. Do not infer significance from rank.
  • These are Sunday-Saturday weekly outlooks revised daily, not daily search peaks. Do not merge Google Trends metro areas with Census DSI metros without a governed mapping.
  • No causal weather, campaign, sales or ROI claim follows from these modeled associations. Missing brand context must remain explicit.

What to report to the manager

  • Recommended signal and why it fits the question
  • Google Trends metro areas, both signal values and their baselines
  • Suggested test and required brand context
  • Extrapolation, coverage and uncertainty qualifications
  • Issue, category, week and selection scope

Interpreting the outputs

  • DSI is a weather-derived index, not a clinical measure, sales prediction or audience size.
  • Search outlooks describe a Sunday–Saturday week revised daily, not daily search predictions or counts.
  • Dry skin and humidifier use different index scales; do not compare or add their indices.
  • Google Trends metro areas differ from Census CBSA metros; no mapping to Census metro areas is approved.
  • Search outlooks have no calibrated per-metro-area prediction intervals. Small differences may be noise.
  • CSV blanks represent unavailable values, not zero. Producer-only fields are not customer CSV columns.

For issue dates, provenance and request options, see the DSI API reference and Search Outlook API reference. Definitions describe field meanings; availability depends on product release and access.