Overview
Query results appear as clusters of connected nodes. Each node represents either an Account in Persona, or a property of that Account. A line between an Account node and a property node means that the Account has that property. For definitions of these terms, see the Graph glossary.
The list of node properties below is for Persona flows using the Hosted Flow, Embedded Flow, and Mobile SDK integration methods. Server API integrations populate a different set of properties.
Properties
| Property | Description | Available on each Account? | Format |
|---|---|---|---|
| Account ID | The Account token | Yes | act_ prefix Example: act_zVbXMCv5oJioB4zkygCWetbT |
| Reference ID | The reference ID provided by your organization for the Account | If provided by your organization | Exact, case-sensitive match Example: username-123 |
| Birthdate | The Account’s birthdate | If on the Account, provided by your organization or collected in an Inquiry | YYYY-MM-DD Example: 1989-06-30 |
| Name | The Account’s full name | If on the Account, provided by your organization or collected in an Inquiry | Any word order; case- and accent-insensitive Example: John Smith, Smith |
| Email address | Any of the emails collected during one of the Account’s Inquiries | If on the Account, provided by your organization or collected in an Inquiry | Full address, or username@, or @example.com Example: jsmith@example.com |
| Email similarity | Links similar email addresses instead of requiring an exact match. | Not available by default. Your organization creates it as a custom node, and it then applies to any Account with an email address | |
| Phone number | Any of the phone numbers collected during one of the Account’s Inquiries | If on the Account, provided by your organization or collected in an Inquiry | Must include the country code; spaces, dashes, and parentheses are ignored Example: 1 201 555-1212, +44 7700 900077 |
| Address | Any of the primary addresses associated with an Account’s Inquiries. Addresses are normalized and validated before being added to Graph. | If a complete address is on the Account. Street, city, subdivision, postal code, and country must all be present | |
| Postal Code | The postal/ZIP code from an Account’s address, normalized separately from the full address so accounts in the same area link even when street lines differ. | If an address postal code is on the Account | Example: 90210, 90210-1234, H4A 1A1 |
| Selfie Similarity | Links Accounts whose selfie images are similar rather than exactly equal. | Only if your organization has it enabled, and the end user completed a Selfie verification. Not available in every region. Removed if the selfie is later redacted. | |
| Image Background Similarity | Links Accounts whose photos were taken in the same or similar physical setting, by comparing the background of the image. | Only if your organization has it enabled, and the Account has a retained photo. Appears under the name configured for your organization. | |
| Camera Fingerprint | Sensor-level fingerprint of the capturing camera, linking accounts that submitted photos from the same physical device. | Limited availability, and must be enabled for your organization. Requires a photo capture that reported camera metadata. | |
| Browser fingerprint | Any of the Browser Fingerprints collected during one of the Account’s Inquiries | If the end user opened the Inquiry in a browser (hosted, embedded, or the web view inside a Mobile SDK), or from a Sentinel session. Not available for Accounts created only via API. | Opaque string Example: 1f7e7abc6515fa932b4cdf12b11 |
| Device fingerprint (Browser) | Any of the Device Fingerprints collected during one of the Account’s Inquiries | If the end user opened the Inquiry in a browser and device fingerprinting is enabled on the Inquiry template (enabled by default when Graph is set up). | Opaque string Example: PTW93ZArKL8c3v4hVUMV |
| Device Fingerprint (Mobile SDK) | Any of the Device Fingerprints associated with one of the Account’s Inquiries A Device Fingerprint is the unique identifier for a device provided by the Android/iOS operating system. | Only for Inquiries completed via a Mobile SDK integration | UUID Example: 7bab59c4-6be9-4bc9-ba8f-e3f8a130701f |
| Device Token | A persistent device identifier Persona sets and stores client-side. | If a device was recorded for the Account, from a browser or Mobile SDK session. Not available for Accounts created only via API. | |
| IP address | Any of the IP addresses used when completing one of the Account’s Inquiries | If the end user made a request to Persona, from an Inquiry session or a Sentinel session. Not available for Accounts created only via API. Private, loopback, and iCloud Private Relay addresses are excluded. | Full IPv4 or IPv6 address Example: 203.0.113.42 |
| Government ID number | Any ID number associated with a Government ID collected during one of the Account’s Inquiries | If a Government ID verification captured an ID number, or your organization provided one. Social Security Numbers are excluded, and become SSN nodes instead. | Letters and numbers only, no dashes or spaces; more than 5 characters Example: F12345678 |
| Government ID Document Number | The document’s own serial/document number. | Only for Inquiries with a completed Government ID verification whose document was successfully processed | |
| SSN | Any of the Social Security Numbers collected during one of the Account’s Inquiries | If a full 9-digit SSN is on the Account | numbers only, no dashes Example: 123456788 |
| Last 4 SSN | Only the final four SSN digits. Links accounts in flows that collect SSN4 rather than a full SSN, where the full-SSN node would never match. | If only the last four digits of an SSN are on the Account. An entry produces either an SSN node or a Last 4 SSN node, never both. | |
| Created at | The time at which the Account was created | Yes | YYYY-MM-DD HH:mm:ss (24-hour), in your dashboard profile’s timezone |
| Custom Node (Node Functions) | A node type defined by you, letting you link Accounts on data Persona doesn’t natively model: a hashed credit-card number, an internal user ID, a bank-account token, anything listed on an Account or Inquiry field. | Only for the data your organization maps into the node. Accounts that existed before the node was created show it only after a data sync. | Depends on the functions you configure |
Good to know
- Phone numbers must include the country code. A bare 10-digit US number is rejected without it.
- Government ID numbers must be typed without punctuation.
- A 5-digit ZIP code search also matches ZIP+4 postal codes.