Wikipedia company-article attention velocity (daily)
Daily enrichment signals measuring public attention to ~79 US and Canadian companies through English-Wikipedia pageviews. For each company the trailing 60 complete UTC days of daily views are pulled from the official keyless Wikimedia pageviews API for the company's canonical article (resolved by hand against the curated company dictionary shared with hn_company_sentiment/gdelt_company_tone; "Crusoe" has no article and is excluded), then transformed: views_60d (identity-gated: sum of daily views), mean_daily_views, views_7d / views_7d_prev (trailing vs prior week), wow_pct (views_7d-views_7d_prev)/views_7d_prev (null when the prior week is zero and the trailing week is also zero; +2.0 clip bound when attention appears from nothing), z_7d = (mean_7d - mean(baseline)) / stdev(baseline) over the first 46 days (flat baseline: +3.0 if the trailing week is above it, -3.0 below, 0.0 equal), attention_score = 100*(0.50*min-max(log1p(views_7d)) + 0.30*min-max(clip(z_7d,-3,3)) + 0.20*min-max(clip(wow_pct,-2,2))), min-maxed within the snapshot, attention_rank (score desc; ties: views_7d desc, company_name asc), spike_flag = 1 when z_7d >= 2.0, source_url = the canonical article URL (the pageviews REST fetch URL's timestamp runs trip the hub PII screen, so the article URL is stored instead). Articles with < 57/60 days of coverage are dropped loudly. Who joins this: an IR/comms team joins daily public-attention velocity per ticker to their trading/media calendar on ticker + as_of; a quant desk joins attention_score/z_7d to returns on ticker + as_of. Primary key: (as_of, company_name); join keys: ticker, company_name, as_of, country_code (ISO alpha-3). Nullability: ticker null for private companies (OpenAI, Anthropic, Databricks, ...); wow_pct null only when both weeks are zero. Caveats: attention_score is within-snapshot relative, not comparable across days; pageviews count all access types including automated traffic not already filtered by the API; article renames are absorbed by the canonical-title table. Underlying aggregates are CC0 1.0, so commercial_use = yes. Sample use: filter ticker = 'NVDA' for Nvidia's daily attention velocity, or order by attention_rank for today's fastest-rising company attention.
Les titres et les descriptions proviennent des sources de données, en anglais.
- Lignes
- 79
- Colonnes
- 17
- Cadence de la source
- Quotidienne
- Dernière actualisation
- 27 sept. 2026
- Thème
- news
| Colonne | Type | Description |
|---|---|---|
| as_of | string | Snapshot date (UTC, YYYY-MM-DD) — the last complete UTC day of the 60-day pageview window. Part of the primary key. (unit: date) |
| company_name | string | Canonical company name from the curated dictionary (shared with hn_company_sentiment / gdelt_company_tone). Part of the primary key; one of the join keys. (unit: text) |
| ticker | string | Primary-listing stock symbol (exchange-suffixed for TSX, e.g. SHOP.TO). Null for private companies (OpenAI, Anthropic, Databricks, ...). The join key for positions/returns tables. (unit: symbol) |
| country_code | string | Company HQ country, ISO alpha-3 (USA/CAN). (unit: ISO alpha-3) |
| sector | string | Closed sector vocabulary from the connector (semiconductors, software, ai-lab, ...). (unit: category) |
| article_title | string | Canonical English-Wikipedia article title the pageviews were pulled for (hand-resolved, redirect-resolved; e.g. xAI resolves to SpaceXAI). (unit: text) |
| views_60d | integer | Total pageviews over the 60-day window. Identity-gated: equals the sum of the 60 daily values. (unit: count) |
| mean_daily_views | float | views_60d / 60, rounded to 2 decimals. (unit: count) |
| views_7d | integer | Pageviews over the trailing 7 days of the window (the attention level). (unit: count) |
| views_7d_prev | integer | Pageviews over the prior 7 days (days -14 to -8), the WoW baseline. (unit: count) |
| wow_pct | float | Week-over-week growth = (views_7d - views_7d_prev) / views_7d_prev, rounded to 4 decimals. +2.0 when attention appears from a zero prior week (clip bound); null only when both weeks are zero. (unit: ratio) |
| z_7d | float | Attention z-score = (mean_7d - mean(baseline)) / stdev(baseline) over the first 46 days of the window, rounded to 4 decimals. Flat baseline: +3.0 if the trailing week is above it, -3.0 below, 0.0 when equal. (unit: score) |
| attention_score | float | 0-100 attention composite = 100 * (0.50 * min-max(log1p(views_7d)) + 0.30 * min-max(clip(z_7d,-3,3)) + 0.20 * min-max(clip(wow_pct,-2,2))), min-maxed within the snapshot. Within-snapshot relative — not comparable across days. (unit: score) |
| attention_rank | integer | Rank by attention_score desc (1 = most attention); ties broken by views_7d desc, then company name asc. (unit: rank) |
| spike_flag | integer | 1 when z_7d >= 2.0 (documented attention spike), else 0. (unit: flag) |
| source_url | string | Canonical English-Wikipedia article URL for the row's company. The pageview aggregates behind the row were fetched from the Wikimedia pageviews REST API per-article endpoint over the 60-day window (the exact REST URL is not stored: its YYYYMMDDHH timestamp runs trip the hub ingest PII phone screen). (unit: url) |
| row_hash | string | Deterministic 16-hex-char content hash over (as_of, company_name, views_60d, views_7d, article_title) — identical input yields an identical snapshot. (unit: hash) |
10 premières lignes d’exemple — un aperçu, pas le jeu de données complet.
| as_of | company_name | ticker | country_code | sector | article_title | views_60d | mean_daily_views | views_7d | views_7d_prev | wow_pct | z_7d | attention_score | attention_rank | spike_flag | source_url | row_hash |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-09-26 | Scale AI | — | USA | ai-lab | Scale AI | 52 283 | 871,38 | 13 039 | 5 592 | 1,332 | 6,141 | 84,49 | 1 | 1 | https://en.wikipedia.org/wiki/Scale_AI | 34c50ee5ba105841 |
| 2026-09-26 | Discord | — | USA | social | Discord | 179 564 | 2 992,73 | 28 322 | 19 781 | 0,432 | 4,24 | 82,26 | 2 | 1 | https://en.wikipedia.org/wiki/Discord | e886085ac529a123 |
| 2026-09-26 | DoorDash | DASH | USA | mobility | DoorDash | 53 173 | 886,22 | 10 055 | 5 105 | 0,97 | 4,4 | 78,05 | 3 | 1 | https://en.wikipedia.org/wiki/DoorDash | 68fb248315852b37 |
| 2026-09-26 | AMD | AMD | USA | semiconductors | AMD | 73 807 | 1 230,12 | 13 422 | 8 363 | 0,605 | 5,69 | 76,9 | 4 | 1 | https://en.wikipedia.org/wiki/AMD | e0cfc1b80b7af3b0 |
| 2026-09-26 | BlackBerry | BB | CAN | cybersecurity | BlackBerry Limited | 79 183 | 1 319,72 | 13 170 | 12 166 | 0,083 | 2,788 | 69,48 | 5 | 1 | https://en.wikipedia.org/wiki/BlackBerry_Limited | c7cfa97575dc9bec |
| 2026-09-26 | OpenAI | — | USA | ai-lab | OpenAI | 456 800 | 7 613,33 | 64 592 | 81 273 | -0,205 | 0,874 | 67,49 | 6 | 0 | https://en.wikipedia.org/wiki/OpenAI | 809f17441f77cba1 |
| 2026-09-26 | Microsoft | MSFT | USA | software | Microsoft | 376 805 | 6 280,08 | 48 888 | 58 953 | -0,171 | 0,806 | 64,66 | 7 | 0 | https://en.wikipedia.org/wiki/Microsoft | b88232af065dd5e0 |
| 2026-09-26 | Nvidia | NVDA | USA | semiconductors | Nvidia | 319 111 | 5 318,52 | 41 085 | 39 040 | 0,052 | 0,457 | 62,79 | 8 | 0 | https://en.wikipedia.org/wiki/Nvidia | 9ba2c465b78e6fa3 |
| 2026-09-26 | Amazon | AMZN | USA | ecommerce | Amazon (company) | 471 852 | 7 864,2 | 56 099 | 54 639 | 0,027 | 0,085 | 62,75 | 9 | 0 | https://en.wikipedia.org/wiki/Amazon_%28company%29 | fcc229b492548cfc |
| 2026-09-26 | Qualcomm | QCOM | USA | semiconductors | Qualcomm | 57 017 | 950,28 | 8 528 | 7 146 | 0,193 | 2,207 | 62,14 | 10 | 1 | https://en.wikipedia.org/wiki/Qualcomm | 0fb16499da347e5f |
- Actuelle
20260927T113249Z-38d19e88533d · sha256 38d19e88533d…
79 lignes · premier instantané
Dirigez n’importe quel LLM vers le point d’accès des métadonnées — la documentation ci-dessus est aussi lisible par machine (JSON-LD + Croissant).
curl "https://datazimuts.com/v1/datasets/wiki_company_attention/wiki_company_attention_daily" | jq '{title, rows, columns_count, license}'import requests
ds = requests.get("https://datazimuts.com/v1/datasets/wiki_company_attention/wiki_company_attention_daily").json()
print(ds["title"], ds["rows"], "rows")
# Sample rows for an LLM context window
for row in ds.get("sample_rows", [])[:5]:
print(row)Point d’accès API : https://datazimuts.com/v1/datasets/wiki_company_attention/wiki_company_attention_daily
Astuce : récupérez /llms.txt pour le catalogue complet lisible par machine.
D’où viennent ces données et ce qui en a été fait. Le travail des autres apparaît sous forme de décomptes ; seuls les projets partagés sont nommés.
Citer cet instantané
Épinglé à l’instantané 20260927T113249Z-38d19e88533d et à son empreinte, pour que vos lecteurs obtiennent exactement les données utilisées.
Wikipedia company-article attention (agent-curated). (2026). Wikipedia company-article attention velocity (daily) [Data set, snapshot 20260927T113249Z-38d19e88533d, sha256 38d19e88533d]. Datazimuts. Retrieved 2026-09-27, from https://datazimuts.com/fr/datasets/wiki_company_attention/wiki_company_attention_daily?snapshot=20260927T113249Z-38d19e88533d
@misc{dz_wiki_company_attention_wiki_company_atte_38d19e88,
title = {{Wikipedia company-article attention velocity (daily)}},
author = {{Wikipedia company-article attention (agent-curated)}},
year = {2026},
publisher = {Datazimuts},
howpublished = {\url{https://datazimuts.com/fr/datasets/wiki_company_attention/wiki_company_attention_daily?snapshot=20260927T113249Z-38d19e88533d}},
note = {Snapshot 20260927T113249Z-38d19e88533d, sha256 38d19e88533d95e55121e0f5d65fae0b8eadc901da613513af6849b4bced2ee7; accessed 2026-09-27}
}Intégrer un tableau ou un graphique
Collez ce code dans n’importe quelle page. L’intégration est épinglée au même instantané, suit le thème clair ou sombre du lecteur et affiche toujours la source, la licence et un lien de retour.
<iframe src="https://datazimuts.com/embed/chart?dataset=wiki_company_attention%2Fwiki_company_attention_daily&lang=fr&theme=auto&snapshot=20260927T113249Z-38d19e88533d&x=as_of&y=views_60d&agg=avg" title="Wikipedia company-article attention velocity (daily)" width="100%" height="380" style="border:0" loading="lazy"></iframe>
Posez une question sur ce jeu de données. Les réponses viennent uniquement de sa fiche, de son profil mesuré et de son historique, et citent les faits utilisés.