ContextHint
Quality rubric

Context Hint Scoring: A Practical 100-Point Rubric

Grade the quality of the instruction before you confuse polished wording with campaign performance.

Important distinction

This is an editorial preflight rubric. It is not an OpenAI Ads score, delivery prediction, conversion score, or the within-niche targeting AUC returned by the ContextHint generator and MCP.

Score each dimension independently, then inspect the weakest dimension before rewriting. The total helps teams review consistently; the explanation behind each score is more valuable than the number itself.

The five scoring dimensions

20points

Audience clarity

The buyer, team, or use case is identifiable without becoming a full persona.

25points

Need specificity

The instruction names a concrete job, pain, outcome, or evaluation task.

20points

Situational relevance

A trigger, workflow, comparison, or constraint explains when the offer fits.

20points

Offer alignment

The hint, creative, landing page, and ad-group theme make the same promise.

15points

Natural variation

The wording is descriptive enough for semantic matching without collapsing into keywords or over-constraining phrasing.

How to interpret the total

85–100Ready to test

Focused and aligned enough to become a clean campaign hypothesis.

70–84Revise one dimension

Usually workable, but one weak area may admit irrelevant conversations or obscure fit.

Below 70Return to the brief

Rebuild the buyer, need, or situation before polishing individual words.

A high writing score is not a winning-ad claim

The rubric evaluates whether the context hint is clear and testable. It cannot see private auction mechanics or prove which wording caused a conversion. Use a clean testing workflow and evaluate business outcomes in your own Ads Manager data.