Data Studio pharma dashboards for brand and commercial teams

What does a pharma dashboard show a brand team?

It shows whether the brand is on plan and where the gap is. The pharma dashboard we built in Data Studio for a healthcare and pharma client covers brand performance on one set of pages, starting with the headline and drilling to state, product and rep.

The views are the ones a brand lead asks for before a quarterly business review, arranged so the national picture comes first and the field detail second.

• Sales and prescription (Rx) volume by week or month.
• Product performance across the portfolio and by strength or pack where the data allows.
• Sales by state on a filled map.
• Top reps ranked on the agreed measure.
• HCP metrics: prescribers reached, called on and writing.
• Actual versus forecast by product, with the variance highlighted.

Which data sources feed a commercial pharma report?

Usually four or five, each with its own refresh rhythm and its own idea of a territory. Syndicated prescription data from the large data vendors arrives weekly or monthly at prescriber or geography level. Veeva CRM holds call activity, samples and HCP targeting. Specialty pharmacy and hub data adds dispense, referral and patient start counts for specialty brands. Finance supplies ex-factory sales and the forecast.

Aligning them is the real work. We build one product hierarchy, one HCP master keyed on the identifier your data uses, and one territory alignment table, then join everything in BigQuery or a governed Google Sheet. Data Studio blends cap at five sources with equality joins only, which is not enough for a full commercial model, so the joins happen upstream.

We also plan for restatements. Syndicated vendors often revise recent weeks, so the pipeline reloads a rolling window rather than appending, and the report shows the data-through date on every page.

How do you keep patient privacy out of the dashboard?

By never bringing patient-level records into the reporting layer. The pages show aggregated counts, such as prescriptions by prescriber, by state or by week, and hub or specialty pharmacy figures arrive already summarized. Small-cell counts can be suppressed or grouped where your policy calls for it.

Healthcare data is subject to privacy rules such as HIPAA in the US and equivalents elsewhere. We work within the policies your compliance and legal teams set and follow their direction on what may be stored and shown. We are not lawyers and do not give legal or regulatory advice.

Can each rep see only their own territory?

Yes. Field reports usually need row-level access, so a rep sees their territory, a district manager sees their reps, and head office sees the nation. We do this with a data source filter on the viewer's email, matched to the alignment table, or with BigQuery row-level policies for larger teams.

Credentials matter here. Viewer's credentials make Data Studio check each person's own access to the data, while owner's credentials show the report as the owner sees it, so the filter has to be in place before a field-wide link goes out. We test with real accounts from each level before launch.

How should forecast versus actual be shown?

As variance against a forecast that is versioned and dated. Brand teams reforecast during the year, so a single forecast column loses the history of what was promised. We store each forecast version and let the viewer pick the comparison with a parameter, so the original budget and the latest reforecast are both a click away.

Variance is shown by product, by month and by state, with calculated fields that flag where actual falls outside a tolerance you choose. That turns the page into a list of conversations for the next field meeting.

Why does pharma commercial experience matter for a pharma dashboard?

Because the hard questions are about the business, not the charts. Harsh Khubchandani, our Director of Automation and Analytics, began his career at ZS in pharmaceutical commercial operations, and our team brings experience from top consulting firms. We know why a TRx trend and an NRx trend can point in opposite directions, why call plans and alignments change mid-cycle, and why a brand lead wants the data-through date in the corner of every page.

As a data studio agency, we pair that domain knowledge with the build work: modeling in BigQuery, report design in Data Studio and scheduled delivery of a PDF summary to leadership each week. On Data Studio Pro, content can be owned by your organization's Google Cloud project, with audit logging.