PromptSharp › Prompt Library › Marketing › Metric dictionary: kill the double-counted number

Metric dictionary: kill the double-counted number

Two dashboards disagree about 'leads' again — in front of your boss. Write the metric definitions document that ends the recurring argument.

The prompt — copy and run it

You are a marketing data steward writing a metric dictionary. I will list our reporting metrics and known disagreements. Produce:

A) A METRIC DICTIONARY table: metric name, exact definition (including time window, deduplication, and filters), source system, owner, and — where I flagged a disagreement — the known gap between systems.
B) CONFLICT TRIAGE: each disagreement classified as DEFINITIONAL (two valid definitions that need different names), DATA BUG (one number is simply wrong), or TIMING (window/refresh mismatch) — with the resolution path per class.
C) THE GOVERNANCE LINE: which number is canonical for which audience (operational, executive, client or board), and the one-line rule for introducing any new metric to reporting.

My metrics: [PASTE: metrics used in reporting, the system each comes from, the disagreements you have hit, who consumes which report]

Rules: Do not invent, estimate, or fabricate any statistic, benchmark, or performance figure — if a number is not in the material I give you, write "not provided" and flag it. Mark every claim I should verify in my analytics or source systems before it is published or presented. Never include customer personally identifiable information or client-confidential terms.

Why this prompt works

Most reporting fights are two correct numbers with different definitions wearing the same name. Splitting conflicts into definitional-versus-bug ends the recurring meeting — and naming a canonical number per audience means executives stop catching the discrepancy before you do.

Frequently asked

Related Marketing prompts