Jev analytics event kind

Classify an analytics event by what happened

Give an event description to distinguish navigation, purchases, account changes and support requests. The described activity takes precedence over a misleading event name.

What activity does this event describe?Live API
Try an example

Original input for the Navigation 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 activity, not the event name alone.

Decision rules and labels
NavigationPurchaseAccountSupportNeed 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

A checkout-page view is not a purchase.

The event name can describe a location rather than an outcome. The misleading-name fixture views a checkout page but completes no order, so it belongs under Navigation in this taxonomy.

A profile change and a support submission may both come from a form. Their purposes distinguish Account from Support. The input must describe the activity that actually occurred.

This is a semantic intake label. Event schema validation, payment verification, duplicate detection and aggregate counts belong to separate checks; the model does not reconstruct telemetry from an event name.

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 one spreadsheet row producing two separate classification results
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 analytics event categories.

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

    Add the information to check

    Give an event description to distinguish navigation, purchases, account changes and support requests.

  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 Navigation, Purchase, Account, Support, 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
Page openedNavigation95.0%
Order completedPurchase100%
Profile changedAccount100%
Help requestedSupport100%
Misleading nameNavigation100%
No 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

  • Reviewing meaning in inconsistently named events
  • Testing a small analytics activity taxonomy
  • Replaying the exact synthetic requests and inspecting their distributions

Outside this demonstration

  • Counting purchases from unverified page names
  • Replacing structural telemetry validation
  • Treating six fixture expectations as measured production accuracy
Example FAQ

Questions about analytics event kind.

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

Can event names be useful evidence?

Yes, when their meaning is established, but they are not authoritative in this example. The description and verified activity take precedence over a misleading name.

Does Purchase confirm a payment succeeded?

No. It labels the supplied description. Payment success must come from the transaction system and should not be inferred by this classifier.

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 analytics event kind input

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