Home
Reporting overview
daily| Article | Category | Editor | Published | Pageviews | First 3 days | New visitors | Top channel | Score v1beta |
|---|
Just published
last 3 days| Article | Category | Editor | Published | Pageviews | First 3 days | New % | Avg time | Top channel |
|---|
Articles
Data source & BigQuery mapping
This dashboard runs on two sources. Everything visible today is shaped to match the BigQuery export, so it can be wired to the live table without restructuring.
Live feed: one published Google Sheet (BigQuery → scheduled query → sheet → publish-to-web CSV), one row per article per day — columns date_day · pagepath · pageviews · pct_new · pct_mobile · top_channel · editor · title · category · post_type · yoast_seo_score · post_date. Traffic, the period selector, the daily trend and sparklines run off the aggregate; editor, title, category, article type and SEO come from the designboom_posts join now folded into the same query.
1 · bigquery — traffic (live source)
Live table daaily-ssa.dataform_final.fct_pageviews — a flat events table, one row per event. Aggregated to per-article rows on pagepath where event_name = 'page_view'. Source for pageviews, channels, geo, device, language, and new-vs-returning.
2 · wordpress join — editorial (live)
Editor, article type, SEO score and publish date come from the designboom_posts join (author / Yoast / publish date), now merged into the feed query. Only write time (manual time-log) and Score v1 stay beta until write-time lands.
field → source mapping
| article url | pagepath | BigQuery |
| title | title (often empty → WP) | BigQuery / WP |
| category | derived from pagepath | BigQuery |
| pageviews | count of event_name = 'page_view' rows | BigQuery |
| new vs returning | first_time_visit | BigQuery |
| mobile share | device.mobile | BigQuery |
| top channel | channel_group | BigQuery |
| top country | geo.country_name | BigQuery |
| published date | post_date (WordPress publish date) | WordPress |
| first 3-day pageviews | daily pageviews summed over post_date + the two days after — only when the launch falls inside the tracked window | Derived |
| avg time on pagebeta | duration — often null / sparsely populated | BigQuery (partial) |
| scroll depth | no source — only page_view events exist, no scroll event | missing |
| editorbeta | WordPress author | WordPress |
| article typebeta | WordPress | WordPress |
| seo scorebeta | Yoast (WordPress) | WordPress |
| write timebeta | manual time-log | Manual |
| engagement score v1beta | computed once inputs above land | Derived |
Raw sample · exactly as exported
Full BigQuery schema · fct_pageviews · 41 columns
| Article | Category | Editor | Published | Pageviews | First 3 days | First-3d % | Peak day | New % | Mobile % | Top channel | 15-day trend | Avg timebeta | Write timebeta | SEO | Score v1beta |
|---|
Editors
About this data
Editor attribution is live. Names come from the designboom_posts join — internal author, or the internal editor (last_edit_by) for reader / guest submissions. Only the confirmed designboom editorial team is counted as staff; every other byline is treated as a guest / reader submission. Traffic and SEO are real; write time and Score v1 stay beta until write-time lands.
| Editor | Published | Articles | Total pageviews | Avg / article | New % | Mobile % | SEO |
|---|
Time log
| article | editor | hours | seo | date |
|---|
Priority Content Lab
Traffic over time
Chapters
Evergreen performers
Boosted content
Editor scorecards
Category performance
Article lifetime
Benchmarks
Every article, measured against the typical story in its own category. The vs median column compares each piece's pageviews to the median for its category — architecture, design, art or technology — so you can see at a glance what over- or under-performed relative to its peers, not against the whole site. Green means it beat the category median; red means it trailed it. Runaway outliers (10× or more above the median, common in low-volume categories like art) are shown as a compact multiplier — e.g. 261× — instead of a five-digit percentage; hover for the exact figure.
| Article | Category | Editor | Published | pageviews | first 3 days | vs median | top channel |
|---|
Article lab
Two tools. Write a first draft in the designboom voice from a press release or a dictated brief, then turn any finished draft into a publish pack — SEO title, alternate headlines, meta description and keywords, channel-ready posts for LinkedIn, Facebook and X, and clean tags and entities. Everything's one click to copy.
Paste a press release or notes, upload a PDF, or dictate a brief out loud. Check whether it's even a designboom story, then write a first draft in the house voice — grounded only in what you give it, plus cited public context if you switch enrichment on. Always edit and fact-check before publishing.
Story desk
External design stories from the team's shared source library, pulled live from RSS. Claim a story, add your thoughts, connect it to prior designboom coverage, then hand it to the Article Lab. Any editor can add a source and everyone gets its stories.
Pitch desk
Where the day's stories start. Anyone can pitch an idea — from a website, Instagram, a press release, a contributor or an exclusive. The managing editor and editor-in-chief review and plan them into the calendar — usually for the next day, which makes for stronger stories and a team that can organise itself.
Voice Studio
The designboom voice the AI writes with — editable, versioned, reversible. Editorial leads and admins can edit it, so the editor-in-chief and managing editor own the voice. Change the house style or the drafting brief and save it as a new version (it goes live immediately across the draft writer, AI pack and social tools). Roll back to any earlier version anytime. Below, review the rule changes the model proposes from how editors actually edit its drafts.
Copy
The visible headings, subheadings and page text across the newsroom — editable here, no code. Edit a field and Save; changes go live for everyone immediately. Leave a field blank (or hit ↺) to fall back to the built-in default. Formatting like bold uses <strong>…</strong>.
Users
Who can sign in to the newsroom — managed here, no Firebase console. Add a person by their @daaily.com Google address and pick a role. Member gets general access; Editorial lead also gets the Pitch Desk review & planning view; Admin also gets Voice Studio, Copy and this page. Changes take effect the next time they load the app.
Trends
Trend feed not connected yet.
External design trends will surface here in Phase 2, once the Feedly feed is linked — to spark coverage ideas.
Import GA4 / BigQuery
click to upload or drag & drop the csv here
expects the fct_pageviews export columns (pagepath, channel_group, …)