Skip to main content
You do not need a long prompt. You need a request that removes ambiguity from the decision and from what Marketer may do next.

Use the request formula

A strong request contains:
  1. Outcome — the question to answer or artifact to produce
  2. Source — the connected system that should provide the evidence
  3. Scope — the account, campaign, product, audience, or workspace in bounds
  4. Window — exact dates or completed periods
  5. Measures — the metrics or quality criteria that matter
  6. Constraints — definitions, exclusions, and business rules
  7. Output — the format you want
  8. Action boundary — read, draft, ask for approval, or execute under policy

Start from these patterns

Performance analysis

Creative brief

Campaign preparation

Replace vague language

Ask for decision-ready output

Tell Marketer how you will use the result. A useful structure is:
  • Finding: what changed
  • Evidence: source, dates, scope, and values
  • Interpretation: the most likely explanation and uncertainty
  • Recommendation: the proposed next step
  • Approval: what would change and what control applies

Refine without restarting

Use follow-ups to correct one dimension at a time:
  • “Use only Google Ads. Remove Shopify figures.”
  • “Recalculate in the workspace timezone using complete days.”
  • “Limit the answer to the attached campaign.”
  • “Keep the recommendation, but turn it into a draft with no write actions.”
  • “Show the source and calculation behind the first claim.”
A prompt cannot expand your role or bypass workspace controls. Guardrails, autonomy settings, provider permissions, and approval gates still apply.
Before acting on the output, use Review results.
Last modified on August 7, 2026