OmniView Return Codes Reference Guide
Reference for the return codes from OmniView, a part of Experian's Offline Identity Resolution product
This document is a reference guide for OmniView 5-byte return codes. It highlights information from the API Developers guide and distills the relevant information for the OmniView-specific identity resolution outcomes that indicate what happened during the assignment/linkage process.
The OmniView identity resolution system is part of Offline Identity Resolution.
Below are the four different OmniView return code families, a description, and the potential return codes.
| Family | Description | Codes |
| V-series | Normal identity resolution | VB000, VC000, VE000, VG000 |
| B-series | Blocklisted input | BB000, BC000, BE000, BG000, BH000 |
| E-series | Validation failed / processing errors | E0018, E0019, E0020, E0021, E0022, E0023, E0024, E9999 |
| N-series | Nameless / channel-only | N0000, NB001, NC001, NE001, NB002, NC002, NE002, N0006 |
Every OmniView return code at a glance. Full definitions and worked examples follow in the sections below.
| Series | Code | Meaning | Confidence |
| V-series | VB000 | Both repositories | Highest |
| VC000 | Client repository match | High | |
| VE000 | Experian match | Highest | |
| VG000 | Generated profile | High | |
| B-series | BB000 | Blocked + both | High |
| BC000 | Blocked + client | High | |
| BE000 | Blocked + Experian | High | |
| BG000 | Blocked + generated | Moderate | |
| BH000 | All addresses blocked | None | |
| E-series | E0018 | No usable input | None |
| E0019 | Address only, no name | None | |
| E0020 | Invalid name | None | |
| E0021 | Invalid channels | None | |
| E0022 | Malformed record | None | |
| E0023 | Processing error | None | |
| E0024 | Timeout failure | None | |
| E9999 | Inquire only, no match | None | |
| N-series | N0000 | No match | None |
| NB001 | Unique both | High | |
| NC001 | Unique client | High | |
| NE001 | Unique Experian | High | |
| NB002 | 2-5 across both | Low | |
| NC002 | 2-5 client candidates | Low | |
| NE002 | 2-5 Experian candidates | Low | |
| N0006 | 6+ candidates | Low |
The following return codes describe the V series family of OmniView identity resolution outcomes.
| Code | Meaning | Confidence | Summary |
| VB000 | Both repositories | Highest | Identity resolved in both repositories |
| VC000 | Client repository match | High | Identity resolved to an existing individual in the client repository only |
| VE000 | Experian match | Highest | Identity resolved to an existing Experian individual |
| VG000 | Generated profile | High | No existing match; new OmniView profile generated |
What it means: The record matched an existing individual in both client and Experian repositories.
Confidence: Highest — Corroborated across both repositories.
Threshold behavior: Not filtered; returned whenever matched.
Example
| Field | Example |
| Client Input Record | fname=Taylor | lname=Morgan | addr1=789 Pine Rd | city=Sample City | state=TX | zip=75001 |
| Experian Match | Both repositories matched: Taylor Morgan, 789 Pine Rd, Sample City TX 75001 — the same individual was found in the client repository and the Experian repository; identity corroborated across both sources. |
What it means: The record matched to one individual in a client repository.
Confidence: High - Successful client-repository identity match.
Threshold behavior: Not filtered; returned whenever matched.
Example
| Field | Example |
| Client Input Record | fname=Alex | lname=Rivera | addr1=123 Main St | city=Sampletown | state=CA | zip=90001 |
| Experian Match | Client repository record matched: Alex Rivera, 123 Main St, Sampletown CA 90001 — exact name + postal address resolved to one individual in the client repository; no Experian identity found. |
What it means: The record matched one existing individual in the Experian repository.
Confidence: Highest — Successful Experian identity match.
Threshold behavior: Not filtered; returned whenever matched.
Example
| Field | Example |
| Client Input Record | fname=Jordan | lname=Lee | addr1=456 Oak Ave | city=Example City | state=IL | zip=60007 |
| Experian Match | Experian repository record matched: Jordan Lee, 456 Oak Ave, Example City IL 60007 — exact name + postal address resolved to one Experian individual; no client repository identity found. |
What it means: No existing individual matched in any repository, so new ID(s) were generated.
Confidence: High - New identity — not a prior-record match.
Threshold behavior: Not filtered; returned when new IDs are generated.
Example
| Field | Example |
| Client Input Record | fname=Casey | lname=Newrecord | addr1=321 Elm Blvd | city=Exampletown | state=OR | zip=97035 |
| Experian Match | No repository match: Casey Newrecord, 321 Elm Blvd, Exampletown OR 97035 was not found in the client or Experian repository — a new OmniView profile was generated and new identifier(s) assigned. |
The following return codes describe the blocklisting family of OmniView identity resolution outcomes. Blocklisting is a process that prevents the incorrect merging of records due to things like generic or default emails and phones, or postal addresses for apartment buildings with no apartment numbers.
| Code | Meaning | Confidence | Summary |
| BB000 | Blocked + Both | High | One or more address channels available on input. At least one address channel is blocklisted. The input matched only to data in the client repository |
| BC000 | Blocked + Client | High | One or more address channels available on input. At least one address channel is blocklisted. At least one address channel is valid and matches to the Experian repository |
| BE000 | Blocked + Experian | High | One or more address channels available on input. At least one address channel is blocklisted. The input matched to both the Experian repository and client repository. |
| BG000 | Blocked + Generated | Moderate | One or more address channels available on input. At least one address channel is blocklisted. No existing match; new OmniView profile generated. |
| BH000 | All addresses blocked | None | All usable addresses suppressed; hashed-ID fallback. |
What it means: An individual matched in both client and Experian repositories, and at least one channel is blocklisted.
Confidence: High - Corraborated identity match despite suppressed channel(s).
Threshold behavior: Not filtered; always returned when blocklisted.
Example
| Field | Example |
| Client Input Record | fname=Taylor | lname=Morgan | addr1=789 Pine Rd | city=Sample City | state=TX | zip=75001 | email=shared@example.com (blocklisted) |
| Experian Match | Both repositories matched: Taylor Morgan, 789 Pine Rd, Sample City TX 75001 — the same individual was found in the client and Experian repositories via name + postal address; the blocklisted email 'shared@example.com' was suppressed. |
What it means: An individual matched in a client repository, and at least one channel is blocklisted.
Confidence: High - Strong client identity match despite suppressed channel(s).
Threshold behavior: Not filtered; always returned when blocklisted.
Example
| Field | Example |
| Client Input Record | fname=Alex | lname=Rivera | addr1=100 Spam Ave (blocklisted) | city=Sample City | state=TX | zip=75001 | phone=2025550143 |
| Experian Match | Client repository record matched: Alex Rivera, 123 Main St, Sample City TX 75001 2025550143 — matched on remaining usable data; input phone matched to Experian phone; the blocklisted address channel '100 Spam Ave' was suppressed from matching. |
What it means: An individual matched in the Experian repository, and at least one channel is blocklisted.
Confidence: High — Strong Experian identity match despite suppressed channel(s).
Threshold behavior: Not filtered; always returned when blocklisted.
Example
| Field | Example |
| Client Input Record | fname=Jane | lname=Doe | addr1=456 Oak Ave | city=Schaumburg | state=IL | zip=60173 | phone=8475550000 (blocklisted) |
| Experian Match | Experian repository record matched: Jane Doe, 456 Oak Ave, Schaumburg IL 60173 — matched via name + postal address; the blocklisted phone channel 8475550000 was suppressed from matching. |
What it means: No existing individual matched; new ID(s) were generated, and at least one channel is blocklisted.
Confidence: Moderate - New identity with caution — no prior match and a channel was suppressed.
Threshold behavior: Not filtered; always returned when blocklisted.
Example
| Field | Example |
| Client Input Record | fname=Casey | lname=Newrecord | addr1=321 Elm Blvd | city=Exampletown | state=OR | zip=97035 | phone=2025550198 (blocklisted) |
| Experian Match | No repository match: Casey Newrecord, 321 Elm Blvd, Exampletown OR 97035 was not found in the client or Experian repository — a new OmniView profile was generated; the blocklisted phone 2025550198 was excluded from matching. |
What it means: All input addresses are blocklisted as bad data; consistent hashed IDs are returned.
Confidence: None - For address-based identity — all addresses are unusable.
Threshold behavior: Not filtered; always returned when blocklisted.
Example
| Field | Example |
| Client Input Required | fname=Test | lname=User | addr1=123 Test St | city=Nowhere | state=XX | zip=00000 (all address channels flagged as bad data) |
| Experian Match | No usable address: every address channel on the record was blocklisted, so no individual or household identity was published — consistent hashed IDs were returned in place of address-based identifiers. |
The following return codes describe this family of OmniView identity resolution outcomes.
| Code | Meaning | Confidence | Summary |
| E0018 | No usable input | None | No usable identifying data |
| E0019 | Address only | None | At least one address channel present on input but name is blank / not provided |
| E0020 | Invalid name | None | At least one address channel present on input but name is too short (<3 bytes total) |
| E0021 | Invalid channels | None | Address channels are present on input but all failed quality metrics |
| E0022 | Malformed record | None | Input schema mismatch |
| E0023 | Processing error | None | Internal processing failure |
| E0024 | Timeout Failure | None | Record processing timeout failure (applicable to microbatch processing only) |
| E9999 | Inquiry only | None | No match was found and inquiry only mode prevented new profile generation |
What it means: No identifying channel and no nameless channel were supplied.
Confidence: None - Insufficient input to attempt matching.
Threshold behavior: Not filtered.
Example
| Field | Example |
| Client Input Record | (Empty or non-valid record — no name, postal address, email, or phone supplied) |
| Experian Match | Not attempted — no identifying or nameless channel is present; the record was rejected before repository lookup |
What it means: No name and no nameless identity channel were supplied.
Confidence: None — Name is missing and no alternate channel can support matching.
Example
| Field | Example |
| Client Input Record | addr1=123 Main St | city=Sample City | state=TX | zip=75001 | fname= | lname= (no name, no email or phone) |
| Experian Match | Not attempted — 123 Main St, Sample City TX 75001 is a usable address, but no name and no nameless channel (email or phone) is present to support identity matching |
What it means: A name is present, but the combined name fields contain fewer than three characters.
Confidence: None — Supplied name is too short for normal identity matching.
Threshold behavior: With ep_threshold=accuracy, rejected nameless results may also resolve to E9999.
Example
| Field | Example |
| Client Input Record | fname=J | lname=(blank) | addr1=123 Main St | city=Sample City | state=TX | zip=75001 (no email or phone supplied) |
| Experian Match | Not attempted — the combined name value 'J' is fewer than three characters, and no alternate channel is available, so 123 Main St, Sample City TX 75001 cannot be resolved to an individual |
What it means: Identifying channels were present, but every supplied channel failed validation.
Confidence: None — All supplied channels are invalid.
Threshold behavior: Not filtered.
Example
| Field | Example |
| Client Input Record | fname=Alex | lname=Rivera | email=invalid-email | phone=000 |
| Experian Match | Not attempted — the email and phone values supplied for Alex Rivera both failed format validation; no channel survived quality checks, so no repository lookup was performed |
What it means: For delimited files, the record has the wrong number of delimiters.
Confidence: None — File structure is invalid.
Threshold behavior: Not filtered.
Example
| Field | Example |
| Client Input Required | "Alex|Rivera|123 Main St|Sample City" (job expects 6 delimited fields; record has 4) |
| Experian Match | Not attempted — the delimiter count does not match the configured input layout, so the parser rejected the row before identity matching. Check the input file layout against the job configuration |
What it means: A processing thread failed because of an unexpected internal error; no IDs are returned.
Confidence: None - Unavailable system processing failure.
Threshold behavior: Not filtered.
Example
| Field | Example |
| Client Input Record | Any otherwise-valid input record — fname=Jordan | lname=Lee | addr1=456 Oak Ave | city=Example City | state=IL | zip=60007 |
| Experian Match | Not completed — an internal processing exception occurred after the record passed validation; no client, Experian, or generated IDs were returned. Retry, or contact support if this persists across multiple records |
What it means: The input record failed with a timeout exception. No IDs are returned. Applicable to microbatch processing only.
Confidence: None - Record processing timeout failure.
Threshold behavior: Not filtered.
Example
| Field | Example |
| Client Input Record | Any otherwise-valid input record — fname=Jordan | lname=Lee | addr1=456 Oak Ave | city=Example City | state=IL | zip=60007 |
| Experian Match | Not completed — The processing of the input record failed with timeout exception; no client, Experian, or generated ID's were returned. Retry, or contact support if this persists across multiple records |
What it means: In inquiry-only mode, the record did not match the repository; no household or individual ID was found.
Confidence: None - No match — repository lookup produced no qualifying identity.
Example
| Field | Example |
| Client Input Record | fname=Unknown | lname=Person | addr1=999 Nowhere Ln | zip=00000 (inquiry_only_mode=true on job) |
| Experian Match | No match — Unknown Person, 999 Nowhere Ln 00000 did not resolve to an individual or household in either repository, or inquiry-only mode prevented generation of a new OmniView profile; no IDs were returned |
The following return codes describe this family of OmniView identity resolution outcomes.
| Code | Meaning | Confidence | Summary |
| N0000 | No match | N/A | No qualifying match |
| NB001 | Unique both | High | Single both-repository match |
| NC001 | Unique client | High | Single client channel match |
| NE001 | Unique Experian | High | Single Experian channel match |
| NB002 | 2-5 both | Low | Ambiguous mixed repositories |
| NC002 | 2-5 client | Low | Ambiguous client channel |
| NE002 | 2-5 Experian | Low | Ambiguous Experian channel |
| N0006 | 6+ candidates | Low | Too many candidates |
What it means: Channel-only flow found no matching individuals.
Confidence: N/A
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | email=unknown_user@example.com | phone=2025550100 (no name, no postal address) |
| Experian Match | No match — neither 'unknown_user@example.com' nor phone 2025550100 resolved to an individual in the client or Experian repository; no individual IDs were returned |
What it means: One individual matched across both client and Experian repositories.
Confidence: High — One channel-only identity corroborated by both sources.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | email=person.two@example.com | phone=2025550102 (no name, no postal address) |
| Experian Match | Both repositories matched: Riley Alvarez, 615 Corroborated Ave, Sampletown CA 90001 — the same individual resolved from the email and phone channels in both the client and Experian repositories |
What it means: One individual matched in a client repository only.
Confidence: High - One nameless-channel match, client source.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | phone=2025550101 (no name, no postal address) |
| Experian Match | Client repository record matched: Morgan Patel, 240 Client Way, Sample City TX 75001 — one client individual resolved from phone 2025550101; no Experian identity found |
What it means: One individual matched in the Experian repository only.
Confidence: High - One nameless-channel match, Experian source.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | email=person.one@example.com (no name, no postal address) |
| Experian Match | Experian repository record matched: Dana Chen, 88 Channel St, Example City IL 60007 — one Experian individual resolved from email 'person.one@example.com'; no client repository identity found |
What it means: Two to five individuals matched across both repositories.
Confidence: Low - Ambiguous multi-match result despite cross-repository presence.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Required | email=shared@example.com (no name, no postal address) |
| Experian Match | 2–5 candidates across both repositories share email 'shared@example.com' — e.g. Taylor Morgan and Jamie Morgan, 789 Pine Rd, Sample City TX 75001. Identity is ambiguous; published only when ep_threshold=coverage |
What it means: Two to five individuals matched in a client repository only.
Confidence: Low - Ambiguous multi-match result.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | phone=8005550101 (no name, no postal address) |
| Experian Match | 2–5 client repository candidates share phone 8005550101 — e.g. Chris Household and Dana Household, 72 Shared Ln, Sample City TX 75001. Identity is ambiguous; published only when ep_threshold=coverage |
What it means: Two to five individuals matched in the Experian repository only.
Confidence: Low - Ambiguous multi-match result.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | phone=8005550100 (no name, no postal address) |
| Experian Match | 2–5 Experian candidates share phone 8005550100 — e.g. Pat Shared and Janet Shared, 500 Shared Ave, Chicago IL 60601. Identity is ambiguous; published only when ep_threshold=coverage |
What it means: Six or more matching individuals were found; no Individual IDs are returned.
Confidence: Low — highly ambiguous/overflow result.
Threshold behavior: Not filtered
Example
| Field | Example |
| Client Input Record | email=info@example.com (no name, no postal address) |
| Experian Match | 6+ candidates share the role-based mailbox 'info@example.com' — e.g. multiple individuals at 900 Market St, Chicago IL 60601. Overflow result; no individual IDs are returned |