Consumer Address History

Overview

Verisk’s Consumer History product includes up to 10 sequential addresses for millions of adult U.S. consumers.

Data Information	Value
Refresh Cadence	`Monthly`
Historical Coverage	`30+ Years`
Geographic Coverage	`United States`

Schema

This schema repeats itself in the dataset starting with ADDRESS_SEC and ending with ADDRIDD

Name	Description
PID	Persistent ID
SUFFIX	Jr., Sr., I, II, II, etc
GENDER	Gender Code: M - Male F - Female U - Unknown
DECEASEDCD	Y - Individual is Deceased
IDATE	First Time we have seen an individual
ODATE	Last time we seen activity for that individual
ADDRESS_SEC	Address Sequence
ADDRESS	Full Address
HOUSE	House Number
PREDIR	Street PreDirectional: N, S, E, W, NE, etc
STREET	Street Name or PO Box name, or RR # Box name, or HC # Box name
STRTYPE	Physical Street Suffix: ST, AVE, PL, BLVD, PKWY, etc
POSTDIR	Street Post Direction: N, S, E, W, NE, etc
APTTYPE	Unit Designator
APTNBR	Unit Number
CITY	City Name
STATE	State Abbreviation
ZIP	Zip Code
Z4	Zip+4 Code
DPC	Delivery Point Code with Check Digit
DPV	Delivery Point Validation Code: Y - Address DPV confirmed for both primary and secondary numbers, etc.
CRTE	Carrier Route Code
FIPSCD	FIPS County Code
Z4TYPE	Zip+4 Type: F - Firm or company address, G - General delivery address, H - High-rise or business complex, etc.
EFFDATE	First time an individual seen at this address
ADDRID	Address ID

Key Concepts

Should the EFFDATE of an individual's last recorded address match the ODDATE?

ODATE represents the last time activity was seen for an individual. This can be any activity across all sources (captured by logging into an app or filling out a form, etc). This field is tied to the individual. It represents their activity—and, more specifically, their recency. EFFDATE on the other hand is a date that’s tied to a given address (first time an individual is seen at that address). There’s an EFFDATE for any/all addresses on file for a given individual: EFFDATE, EFFDATE2, etc.

An individual will show activity without moving homes and would likely have a more recent ODATE than EFFDATE. So no, the ODATE and the EFFDATE probably don’t match. Though, if someone moved very recently, the two dates could match in theory.

Extracting insights across datasets

This dataset can be joined to the Property Data dataset using the address ID (ADDRID) attribute to join property characteristics with consumer address changes.