Content Analytics Dashboard for Media Teams.
INDUSTRY
Digital media & publishing
DATA SOURCES
GA4 + Google Search Console
DASHBOARD LAYERS
Audience, Content, Search
IN THIS CASE STUDY
Running a media platform or publication? Let’s talk about what a unified editorial intelligence system would look like for your team.
THE SITUATION
Traffic Without Editorial Clarity
Most digital media companies are measuring traffic. Few are measuring what that traffic actually means for their business — which content builds loyal readers, which drives one-time visits, and where the gap between search visibility and audience growth is quietly widening. This case study walks through how coreVIEW built a unified content analytics dashboard for a digital media company, connecting GA4 and Google Search Console into one editorial intelligence system for the first time.
Google Analytics 4 showed what was happening on the site — who came, what they read, how long they stayed. Google Search Console showed what was happening in search — what people were looking for, where the site ranked, how often it got clicked. Neither told the full story on its own. And nobody had ever connected the two.
THE BUILD
A Unified Editorial Analytics Dashboard
We connected both platforms into a unified dashboard with three layers — audience intelligence for the editorial team, content performance for the editor-in-chief, and search visibility for the SEO and growth team. Each layer was designed around the specific decisions each team needed to make. Not a generic analytics view, but a system built backwards from the questions that came up in every editorial meeting.
GA4
GSC
→
One editorial intelligence system
The audience layer segmented readers into casual visitors, loyal readers, and brand lovers — each with distinct behaviour profiles. The content layer mapped individual articles against audience segments, showing not just how many people read each piece but which audience type it attracted and retained. The search layer surfaced the gap between impressions and clicks, making it possible to see where the site was visible but failing to convert.
THE SHIFT
From traffic reporting to editorial intelligence
Before the dashboard, the editorial meeting started with a pageview number. After it, the conversation started with a question: who are we actually reaching, and is that who we are building for? That shift — from reporting what happened to asking whether it mattered — is the difference between a metrics tool and a decision system.
Three teams walked away with something they had not had before: a shared, connected picture of how the publication’s content was performing across the entire reader journey, from first search impression to loyal reader behaviour.
EDITORIAL TEAM
Content strategy
A clear picture of which content builds loyal readers versus drives one-time traffic — and what to produce more of for each goal.
COMMERCIAL TEAM
Audience pitch
An accurate audience profile for sponsorship and advertiser conversations — one that reflected who was actually reading, not just the total traffic number.
GROWTH TEAM
Search strategy
CTR gaps and keyword opportunities surfaced and prioritised — with a clear view of where visibility was high but conversion was broken.
THE OUTCOME
GA4 and GSC Connected Into One System
The combined dashboard gave the editorial, commercial, and growth teams a shared starting point for every strategy conversation. Not three separate reports from three separate tools — one connected system where every question about audience, content, and search could be answered from the same picture.
2 → 1
GA4 and GSC unified into a single editorial intelligence system — connected for the first time in the publication’s history.
Live
Real-time performance by article, author, category, and audience segment — updated continuously, not assembled in weekly reports.
HOW WE DID IT
The engagement from start to finish
This was a full decision system build. From initial data audit to live dashboard handover, the engagement followed five structured stages — each designed to ensure the finished system reflected the decisions leadership actually needed to make, not just the data that was available.
01
Audit
Full review of GA4 configuration, GSC setup, tracking gaps, and data quality across both platforms.
02
Connect
GA4 and GSC joined into a unified data model. Audience segments defined and applied consistently across both sources.
03
Build
Built on Looker Studio and connected via Google’s APIs, the dashboard required no new tools — only a unified data model that had never existed before.
04
Handover
Full team walkthrough per layer, documentation, and a 30-day support window for adjustments and questions.