Jev ad creative format

Classify the structure of an ad creative

Describe an ad's content to compare a product demonstration, customer testimonial and problem-solution format. The result labels its structure, not its performance.

How is this creative structured?Live API
Try an example

Original input for the Demonstration 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 described creative structure.

Decision rules and labels
DemonstrationTestimonialProblem solutionMixed formatNeed 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

Format describes structure, not success.

A demonstration shows use, a testimonial centers on a customer’s account, and a problem-solution creative organizes its message around a difficulty and remedy. Those structures can be described without estimating conversions.

The misleading-title fixture tests the description rather than an existing label. Mixed format preserves an equally central combination that a one-format taxonomy would otherwise hide.

These are fictional text descriptions. They do not copy an ad library, verify a testimonial or reproduce the source post’s claimed volume, time or cost.

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 creative format.

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

    Add the information to check

    Describe an ad's content to compare a product demonstration, customer testimonial and problem-solution format.

  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 Demonstration, Testimonial, Problem solution, Mixed format, 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
Product walkthroughDemonstration100%
Customer accountTestimonial99.0%
Problem and remedyProblem solution95.0%
Two equal partsMixed format100%
Named testimonial without customerDemonstration99.0%
No creative descriptionNeed 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. 6 of 6 results matched the authored fixture expectations.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 creatives by observable structure
  • Reviewing mislabeled creative descriptions
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Predicting conversion or attention from a format label
  • Treating a fictional testimonial as an actual endorsement
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about ad creative format.

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

Does Testimonial verify the customer’s claim?

No. It identifies the creative structure described in the input. Authenticity and factual support require separate evidence.

Can a creative use several formats?

Yes. This rubric uses Mixed format when two are equally central. A production library may need multi-label fields instead.

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 creative format input

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