PromptSharp › Daily briefs › Marketing › October 9, 2026

Marketing prompt of the day

October 9, 2026 · for Brand and growth marketers, agency strategists, content leads. One sharp, copy-paste prompt — free, every weekday.

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.

How to run “Metric dictionary: kill the double-counted number”, step by step

The situation this prompt is built for: Two dashboards disagree about 'leads' again — in front of your boss. Write the metric definitions document that ends the recurring argument. Below is exactly what to feed it and what comes back — no model-specific tricks, it runs the same in any chat AI.

Why this structure 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.

On Pro, pro personalization preloads your system list and past discrepancies so the dictionary starts from the conflicts your team has actually fought.

When to use it — and when not to

Reach for it when

• Two dashboards disagree about 'leads' again — in front of your boss. Write the metric definitions document that ends the recurring argument.
• You need the output in a shape you can forward as-is — the fixed structure above is the point.

Skip it when

• You don’t yet have the source material — the prompt is built to refuse to fake it. Its own guardrail: “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.” With nothing to work from, you’ll get a list of “not provided” flags, which is honest but not useful. Collect the inputs first.
• The task is genuinely one sentence long — a structured prompt earns its overhead when the output has parts. For quick one-off questions, just ask.

Adapting today’s prompt for adjacent roles

“Metric dictionary: kill the double-counted number” sits in the Analytics & Reporting lane of the marketing pool. If your seat is one desk over, these are the same craft-move rebuilt for the neighbouring workflow — pulled from the same curated pool, each free in full at its permalink:

You are a positioning critic pressure-testing a value proposition. I will paste our positioning and the material behind it. Produce: A) THE THREE-QUESTION TEST applied…

You are a marketing claims reviewer preparing copy for a qualified legal or compliance reviewer. This is preparation, never legal clearance — say so in your output. I…

You are an experimentation designer scoping an incrementality test. I will paste the channel context and constraints. Produce: A) THE DESIGN: the test type suited to my…

Common failure modes (and the fixes)

• Failure: letting the model drift past the prompt’s own guardrail — “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.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Mark every claim I should verify in my analytics or source systems before it is published or presented.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Never include customer personally identifiable information or client-confidential terms.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: accepting the first pass. Fix: reply with one line — “now cut everything that is generic to any company and keep only what is specific to mine” — the cheapest quality doubling available.

Quick answers

Is “Metric dictionary: kill the double-counted number” free to use?

Yes — every weekday issue of the PromptSharp Marketing Brief publishes one full pool prompt free on the web, and it stays free in the archive. Pro is the daily full prompt set, personalization, and MCP delivery — not a paywall on this page.

Which AI model does this prompt work with?

Any of them. Every PromptSharp prompt is model-agnostic plain text — ChatGPT, Claude, Gemini, Copilot, or a local model. No plugins, no custom GPTs; paste and run.

How is the marketing prompt of the day chosen?

Deterministic rotation over the curated marketing pool — currently 51 prompts across 5 sections — the same single source the paid brief reads. Same date, same prompt: the archive never silently changes under you.

How do I get this in my inbox instead?

The capture form above. The PromptSharp Marketing Brief email edition lands most weekday mornings, plus a Sunday roundup; the web issue stays free here either way.

More daily AI prompt briefs

The same free weekday format, tuned to other crafts:

• PromptSharp Finance — for Investment banking, sales & trading, equity research, FP&A
• PromptSharp CPG Brief — for Brand managers, category managers, insights & shopper teams
• PromptSharp Sales Brief — for AEs, SDRs, sales leaders, RevOps
• PromptSharp Consulting Brief — for Management consultants, corporate strategy, biz-ops
• PromptSharp Product Brief — for PMs, product ops, founders wearing the PM hat
• PromptSharp Dev Brief — for Software engineers, tech leads, engineering managers
• PromptSharp Vibe Coding Brief — for Founders, PMs, designers, analysts — anyone building real software with AI without an engineering background
• PromptSharp C-suite Brief — for CEOs, CFOs, CMOs, CTOs, COOs and their chiefs of staff
• PromptSharp Law Brief — for Solo & small-firm attorneys, litigation & transactional associates, in-house counsel
• PromptSharp Personal Finance Brief — for Anyone running their own money — budgets, investing, taxes, and the rent-vs-buy / home-buying decisions that dwarf every other line item
• PromptSharp Career Brief — for Job seekers, career changers, anyone negotiating an offer
• PromptSharp Focus Brief — for Anyone who wants external structure for deep work — ADHD-friendly by design
• PromptSharp Learning Brief — for Self-directed learners — languages, skills, certifications, exam prep
• PromptSharp Health & Fitness Brief — for Anyone training, eating better, or building durable habits
• PromptSharp Travel Brief — for Trip planners — itineraries, deals, points, family logistics
• PromptSharp Students — for College students (undergrad + grad) — study, research, essays with integrity, exam prep, applications
• PromptSharp Trading — for Self-directed retail traders and active investors — risk and position-sizing thinking, regime awareness, journal review, bias-checking, earnings prep. Your own account, your own process.

← 2026-10-08 · All Marketing issues · 2026-10-12 →