Metrica Fundamentals
Learn how Metrica organizes inventory, coverage, signals, naming, and public-safe measurement language for DOOH planning.
Certificate
Finish the course and verify your result
Minimum score
80% to pass and receive the certificate
Public verification
Share the public ID and anyone can check it.
Course lessons
This course brings together the essentials to understand the topic, apply it, and validate it clearly.
Metrica as the operational source of truth
Metrica is Taggify’s operational layer for geography, inventory, audiences, mobility, points of interest, coverage, and measurement signals.
A user should read Metrica as a decision support system, not as a generic reporting dashboard. The practical question is whether a market, city, zone, or screen set has enough clean evidence to plan, forecast, activate, or explain a DOOH campaign.
The public-safe way to describe Metrica is simple: it helps teams understand where inventory exists, what context surrounds it, what signals are available, and how confidently that evidence can support a campaign decision.
Lesson 1
Naming that prevents confusion
Metrica documentation is explicit about naming: similar words can describe different phenomena. For example, an internal slot-yield proxy should not be presented as full visual OTS.
The safe habit is to name the thing by what it actually represents. Coverage describes availability or completeness. Readiness describes whether the data is usable. Modeled impact describes an estimated audience or exposure signal. Slot economics describes how many impacts a slot may represent under a planning model.
This naming discipline matters because buyers, operators, DSP flows, and reports all consume Metrica output differently. The Academy should teach the high-level meaning without exposing formulas, thresholds, or proprietary heuristics.
Lesson 2
Coverage, readiness, and missing reasons
A good Metrica workflow starts with coverage. The operator checks whether the target country, city, area, or screen set has enough signals for the job at hand.
Readiness is not a single magic number. It is a practical status built from available inventory, valid location data, screen metadata, traffic or mobility context, audience signals, and operational constraints.
When something is not ready, the system should make the reason visible. Missing coordinates, incomplete taxonomy, weak upstream metadata, unavailable photos, or insufficient coverage are different problems and require different actions.
Lesson 3
How to use Metrica in planning
The planning workflow is inspect, understand, decide, and only then execute. Operators first define scope, then inspect available inventory and signals, then review gaps, and finally use the output in forecasting or campaign setup.
Metrica is especially useful when DSP or commercial users need defensible answers: which screens are available, what context they sit in, what signals support the recommendation, and what should be avoided because the evidence is weak.
The most important habit is separating inspection from execution. Metrica should help the operator see the system clearly before changes are pushed into campaign, billing, or bidder workflows.
Lesson 4
Public-safe reporting language
Public reporting should focus on understandable evidence: geography, inventory coverage, delivery consistency, contextual fit, planning confidence, and operational learnings.
Do not expose internal formulas, proprietary thresholds, raw provider assumptions, sensitive upstream diagnostics, or broad claims that the data cannot support.
A good Metrica explanation gives a buyer confidence without pretending that every signal is perfect. It names what is known, what is modeled, and what still needs review.
Lesson 5
Quiz
Validate what you learned
Answer every question. If you meet the minimum score, Admin V2 issues a verifiable certificate.