AO Consumer Match
Overview
Advanced Object (AO) Consumer Match matches individuals using name and address information, with additional parameters designed to match females individuals who may have changed their surname. AO Consumer Match can be used to match the individual (full name), the family (last name only) or by residence (no name components). The default scores represent best practices for matching.
AO Consumer Match generally accepts a single stream as input and produces a single output consisting of groups of duplicate records indicated by multiple group IDs and other optional information appended. To use the Consumer Match, you must have address fields (Address and either LastLine or City, State, and ZIP Code components). If you will use the macro with Master Data Management (MDM) you must also define a unique record ID on input. If you use the macro with MDM, you may optionally define an additional input containing "Never Match" ID pairs.
AO Consumer Match configuration parameters
AO Consumer Match has eight sets of configuration parameters in addition to the standard execution options: Input , Name , Input2 , Name2 , Address , Address , Segment , Options, and Table.
AO Consumer Match Input tab
Name
Parameter | Description |
---|---|
Name type | Select input name type, either Full name or Parsed name.
|
Name | If Contact type is Full name, the name field.
|
First name | If Contact type is Parsed name, given name (John A Smith Jr).
|
Middle name | If Contact type is Parsed name, middle name (John A Smith Jr).
|
Last name | If Contact type is Parsed name, surname (John A Smith Jr).
|
Suffix | If Contact type is Parsed name, generation name (John A Smith Jr).
|
Address
Parameter | Description |
---|---|
Address type | Specify whether input address is Full address or Component address.
|
Address1 | Required if Address type is Full address. First line of unparsed address.
|
Address2 | Optional if Address type is Full address. Second line of unparsed address.
|
Street number | Required if Address type is Component address. Street number (123 E Main Street NW Apt 101).
|
Street predir | Required if Address type is Component address. Street predirectional (123 E Main Street NW Apt 101).
|
Street name | Required if Address type is Component address. Street name (123 E Main Street NW Apt 101).
|
Street suffix | Required if Address type is Component address. Street suffix (123 E Main Street NW Apt 101).
|
Street postdir | Required if Address type is Component address. Street postdirectional (123 E Main Street NW Apt 101).
|
Suite/Apt #/Bldg | Required if Address type is Component address. Suite/apartment number (123 E Main Street NW Apt 101).
|
Address last line
Parameter | Description |
---|---|
City | (Required) City.
|
State | (Required) State.
|
ZIP | (Required) ZIP Code.
|
Other match fields
Parameter | Description |
---|---|
Gender | Gender. Must be Male, Female, or blank (unknown or indeterminate).
|
Phone | (Optional). Telephone number or alternate input field.
|
(Optional) Email address.
| |
Other field | (Optional) Alternate input field such as SSN may be specified.
|
Unique record ID
Parameter | Description |
---|---|
Record ID | (Optional) Field containing the unique record ID.
|
AO Consumer Match Name tab
Name options
Parameter | Description |
---|---|
Ethnic nickname match | If selected, matches less common, but valid nicknames (such as Sean/John). Unwanted nicknames can be removed by adding a "remove" entry to the Name alias table.
|
Match gender | If selected, records with two different genders (no matter how close) will never match (for example, Alexander versus Alexandra). If a full name is used instead of parsed names or a gender field is not used, Data Management will attempt to internally generate one for matching purposes.
|
Fix reversed first/last | Select this if you suspect that your records may have First name and Last name reversed.
|
Gender reversal | Defines how gender is handled in records where First Name and Last Name are reversed. Options are:
|
Fix reversed first/last all recs | Select this if you selected Fix reversed first/last and you also want to fix records with an internal dedupe flag set to N.
|
Match first/middle | Select to enable cross comparison of first name against middle name.
|
Match first/initial | Select to enable cross comparison of first name against initial.
|
Match middle/initial | Select to enable cross comparison of the middle name against initial.
|
Ignore middle | Select to ignore middle name in name comparisons.
|
Female-only matching
Match gender must be selected.
Parameter | Description |
---|---|
Match first/address | Select to compare female records using first name (ignoring last name) and address.
|
Match first/phone | Select to compare female records using first name (ignoring last name) and phone.
|
Match first/email | Select to compare female records using first name (ignoring last name) and email.
|
Match first/other | Select to compare female records using first name (ignoring last name) and additional field.
|
Match blank suite | Specifies method for matching blank Suite/Apt. # input field in female records. Options are:
|
Match scores
Parameter | Description |
---|---|
First name score | Match threshold for first name.
|
Middle name score | Match threshold for middle name.
|
Last name score | Match threshold for last name.
|
Address score | Match threshold for address fields, set globally for all address components.
|
Phone score | Match threshold for phone, if present.
|
Email score | Match threshold for email, if present.
|
Other score | Match threshold for other, if present.
|
AO Consumer Match Input2 tab
If alternate input fields are specified, these are compared to the primary versions specified on the Input tab.
Alternate address
If you specify an alternate address, it must have the same format as the primary address on the Input tab. If multiple addresses are used, the Address ID may not represent a single location.
Single field address
Field | Description |
---|---|
Full address | (Required) First line of unparsed address.
|
OR Multi-field address
Field | Description |
---|---|
Street number | (Required) Street number (123 E Main Street NW Apt 101).
|
Street predir | (Required) Street predirectional (123 E Main Street NW Apt 101).
|
Street name | (Required) Street name (123 E Main Street NW Apt 101).
|
Street suffix | (Required) Street suffix (123 E Main Street NW Apt 101).
|
Street postdir | (Required) Street postdirectional (123 E Main Street NW Apt 101).
|
Suite/Apt #/Bldg | (Required) Suite/apartment number (123 E Main Street NW Apt 101).
|
Address last line
Field | Description |
---|---|
City | (Required) City.
|
State | (Required) State.
|
ZIP | (Required) ZIP Code.
|
Alternate other match fields
Field | Description |
---|---|
Phone 2 | (Optional) Telephone number or alternate input field.
|
Email 2 | (Optional) Email address. Alternate input field can be specified.
|
Other field 2 | (Optional) Alternate input field such as SSN may be specified.
|
AO Consumer Match Name2 tab
Phone matching
Field | Description |
---|---|
Phone/first score | Match threshold for optional phone/first name field comparison.
|
Phone/last score | Match threshold for optional phone/last name field comparison.
|
Phone/middle score | Match threshold for optional phone/middle name field comparison.
|
Match first/phone | Select to enable cross comparison of first name against phone.
|
Match middle/phone | Select to enable cross comparison of the middle name against the phone number.
|
Email matching
Field | Description |
---|---|
Email/first score | Match threshold for optional email/first name field comparison.
|
Email/last score | Match threshold for optional email/last name field comparison.
|
Match first/email | Select to enable cross comparison of first name against phone.
|
Match middle/email | Select to enable cross comparison of middle name against phone.
|
Other matching
Field | Description |
---|---|
Other/first score | Match threshold for comparison of first name and an additional match field.
|
Other/middle score | Match threshold for comparison of middle name and an additional match field.
|
Other/last score | Match threshold for comparison of last name and an additional match field.
|
Match first/other | Select to enable cross comparison of first name against additional match field.
|
Match middle/other | Select to enable cross comparison of middle name against additional match field.
|
AO Consumer Match Address tab
Address options
Field | Description |
---|---|
Match street abbreviation | Set this to No for more exact matches. For example, 123 Brook matches 123 Brookstone with this option set to Yes.
|
Match street missing word | Set this to No for more exact matches. For example, 123 Brook matches 123 Brook Lawn with this option set to Yes.
|
Simple street numbers | If selected, 101A and 101 Main street are treated as identical.
|
Substring match on suite number | If selected, increases flexibility in matching of Apt/Suite # field by allowing substring matches such as 10 vs. 101.
|
Match blank/non-blank predir | Set this to No for more exact matches. For example, 123 Brook matches 123 N Brook with this option set to Yes.
|
Match blank/non-blank postdir | Set this to No for more exact matches. For example, 123 Brook W matches 123 Brook with this option set to Yes.
|
Match blank/non-blank suffix | Set this to No for more exact matches. For example, 123 Brook St matches 123 Brook with this option set to Yes.
|
Match blank suite | Specifies method for matching blank Apt/Suite # input field. Options are:
|
Resolve blank suite matching conflicts | If blank matching (Blank to One Blank Only) is selected, selecting this ensures that no cascade matches will occur (No Apt to Match Apt 18, Apt 19, Apt 32, and so on).
|
Match scores
Field | Description |
---|---|
Street number score | Optional match threshold for street number field.
|
Street name score | Optional match threshold for street name field.
|
Street predir score | Match threshold for Pre-directional field.
|
Street postdir Score | Match threshold for Post-directional field.
|
Street suffix score | Match threshold for Suffix field.
|
Suite/Apt #/Bldg score | Match threshold for Suite/Apartment field.
|
AO Consumer Match Segment tab
Address segmentation
Field | Description |
---|---|
Match only within segment | If selected, data will be compared solely within the segment as defined below.
|
Segment data by | Specifies method for defining sort and comparison minimums for address data. Options are:
|
Street name letters | The number of letters of the street name to be used in address data segmentation. Ignored when segment type is Custom.
|
Street number digits | The number of digits of the street number to be used in address data segmentation. Ignored when segment type is Custom.
|
Custom segment | Optional. If Segment data by is Custom, the field containing the segment key.
|
Segment Phone by | When a phone column/field is included, segmentation can be defined to include all 10 digits, 7 digits that exclude the area code or 7 digits excluding the area plus the state.
|
Segment Email by | When an email column/field is included, segmentation can be defined to include the entire contents of the column/field, the entire name element only or the entire domain element.
|
Other segmentation
Field | Description | ||||||
---|---|---|---|---|---|---|---|
Segment Other by | When an additional "Other" field is included, data will be compared solely within the segment as defined below.
| ||||||
Partial segment | If Partial segmentation is selected, specifies the number of bytes (1-N) to compare within the segment.
|
Segment size limits
Field | Description |
---|---|
Limit segment | Turns on segmentation limits for all active match criteria.
|
Max segment size | If Limit segment is selected, specifies maximum number of records compared in a single comparison group. The default setting allows for nearly-unlimited segment size. If you want to limit segment size to avoid runaway computation, potentially at the expense of missing a few record matches, set this to a lower value like 1000.
|
AO Consumer Match Options tab
MDM
The MDM options are only available if you have defined a unique Record ID on the Input tab.
Field | Description |
---|---|
"Never Match" override | If selected, use a second input to define "never match" pairs (pairs of record IDs that should never be matched). This input must contain two fields, ID1 and ID2.
This option operates at the record-comparison level, not the record-grouping level. So if you have three records with IDs {1,2,3} that all match each other, and inject "never match 1-3" using the never-match input, the records will still group due to the transitivity of matching 1-2 and 2-3. |
ID1, ID2 | If "Never Match" override is selected, the fields containing IDs for the "Never Match" pairs.
|
Reporting
Field | Description |
---|---|
Output component match IDs | If selected, outputs IDs showing the match groups for each match logic in addition to the consolidated result.
|
Output match score | If selected, outputs the overall score from the match records as a percentage between 1-100.
|
Output match info | If selected, outputs additional Match information. "Y" will generate Match Type, Group Counts/Order/Rank, Unique No., HOH Flag at the finest level. "All" will generate the same information at all levels as determined by the criteria selected (for example, Address, Phone, Email).
|
Source control
Field | Description |
---|---|
Source | Field containing the logical description for input data source. This is usually defined in AO Define Source.
|
Priority | Field containing Match Rank Priority value, typically assigned using AO Define Source. Determines a record's position in a match group.
|
Suppress flag | Field containing suppression definition for a source (value should be Y or N)
|
Internal dedupe flag | Field containing a Y/N flag indicating whether or not data from a particular source should be compared against itself (deduped) or solely against other sources. As a general rule, master databases are not internally deduped whereas update files are.
|
Compare sources not internally deduped | If a matching process has more than one source with the internal dedupe field set to "N", selecting this will compare the two sources.
|
Master record
Values in text fields sort in alphabetical order, even if the characters are numbers. Numbers are sorted by the first digit, then by the second digit, and so on, instead of by the numeric values. Thus "12" will appear before "7". Check data types or use leading zeros ("07") to ensure correct tie-breaking. Most text fields have a limit of 100MB.
Field | Description |
---|---|
Random priority | Uses random sorting as final tie-breaker. This option may generate different results for each run. If this is option is not selected, the final tie-breaker is the input record order.
|
Tie-breaker field 1 | The first field used to break priority ties.
|
Order 1 | If ASCENDING, then lower values of Tie-breaker 1 field will have higher priority.
|
Tie-breaker field 2 | The second field used to break priority ties.
|
Order 2 | If ASCENDING, then lower values of Tie-breaker 2 field will have higher priority.
|
Tie-breaker field 3 | The third field used to break priority ties.
|
Order 3 | If ASCENDING, then lower values of Tie-breaker 3 field will have higher priority.
|
Parallel processing
Field | Description |
---|---|
Parallelism level | Set to the lesser of the number of CPU cores on the Execution Server, or the number of threads configured in the project in which the macro is embedded.
|
Optimize for large segments | If you receive warnings like "Window Compare segment size for value (06828EAS3135) has exceeded 2000," enable this option. Comparing large candidate groups may reduce matching efficiency. Selecting this option increases the number of records that can be sent to a matching process without slowing processing.
|
AO Consumer Match Table tab
Field | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Name alias table | Path and name of optional DLD table used to augment or override the alias values defined within the macro. The table must be of the following form.
where
|
Configure AO Consumer Match
Select AO Consumer Match.
Go to the Input tab on the Properties pane.
Select the input. If you will be running the macro on Master Data Management (MDM), specify a unique Record ID.
To specify alternate input fields, you may optionally select the Input2 tab.
Select the Name tab to configure name matching options.
Optionally, select Input2 to configure alternate address fields and matching.
Select the Name2 to configure additional name matching options.
Select the Address tab to configure address matching options.
Select the Segment tab to edit segmentation options.
Select the Options tab to configure reporting, source control, master record, and other options.
Optionally, select the Table tab to specify a name reference table.
Optionally, go to the Execution tab, and then set Web service options.