Jev ad awareness cue

Identify what an ad message focuses on

Paste ad copy to distinguish a problem, a solution approach or a named product. Review mixed messages without guessing what an individual reader knows.

What knowledge does this message foreground?Live API
Try an example

Original input for the Problem focus outcome. Edit the evidence to send a new request.

Source: Background discussion on X

Source and example scope

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Classify the main message focus.

Decision rules and labels
Problem focusSolution focusProduct focusMixed focusNeed evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

Message focus does not reveal a person’s knowledge.

This rubric labels what the copy foregrounds. It does not infer whether an actual reader knows a problem, a solution or a product, and it does not assign psychological traits to an audience.

A product name can be incidental. The fifth example centers a remedy approach despite mentioning ParseBox. Mixed focus keeps equally central message levels visible.

The source discussion includes awareness-stage tagging. This adaptation narrows the task to observable text cues, with fictional excerpts and no predicted ad response.

These fictional inputs and decision rules were written for this page. The linked X discussion provides background; the technical implementation follows TypeSafe's Choice contract.

Illustration of selecting a caption token for emphasis in an edit timeline
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for ad message focus.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Paste ad copy to distinguish a problem, a solution approach or a named product.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Problem focus, Solution focus, Product focus, Mixed focus, Need evidence. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Need evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Difficulty onlyProblem focus99.0%
Remedy approachNeed evidence81.0%
Named productProduct focus100%
Equal problem and productMixed focus99.0%
Product name is incidentalSolution focus97.0%
No excerptNeed evidence100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 5 of 6 results matched the authored fixture expectations. For Remedy approach, the expectation was Solution focus; the observed choice was Need evidence.Verified

Understand the results

Source and example scope

Compare each saved result with its authored expectation. A disagreement remains in the fixture review; the call is not repeated to obtain a preferred label.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Organizing copy by its foregrounded message
  • Testing incidental versus central product mentions
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Inferring a person’s beliefs or psychological traits
  • Predicting campaign results from a copy label
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about ad awareness cue.

The rubric explains the decision; the application owns the next step.

Does Product focus mean the audience knows the product?

No. It means the message centers a named product. The reader’s prior knowledge is outside the supplied evidence.

Is this a conversion prediction?

No. It is a descriptive text classification. Any relationship to campaign outcomes would require a separate measured study.

Does the leading probability measure production accuracy?

No. It is the model distribution for this one request. The six examples are functional checks with authored expectations, not a representative benchmark. Inspect disagreements and evaluate your own examples before using the label.

What happens when the API fails?

The window shows an error and supplies no fresh judgment. The downloadable runner sends one request without retries. Need evidence is a valid outcome about incomplete input; it does not stand in for a network or provider failure.

Try your own ad awareness cue input

Edit the evidence above or use the Playground to test another bounded question.