ReversePBKeyLookup
ReversePBKeyLookup allows you to look up an address using a pbKeyTM unique identifier as input and returns all standard returns that are provided as part of address matching.
A pbKeyTM unique identifier (PBKey) is returned when a match is made to the Master Location Dataset (MLD). It is a 12-character (+1 null) field, which is a persistent identifier for an address. The PBKey serves as a lookup key with Pitney Bowes GeoEnrichment databases to add attribute data for an address. Depending on the GeoEnrichment database, the attribute data can include property ownership, real estate, census, consumer expenditure, demographic, geographic, fire and flood protection, telecommunication and wireless systems information and more.
Use Cases
This section presents two example use cases for ReversePBKeyLookup:
- the first one demonstrates improved efficiency in managing and maintaining consistent and accurate data for customer address lists;
- the second one shows how to use pbKey™ unique identifiers retrieved from GeoEnrichment data products to generate an address list of customers targeted for products and services based on specific attributes associated with their address.
- Address Master Data Management
- To ensure the latest address information and most accurate locations are being used, businesses may regularly geocode their customer address list. There is a cost in terms of computing power to this intensive process, as well as a small chance of changes to the address match. Some businesses monitor these changes since it's integral to their business. Additionally, many businesses have multiple address databases across different business functions, and have the need for consistent representation of a single address across multiple systems and databases. ReversePBKeyLookup removes the need to re-geocode the address by using the pbKey™ unique identifier rather than the address as input. The address together with latitude/longitude coordinates are returned. The ReversePBKeyLookup process is substantially faster and therefore less costly than using the address to retrieve this information. In addition, since a pbKey™ unique identifier is persistent, there is no chance of matching to a different address.
- Identifying Addresses from GeoEnrichment Data
- The GeoEnrichment data products are a variety of text-based data files that contain different attributes for each address in the Master Location Dataset. You can use the attributes in one or more of these GeoEnrichment datasets to identify customers for products or services based on those specific attributes. The lookup key for these products is the pbKey™ unique identifier rather than the address. This allows you to easily link customers across multiple datasets if you need to consider attributes included in more than one GeoEnrichment dataset. For example, using Ground View Family Demographics Fabric, in conjunction with Property Attribute Fabric, you would be able to generate a list of pbKey™ unique identifiers for records that represent young families, with 4 or more persons, in large houses, to target for specific products and services. Once records with the desired attributes have been identified, the pbKey™ unique identifiers from those records can be used to return the address and location information for those customers using ReversePBKeyLookup.
Licensing
ReversePBKeyLookup requires a special
license. There are two levels of licensing for ReversePBKeyLookup:
- Standard - This license allows ReversePBKeyLookup of all of the standard MLD addresses.
- Enhanced - This license allows ReversePBKeyLookup of a portion of MLD addresses that require an additional royalty due to address sourcing constraints.
Requirements
ReversePBKeyLookup includes these
requirements:
- You have licensed and installed the Master Location Dataset (MLD).
- You have licensed and installed the DVDMLDR dataset.
- The MLD and DVDMLDR datasets must be the same vintage.
ReversePBKeyLookup Search Results
When using ReversePBKeyLookup, the
search results can return zero to many MLD point address variations that match the
input PBKey. There will be no matches returned if the given PBKey is not found.
While many PBKeys map to a single point-level address, some PBKeys map to multiple
point address variations. Getting multiple point address variations from one PBKey
can occur in two circumstances:
- Alias matches. Some streets are known by their common name and one to
many aliases. In this case, MLD may contain all variations of street names.
An example of multiple alias match returns for an input PBKey (P00008BCG8WM)
is shown below:
AP02. Normal match (non-alias). 1206 W 600 S, FOUNTAINTOWN, IN 46130-9409AP02. Alias match. 1206 W 1200 N, FOUNTAINTOWN, IN 46130-9409AP02. Alias match. 1206 W COUNTY ROAD 1200 N, FOUNTAINTOWN, IN 46130-9409AP02. Alias match. 1206 W COUNTY ROAD 600 S, FOUNTAINTOWN, IN 46130-9409
- Multi-unit buildings with/without units. In some cases, there are
multi-unit addresses without individual unit address records. In this case,
you may see multiple address records returned for the same input PBKey, some
without unit designations and others with ranged unit designations. In the
case of multi-unit addresses that have individual suite/unit number
address designations, each will have their own distinct PBKey. The following
example shows address results for a PBKey that maps to a building with and
without units, which share the same PBKey/location (P00003PZZOIE):
AP02. Normal match (non-alias). 4750 WALNUT ST, BOULDER, CO 80301-2532AP02. Normal match (non-alias). 4750 WALNUT ST STE 100-103, BOULDER, CO 80301-2532AP02. Normal match (non-alias). 4750 WALNUT ST STE 205-205, BOULDER, CO 80301-2532AP02. Normal match (non-alias). 4750 WALNUT ST, BOULDER, CO 80301-2538
ReversePBKeyLookup Return Codes and Match Codes
The table below lists the Return Codes and Match Codes returned when using ReversePBKeyLookup.
| License | Input PBKey | Point Results | Match Code |
|---|---|---|---|
| Enhanced | Found | One Enhanced | V000 |
| Enhanced | Found | Multiple Standard and/or Enhanced | V001 |
| Enhanced | Not Found | None | E040 |
| Standard | Found | One Standard | V000 |
| Standard | Found | Multiple Standard | V001 |
| Standard | Found | One Standard, some Enhanced | V002 |
| Standard | Found | Multiple Standard, some Enhanced | V003 |
| Standard | Found | All Enhanced | E041 |
| Standard | Not Found | None | E040 |
| No license | Not applicable | Not applicable | E000 |