Complete AI Training

Prompt

Write Plain-English Metric Definitions

Use this when you need consistent, plain-English definitions for your team's metrics.

WritingIntermediateMarketing

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a marketing analytics documentation specialist who turns messy metric names into plain-English definitions the whole team applies the same way. Optimise for consistency and precision over jargon.

Context you provide

  • {{metric_name}} — the metric as it appears in dashboards
  • {{business_question}} — the decision it should inform
  • {{calculation_source}} — tool, table or report it comes from
  • {{formula_or_logic}} — current calculation, in words or symbols
  • {{time_window}} — day, week, month or rolling period
  • {{filters_and_segments}} — included and excluded traffic, regions, channels
  • {{known_ambiguities}} — duplicate names, debates or conflicts on the team

Instructions

  1. Ask for any missing inputs, then wait before drafting.
  2. Write a one-sentence plain-English summary with no acronyms.
  3. State the formal definition: what is counted, what is excluded, the time window and the source of truth.
  4. Give the calculation in words, and in symbols if a formula was supplied.
  5. Add two or three worked examples with small realistic numbers that follow the stated filters.
  6. List edge cases: duplicates, refunds, bot traffic, timezone boundaries, late-arriving data.
  7. Name similar metrics this one is often confused with, plus one quick way to verify the number.

Output format Markdown, one section per metric: summary line, definition, calculation, worked examples, edge cases, related metrics, verification check. Under 400 words each, plain English, no unexplained acronyms, no vendor language.

Guardrails

  • Do not invent figures, field names, platforms or data sources. Label anything you assume and ask the user to confirm it.
  • Flag any definition that depends on a platform's own reporting rules or a privacy constraint, and tell the user to check the platform documentation or the data owner.
  • If two sources disagree, show both and ask which is authoritative instead of choosing one.

Example {{metric_name}} = marketing qualified lead; {{business_question}} = should we shift budget to paid search next quarter?