Accuracy and Return Codes
Documentation on our return codes for Experian's Offline Identity Append and Enrichment products
This document is a reference guide for Universal Enrichment System return codes. Each return code is a 7-character value returned in Field ID 25038 that describes the outcome of an identity resolution request: what data was found, how confident the match is, and which address source was used for enrichment.
The Universal Enrichment System is the underlying platform that powers Experian's Offline Identity Append and Enrichment products. While these products may differ in their use cases and available outputs, they share a common return code framework and matching methodology.
Use this guide to assess match quality, configure thresholds, and interpret enrichment results.
Every Universal Enrichment System return code (Field ID 25038) is exactly 7 characters long:
| Component | Field ID (Return Code) | Bytes | Description |
| Base match code | 27195 | 1-5 | Identifies the type of identity outcome (e.g. FE001, AC100, TA100) |
| Match level | 27196 | 6 | Strength of the identity match: P = Person, H = Household, A = Address, G = Geographic, N = None |
| Address source | 27197 | 7 | Which address was used for enrichment: C = Client-supplied, E = Experian repository, N = None |
Byte 6 describes the possible level of identity resolution that the Universal Enrichment system could return based on your threshold settings.
| Code | Match Level | What it means |
| P | Person-level | A specific individual was identified. Highest-quality match used for deterministic identity resolution. |
| H | Household-level | A household was identified but not a single person. Common when name evidence is ambiguous or thresholds prevented person-level output. |
| A | Address-level | An address was matched but no individual identity or household record is published. Useful for address and geographic enrichment only. |
| G | Geographic-level | Only a geographic area was matched. No individual identity, household, or address record was published. |
| N | No match | No appendable outcome. Typically seen on no-match, blocklist, and overflow codes. |
Byte 7 indicates which address source the Universal Enrichment System retained for geographic enrichment — determined by Universal Enrichment's address resolution logic, not simply whether an address was present on the input.
| Code | Source | What it means |
| C | Client address | The address you supplied was used for enrichment. Typical when a valid client address is present and matches. |
| E | Experian repository address | Universal Enrichment System used an address from Experian's repository for enrichment. Common in Trade Area, MAID, IP, and Experian ID lookup flows. |
| N | No address | No usable address was retained for enrichment. No geographic or address-level data was appended. |
Universal Enrichment System return codes are grouped into families based on the type of outcome. The table below lists all Universal Enrichment System families in display order, from channel-based match outcomes to direct lookups, Address Capture, Trade Area, and digital signal flows. These return code families are found either as Byte 1 or Bytes 1 and 2.
| Family | Description | Typical outcome |
| V-series | Valid Experian identity matches | Name and address resolved to a specific individual in the Experian database |
| B-series | Blocklist-influenced outcomes | Match found but one or more channels suppressed by blocklist rules |
| N-series | Nameless / channel-only matches (postal address present) | Email or phone matched an Experian identity; no name on request |
| F-series | Email/phone-only match outcomes | Email or phone matched an identity; no name and no postal address on the request |
| FD-series | Email/phone fallback (name present on record; no postal address) | Name was on the record but processing used email/phone-only |
| ND-series | Email/phone fallback (name present on record; postal address present) | Name and postal address were on the record but processing used email/phone-only |
| L-series | A match that starts as a V-series or a B-series. It is changed to L-series because postal address is not present on input record | Name and email/phone matched an Experian identity; no postal address on the request |
| E-series | Validation and processing errors or Non-matches | Record could not be processed due to missing, invalid, or malformed input data Includes E9999 no-match outcome |
| CV-series | Direct Experian ID lookup (Person ID / Living Unit ID) | Identity resolved directly via a supplied Person ID (PID) or Living Unit ID (LUID); standard name/address matching bypassed |
| AC-series | Address Capture — name + ZIP (no street address) | Name and ZIP matched via Address Capture tiers; no street address on the request |
| AD-series | Address Capture — name + street address + ZIP | Name and ZIP matched via Address Capture tiers. Input record contained street address but not used |
| TA-series | Trade Area matching | Name matched within a configured ZIP radius; Experian-derived address used for enrichment |
| MA-series | MAID-driven identity outcomes (see MAID and IP Return Codes) | Identity resolved via Mobile Advertising ID (MAID) - see MAID and IP Return Codes |
| IP-series | IP-driven identity outcomes (see MAID and IP Return Codes) | Identity resolved via IP address - see MAID and IP Return Codes |
Each entry below states what the code means in plain terms, the confidence level to assign to records bearing it, and a worked example showing real input and match data.
Note: Bytes 6 and 7 can vary within a given base code depending on your job configuration and threshold settings. Confidence levels below reflect the typical published outcome.
V-series codes are returned when Universal Enrichment System resolves the input to a specific individual in the Experian database using name and address. This is the standard high-confidence match outcome.
What it means: The name and postal address or name and phone/email you provided resolved to a single existing individual in the Experian database. This is the standard person-level Experian match outcome.
Confidence: Highest — deterministic person-level Experian match
Example:
| Field | Example |
| Client Input Record | fname=Jane | lname=Doe | addr1=456 Oak Ave | city=Schaumburg | state=IL | zip=60173 | email=jane.alt@example.com | phone=8475550177 |
| Experian Match | Experian record matched: Jane Doe, 456 Oak Ave, Schaumburg IL 60173 — matched via name and postal address; person-level outcome; client address used for enrichment |
B-series codes indicate that at least one input channel (phone, email, or address) was suppressed by blocklist rules. The remaining non-suppressed data determines whether a match was still found.
What it means: One or more supplied channels were flagged and suppressed by blocklist rules. However, the remaining data still matched a single individual in Experian's database. Match is Experian-based.
Confidence: High — strong Experian identity match despite suppressed channel(s)
Example:
| Field | Example |
| Client Input Record | fname=Jane | lname=Doe | addr1=456 Oak Ave | city=Schaumburg | state=IL | zip=60173 | phone=8475550000 (flagged by blocklist) |
| Experian Match | Experian record matched: Jane Doe, 456 Oak Ave, Schaumburg IL 60173 — matched via name/address; blocklisted phone channel suppressed from matching. |
What it means: Every usable address value on this record was flagged as bad data or blocklisted. Without a valid address, Universal Enrichment System cannot produce a standard match outcome.
Confidence: None — all address data invalid or blocked; no match outcome
Example:
| Field | Example |
| Client Input Record | fname=Test | lname=User | addr1=123 Test St | city=Nowhere | state=XX | zip=00000 (all address fields flagged as bad data) |
| Experian Match | No match — all address channels bad or blocklisted; no identity or enrichment published |
N-series codes are returned when no usable name was present on the request. Matching was performed using email or phone channels only. A postal address was present on the request, distinguishing these from F-series codes.
What it means: No usable name was supplied, but the email or phone channel matches exactly one person in Experian's database. A postal address was present on the request but the address-level enrichment is derived from an Experian address.
Confidence: High — unique Experian match via email or phone; address-level enrichment returned
Example:
| Field | Example |
| Client Input Record | email=jane.doe@email.com | addr1=456 Oak Ave | city=Schaumburg | state=IL | zip=60173 (no name supplied) |
| Experian Match | Experian record was matched at person level using only email address 'jane.doe@email.com'. The supplied postal address was not used because client input had no name |
What it means: No usable name was supplied and the email or phone channel matches between 2 and 5 people in Experian's database. The channel is confirmed as present but the identity is ambiguous. The match level is determined by the selected ep_threshold parameter.
Confidence: Moderate — channel confirmed but ambiguous (2–5 Experian candidates)
Example:
| Field | Example |
| Client Input Record | phone=8005551234 | addr1=500 Shared Ave | city=Chicago | state=IL | zip=60601 (no name supplied) |
| Experian Match | 2–5 Experian candidates share this phone number (e.g. Pat Shared, Janet Shared — 500 Shared Ave, Chicago IL 60601); The match level is determined by the selected ep_threshold parameter |
E-series codes indicate:
What it means: The record contained no usable data at all: no name, no postal address, and no email or phone channel. Processing stopped immediately — there is nothing to match against.
Confidence: None — no actionable input data; record not processed
Example:
| Field | Example |
| Client Input Record | (Empty record — no name, address, email, or phone supplied) |
| Experian Match | Not attempted — insufficient data; record rejected before matching |
What it means: The record had a postal address but no name, no email and no phone. At least a name or an alternative channel is required alongside an address to attempt identity matching.
Confidence: Low - Address-level enrichment only
Example:
| Field | Example |
| Client Input Record | addr1=123 Main St | city=Dallas | state=TX | zip=75201 (no name, no email or phone) |
| Experian Match | Not attempted — a name or email/phone channel is required to attempt identity matching. Address-level enrichment is still viable |
What it means: The name on the record was too short for reliable matching (e.g. a single letter or blank) and no alternative email or phone channel was available.
Confidence: Low - Address-level enrichment only
Example:
| Field | Example |
| Client Input Record | fname=J | lname=(blank) | addr1=123 Main St | zip=75201 (no email or phone supplied) |
| Experian Match | Not attempted — name value is insufficient for identity matching. Address-level enrichment is still viable |
What it means: All available address channels in the record are invalid — for example, a malformed email address or a non-numeric phone number. They cannot be used for matching. If a valid Zip code is available address-level enrichment is still viable
Confidence: None — channel data present but invalid; record not processed
Example:
| Field | Example |
| Client Input Record | fname=John | lname=Smith | email=not-a-valid-email | phone=000 |
| Experian Match | Not attempted — supplied email and phone values failed format validation |
What it means: The record format or field count did not match the layout configured for this job. The record was skipped because it could not be reliably parsed.
Confidence: None — malformed record; does not match job input layout
Example:
| Field | Example |
| Client Input Record | "John|Smith|123 Main St|Dallas" (job expects 6 delimited fields; record has 4) |
| Experian Match | Not attempted — record format mismatch; check input file layout against job configuration |
What it means: An unexpected internal error prevented this record from completing the matching process. The record data may be perfectly valid — this is an operational issue, not a data quality issue.
Confidence: None — processing error (operational; not a data quality issue)
Example:
| Field | Example |
| Client Input Record | Any otherwise-valid input record fname=Jane | lname=Doe | addr1=456 Oak Ave | city=Schaumburg | state=IL | zip=60173 | email=jane.alt@example.com | phone=8475550177 |
| Experian Match | Not completed — internal processing error; contact support if this persists across multiple records |
What it means: No individual level match available, however household or address level enrichment is still viable if postal address is valid.
Confidence: Medium - Household or address level enrichment only
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 individual level match found. Household or address level enrichment is still viable |
F-series codes are returned when the request contained only email and/or phone — no name and no postal address. The Universal Enrichment System derives these by rewriting underlying results from the Identity Resolution System when both name and postal address are absent from the request.
What it means: The request had only an email or phone channel (no name, no postal address) and it matches exactly one person in Experian's database. Address-level enrichment is available through Experian derived address.
Confidence: High - unique Experian match via email/phone-only input
Example:
| Field | Example |
| Client Input Record | email=jane.doe@email.com (no name, no postal address) |
| Experian Match | Experian record matched: Jane Doe, 456 Oak Ave, Schaumburg IL 60173 — unique match via email; address-level enrichment returned through Experian derived address. |
What it means: The request had only an email or phone channel (no name, no postal address) and it matches between 2 and 5 people in Experian's database. The channel is confirmed but the identity is ambiguous.
Confidence: Moderate — channel confirmed but ambiguous (2–5 candidates)
Example:
| Field | Example |
| Client Input Record | email=team@brand.com (no name, no postal address) |
| Experian Match | 2–5 Experian candidates share this email (e.g. Team Brand accounts at 900 Market St, Chicago IL 60601) — The match level is determined by the selected ep_threshold parameter |
FD-series codes are returned when a name was on the record but it was routed through email/phone-only processing because a match could not be achieved using the name alongside the email and/or phone. These are Experian-derived outcomes unique to the Universal Enrichment System.
What it means: A name was present on the record but it was routed through email/phone-only processing because a match could not be achieved using the name alongside the email and/or phone. One Experian-derived candidate was found via the email or phone channel. Only address-level enrichment is returned — no individual Experian identity is published.
Confidence: Moderate — forced email/phone-only path; one candidate
Example:
| Field | Example |
| Client Input Record | fname=Derek | lname=Derived | email=derived@example.com (name present; no postal address; email/phone-only path applied) |
| Experian Match | Experian-derived candidate: Derek Derived, 22 Derived Dr, Atlanta GA 30301 — one candidate via email; The match level is determined by the selected ep_threshold parameter. |
What it means: A name was present but the record was routed through email/phone-only processing with no postal address. Between 2 and 5 Experian-derived candidates share the same channel.
Confidence: Low — forced email/phone-only path; ambiguous (2–5 derived candidates)
Example:
| Field | Example |
| Client Input Record | fname=Devon | lname=Derived | email=derived-shared@example.com (name present; no postal address; email/phone-only path applied) |
| Experian Match | 2–5 Experian-derived candidates share email channel |
ND-series codes are returned when a name was on the record and a postal address was also present, fell back to email and/or phone only processing because a match could not be achieved using the name and postal alongside the email and/or phone.
What it means: A name and postal address were on the record but the matching fell back to email and/or phone only processing because a match could not be achieved using the name and postal alongside the email and/or phone. One Experian-derived candidate was found via the email or phone channel.
Confidence: Moderate— nameless fallback; one candidate
Example:
| Field | Example |
| Client Input Record | fname=Rita | lname=Refresh | addr1=999 Mismatch Ave | zip=78664 | email=refresh@example.com (name and address present; nameless fallback path applied) |
| Experian Match | Experian-derived candidate: Rita Refresh, 12 Refresh Ln, Austin TX 73301 — one candidate via email; The match level is determined by the selected ep_threshold parameter. |
What it means: A name and postal address were on the record but the matching fell back to email and/or phone only processing because a match could not be achieved using the name and postal alongside the email and/or phone. Between 2 and 5 Experian-derived candidates share the same channel.
Confidence: Low — nameless fallback; ambiguous (2–5 derived candidates)
Example:
| Field | Example |
| Client Input Record | fname=Riley | lname=Refresh | addr1=777 Offset Rd | zip=78613 | email=refresh-shared@example.com (name and address present; nameless fallback path applied) |
| Experian Match | 2–5 Experian-derived candidates share email channel |
L-series codes are returned when a name was present on the request and an email or phone channel matched an Experian identity — but no postal address was supplied. Universal Enrichment System derives these by rewriting an underlying result when both name and channel evidence are present but no postal address is on the request.
What it means: A name and email or phone were supplied (no postal address) and they matched a single person in Experian's database. Experian found the individual from their channel data and an address is appended from the Experian repository.
Confidence: High — named individual match via email/phone channel; Experian address returned
Example:
| Field | Example |
| Client Input Record | fname=John | lname=Smith | email=john.smith@email.com (no postal address on record) |
| Experian Match | Experian record matched: John Smith, 1 Example Way, Sampletown ST 11111 — matched via name + email; Experian derived address used for enrichment |
CV-series codes are returned when a Person ID (PID) or Living Unit ID (LUID) was supplied on the request. Universal Enrichment System bypasses the standard Identity Resolution System and resolves the identity directly using the supplied Experian ID.
What it means: A valid Person ID (PID) or Living Unit ID (LUID) was supplied and Universal Enrichment System resolved the request directly using that Experian ID. This is a direct identity lookup — no probabilistic matching. CV000HE is returned when the result falls back to household-level.
Confidence: Highest — direct identity lookup via Person ID or Living Unit ID; no probabilistic matching involved
Example:
| Field | Example |
| Client Input Record | pid=123456 | luid=654321 (Experian IDs supplied directly; no name or address matching required) |
| Experian Match | Experian ID matched: Consumer View, 1 Identity Plaza, Schaumburg IL 60173 — direct identity lookup; Experian repository address used for enrichment |
AC-series codes are returned for Address Capture processing and the request contained a name and ZIP code but no street address. Tiers reflect how closely the name matched an Experian record at that ZIP.
What it means: Exact name matched to a single individual at the supplied ZIP. Strongest Address Capture tier.
Confidence: Highest — deterministic person-level match; exact name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Jennifer | lname=Williams | zip=90210 (no street address; Address Capture enabled) |
| Experian Match | Experian record matched: Jennifer Williams, 1 Example Way, Beverly Hills CA 90210 — exact name + ZIP; client address used for enrichment |
What it means: A near-exact name variation (e.g. missing accent, transposed letter, common abbreviation) matched a single individual at the supplied ZIP.
Confidence: Highest — person-level match; near-exact name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Jenifer | lname=Willams | zip=90210 (slight spelling variation; no street address) |
| Experian Match | Experian record matched: Jennifer Williams, 1 Example Way, Beverly Hills CA 90210 — near-exact name + ZIP; client address used |
What it means: The first part of a multi-word first name (e.g. 'Mary' from 'Mary Jane') matched a single individual at the supplied ZIP.
Confidence: High — person-level match; first-token multi-word name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | zip=90210 (compound first name; no street address) |
| Experian Match | Experian record matched: Mary Jane Williams, 1 Example Way, Beverly Hills CA 90210 — first name token matched; client address used |
What it means: An alternate part of a multi-word first name (e.g. 'Jane' from 'Mary Jane') matched a single individual at the supplied ZIP.
Confidence: High — person-level match; alternate name token and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | zip=90210 (compound first name; no street address) |
| Experian Match | Experian record matched: Mary Jane Williams, 1 Example Way, Beverly Hills CA 90210 — alternate name token matched; client address used |
What it means: The name was too ambiguous for a specific person (e.g. only a first initial) but matched a household at the supplied ZIP. Enrichment is at household level only.
Confidence: Moderate — household-level match; ambiguous name (first initial or similar)
Example:
| Field | Example |
| Client Input Record | fname=J | lname=Williams | zip=90210 (first initial only; no street address) |
| Experian Match | Experian household matched: James Williams, 1 Example Way, Beverly Hills CA 90210 — household-level enrichment; no individual Experian identity found |
What it means: The name on the record did not match any individual but a broader household match was possible at the supplied ZIP. Weakest Address Capture tier.
Confidence: Low — household-level match; weak name signal
Example:
| Field | Example |
| Client Input Record | fname=Completely | lname=Williams | zip=90210 (non-matching first name; no street address) |
| Experian Match | Experian household matched: Williams household, 1 Example Way, Beverly Hills CA 90210 — name did not match any individual; |
AD-series codes mirror the AC-series exactly — the same matching tiers, confidence levels, and logic apply — but are returned when a street address (addr1) was also supplied alongside the name and ZIP.
What it means: Exact name matched to a single individual at the supplied ZIP. Same strength as AC100 but a street address was present on the request.
Confidence: Highest — deterministic person-level match; exact name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Jennifer | lname=Williams | addr1=456 Oak Ave | zip=90210 (Address Capture enabled; street address present) |
| Experian Match | Experian record matched: Jennifer Williams, 15 Rudy Ave, Beverly Hills CA 90210 — exact name + ZIP match |
What it means: A near-exact name variation (e.g. missing accent, transposed letter, common abbreviation) matched a single individual at the supplied ZIP. Same strength as AC101 but a street address was present on the request.
Confidence: Highest — person-level match; near-exact name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Jenifer | lname=Willams | addr1=456 Oak Ave | zip=90210 (slight spelling variation; street address present) |
| Experian Match | Experian record matched: Jennifer Williams, 15 Rudy Ave, Beverly Hills CA 90210 — near-exact name +ZIP match |
What it means: The first part of a multi-word first name (e.g. 'Mary' from 'Mary Jane') matched a single individual at the supplied ZIP. Same strength as AC110 but a street address was present on the request.
Confidence: High — person-level match; first-token multi-word name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | addr1=456 Oak Ave | zip=90210 (compound name; street address present) |
| Experian Match | Experian record matched: Mary Jane Williams, 15 Rudy Ave, Beverly Hills CA 90210 — first name token matched + ZIP |
What it means: An alternate part of a multi-word first name (e.g. 'Jane' from 'Mary Jane') matched a single individual at the supplied ZIP. Same strength as AC111 but a street address was present on the request.
Confidence: High — person-level match; alternate name token and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | addr1=456 Oak Ave | zip=90210 (compound name; street address present) |
| Experian Match | Experian record matched: Mary Jane Williams, 15 Rudy Ave, Beverly Hills CA 90210 — alternate name token matched |
What it means: The name was too ambiguous for a specific person (e.g. only a first initial) but matched a household at the supplied ZIP. Same strength as AC120 but a street address was present on the request.
Confidence: Moderate — household-level match; ambiguous name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=J | lname=Williams | addr1=456 Oak Ave | zip=90210 (first initial; street address present) |
| Experian Match | Experian household matched: J Williams, 15 Rudy Ave, Beverly Hills CA 90210 — multiple household members; |
What it means: The name on the record did not match any individual but a broader household match was possible at the supplied ZIP. Weakest AD tier.
Confidence: Low — household-level match; weak name and ZIP
Example:
| Field | Example |
| Client Input Record | fname=Completely | lname=Williams | addr1=456 Oak Ave | zip=90210 (non-matching first name; street address present) |
| Experian Match | Experian household matched: Williams household, 15 Rudy Ave, Beverly Hills CA 90210 — weak name match |
TA-series codes are returned when Trade Area matching is enabled. The same name-matching tiers as Address Capture apply, but the match is found within a configured geographic radius (ZIP radius) rather than at the exact input ZIP. Byte 7 is typically E (Experian repository address) for Trade Area outcomes.
The presence of postal street address impacts the confidence of a return code.
What it means: Exact name matched to a specific individual within the configured ZIP radius. Strongest Trade Area tier.
Confidence: Highest — person-level Trade Area match; exact name within ZIP radius
Example:
| Field | Example |
| Client Input Record | fname=Jennifer | lname=Williams | zip=90210 (zip_radius=25; Trade Area enabled) |
| Experian Match | Experian record matched: Jennifer Williams, 1 Example Way, Beverly Hills CA 90210 — exact name within trade area |
What it means: Near-exact name variation matched to an individual within the configured ZIP radius.
Confidence: Highest — person-level Trade Area match; near-exact name within ZIP radius
Example:
| Field | Example |
| Client Input Record | fname=Jenifer | lname=Willams | zip=90210 (slight variation; zip_radius=25) |
| Experian Match | Experian record matched: Jennifer Williams, 1 Example Way, Beverly Hills CA 90210 — near-exact name within trade area |
What it means: First token of a multi-word first name matched within the configured ZIP radius.
Confidence: High — person-level Trade Area match; first-token multi-word name within ZIP radius
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | zip=90210 (compound name; zip_radius=25) |
| Experian Match | Experian record matched: Mary Jane Williams, 1 Example Way, Beverly Hills CA 90210 — first token matched within trade area |
What it means: Alternate token of a multi-word first name matched within the configured ZIP radius.
Confidence: High — person-level Trade Area match; alternate name token within ZIP radius
Example:
| Field | Example |
| Client Input Record | fname=Mary Jane | lname=Williams | zip=90210 (compound name; zip_radius=25) |
| Experian Match | Experian record matched: Mary Jane Williams, 1 Example Way, Beverly Hills CA 90210 — alternate name token matched within trade area |
What it means: A household match was found within the Trade Area but no specific individual could be confirmed. The household is within the configured ZIP radius.
Confidence: Moderate — household-level Trade Area match
Example:
| Field | Example |
| Client Input Record | fname=John | lname=Doe | zip=75201 (zip_radius=25; Trade Area enabled) |
| Experian Match | Experian household matched: Doe household within trade area of 75201 |
What it means: A broad household match was found within the Trade Area with weak name evidence. Weakest Trade Area tier.
Confidence: Low — household-level Trade Area match; weak name signal
Example:
| Field | Example |
| Client Input Record | fname=J | lname=Doe | zip=75201 (zip_radius=25; first initial only) |
| Experian Match | Experian household matched: Doe household within trade area — weak name signal; Experian derived address used |
MAID (Mobile Advertising ID) and IP-address return codes represent identity outcomes driven by digital signals rather than name/address matching. These flows are unique to Universal Enrichment.
| Code | Signal type | PII fields | Typical match level | Confidence |
| MA000 | MAID | Not requested (field_list omits PII) | Person (P) or Household (H) | Variable — High when MAID resolves uniquely to one individual; Moderate if MAID is shared or threshold not met |
| MA001 | MAID | Requested (field_list includes PII) | Person (P) or Household (H) | Variable — High when MAID resolves uniquely to one individual with PII output enabled; Moderate at threshold boundary |
| IP000 | IP address | Not requested (field_list omits PII) | Household (H) | Variable — High for dedicated residential IPs; Moderate to Low for shared, corporate, or mobile IPs |
| IP001 | IP address | Requested (field_list includes PII) | Household (H) | Variable — High for dedicated residential IPs; Moderate to Low for shared, corporate, or mobile IPs |
Universal Enrichment System supports four threshold approaches that control the trade-off between match confidence and match volume. The approach you configure determines which return codes are published — the same input record may produce different codes depending on the threshold set.
Precision: Highest level of accuracy for Address Capture and Trader Area matches only.
Accuracy: Prioritises precision. Returns primarily person-level (P) outcomes with the lowest false-positive rate. Fewer records are matched overall, but those that are matched carry the highest confidence. Recommended for compliance-sensitive or high-stakes use cases.
Balanced: Blends person-level and selective household-level outcomes. The most common default for general enrichment programmes where both coverage and confidence matter.
Coverage: Maximises match volume by allowing person, household, address, and geographic-level outcomes. Best suited to prospecting and audience-building where total reach is the primary goal. Higher coverage comes with increased ambiguity.
| Approach | Typical match levels | Typical codes |
| Precision | Address Capture only threshold | AC100, AC101 |
| Accuracy | Primarily P (person) | FE001P*, AC100P*, AD100P* |
| Balanced | P (person) + selective H (household) | FE001*, LE000*, AC110* |
| Coverage | P / H / A / G outcomes | FE002*, AC120*, TA120* |
Note: MAID and IP codes (MA/IP series) have their own threshold settings (maid_threshold, ip_threshold) independent of the main threshold. AC/AD/TA codes are governed by ac_threshold. Nameless return codes are governed by ep_threshold. The direct Experian ID lookup (CV-series) is not subject to threshold settings — it is a deterministic direct identity lookup.