Skip to main content

ClassifyContactPersonaResult

How one press of the Classify button ended, and what it found.

ONE ROW, not one per scope: Personas are product-wide, so a Contact has a single verdict. The ICP equivalent answers with a row per Brand because an Account holds one ICP per Brand.

type ClassifyContactPersonaResult {
contact_id: ID!
outcome: ContactPersonaClassificationOutcome!
persona_id: ID
persona_name: String
fit_level: Int
rationale: String
detail: String
status: ContactPersonaClassificationStatus!
}

Fields​

ClassifyContactPersonaResult.contact_id ● ID! non-null scalar​

ClassifyContactPersonaResult.outcome ● ContactPersonaClassificationOutcome! non-null enum​

CLASSIFIED (a Persona, or a confident no-match), NO_PERSONAS, NOT_FOUND, UNPROVISIONED, NOT_ELIGIBLE, NO_EVIDENCE, UNDETERMINED, UNUSABLE or FAILED.

ClassifyContactPersonaResult.persona_id ● ID scalar​

Null on a confident no-match as well as on every non-CLASSIFIED outcome.

ClassifyContactPersonaResult.persona_name ● String scalar​

ClassifyContactPersonaResult.fit_level ● Int scalar​

How firmly the evidence placed the Contact inside the Persona, 1-10.

ClassifyContactPersonaResult.rationale ● String scalar​

The classifier's own one-line summary. Only set on a CLASSIFIED outcome.

ClassifyContactPersonaResult.detail ● String scalar​

Why nothing was recorded, when nothing was. Set on the outcomes that explain themselves.

ClassifyContactPersonaResult.status ● ContactPersonaClassificationStatus! non-null object​

Returned By​

classifyContactPersona mutation

Product

PricingFAQPaminga vs. MarketoMigration CenterMarketo to Paminga TranslatorMarketo Alternative
Paminga Logo
LinkedInFacebookXYouTube
ISO 27001 CompliantSOC 2 Compliant

Built with pride in Denver, Colorado, USA

Copyright © Paminga, Inc. 2026
All rights reserved. Various trademarks held by their respective owners.