Building a dashboard

A view you keep rebuilding by hand is worth asking for once. Name the metrics and the comparison.

If you assemble the same numbers every week, build the view once in Dashboard Studio

and keep it. The requests that work name only the metrics the team actually reads.

Template

Build a dashboard titled "[name]" in Dashboard Studio.
Sources: [the connectors to use].
Metrics: [the three or four you actually check].
Compare each against [the prior period of the same length].
Break down by [campaign / channel / placement].

What makes a dashboard get opened twice

  • Name only what you read. A dashboard with thirty tiles is a dashboard nobody

opens. Three or four numbers with a movement against them is a dashboard that gets

checked.

  • Always give a comparison period. A number on its own is not information.

  • Say which connector the data should come from when more than one could supply it,

or the figures will not match the platform your team argues about.

  • Say what to do when a source is missing. If a connector is not available, state

whether to leave the tile out or substitute another source.

Live views from review data

Dashboards are not only for spend. Marketplace and app-store review data works the same

way.

Build a live dashboard tracking [brand] product reviews across
[marketplaces or app stores]. Show rating movement, review volume and
the themes behind negative reviews, refreshed daily.
Did this answer your question?
😞
😐
😁