Unified Delivery with Norden

2 Minutes to read

Print
Share
Dark

Light

Article summary

Did you find this summary helpful?

Thank you for your feedback

Unified Delivery with Norden utilizes the same core schema as Unified Delivery with the addition of custom features, given the nature of the flexibility designed with the Norden Tag.

Feature	Description
HEM	Hashed email associated with the tag fire, sha256
FIRST_NAME	First name of the matched record
LAST_NAME	Last name of the matched record (family name, surname)
BUSINESS_EMAIL	Business email attributed to the record and visit
MOBILE_PHONE	Mobile number associated with the record, run against FCC portability data (to be used for matching purposes only)
LINKEDIN_URL	LinkedIn URL for the record
PERSONAL_CITY	Personal address city
PERSONAL_STATE	Personal address state
PERSONAL_ZIP	Personal address zip
PERSONAL_ZIP4	Plus 4 extension of PERSONAL_ZIP. Does not include PERSONAL_ZIP
PERSONAL_EMAIL	The most observed personal email and match for visit
GENDER	Gender of record (M/F/U)
AGE_RANGE	Age range of record
MARRIED	Determination if the record is married (Y/N)
INCOME_RANGE	Income range of record
NET_WORTH	Estimate of a households total financial assets minus liabilities. Assets include financial holdings such as deposit accounts, investments, and home value. Liabilities include loans, mortgages, and credit card debt.
HOMEOWNER	Probabilistic and deterministic data set to capture home ownership (Y/N/P)
JOB_TITLE	Job title
SENIORITY_LEVEL	Modeled Seniority based on Job Title (CXO, VP, Director, Manager, or Staff)
DEPARTMENT	Modeled Department based on Job Title.
PROFESSIONAL_ADDRESS	Business address
PROFESSIONAL_ADDRESS_2	Business address 2
PROFESSIONAL_CITY	Business address city
PROFESSIONAL_STATE	Business address state
PROFESSIONAL_ZIP	Business address zip
PROFESSIONAL_ZIP4	Plus 4 extension of PROFESISONAL_ZIP. Does not include PROFESSIONAL_ZIP
COMPANY_NAME	Company name associated with the current job title
COMPANY_DOMAIN	Company domain associated with the company name and business email
COMPANY_PHONE	Comma separated array of phone numbers associated with the company
COMPANY_SIC	Semicolon separated array of SIC codes associated with the company
COMPANY_NAICS
COMPANY_ADDRESS	Company address
COMPANY_CITY	Company address city
COMPANY_STATE	Company address state
COMPANY_ZIP	Company address zip
COMPANY_LINKEDIN_URL	Corporate LinkedIn URL
COMPANY_REVENUE	Revenue range of company
COMPANY_EMPLOYEE_COUNT	Range of employees based on observed employees
PRIMARY_INDUSTRY	Primary industry associated with the company, mapped to LinkedIn industries
BUSINESS_EMAIL_VALIDATION_STATUS	Valid is included if the email has been validated by email service provider or null if validation is unavailable
BUSINESS_EMAIL_LAST_SEEN	Unix timestamp of the last activity signal
PERSONAL_EMAIL_VALIDATION_STATUS	Valid is included if the email has been validated by email service provider or null if validation is unavailable
PERSONAL_EMAIL_LAST_SEEN	Unix timestamp of the last activity signal
LAST_UPDATED	Date the record was last updated
EVENT_DATE	Timestamp (Date/Time) of the tag fire to the millisecond in UTC
IP_ADDRESS	IP address associated with the tag fire
PARTNER_ID	PID provisioned by Agency from the tag (feature is an aggregate of all PIDs associated the the Agency)
AGENCY_ID	AID provisioned by The Prospect Desk for Agency
UNIX_TIMESTAMP	Unix version of EVENT_DATE
JSON_HEADERS	JSON Header from the tag fire
EXTERNAL_ID	Pass through of values provided through the tag implementation (this implementation is optional, though the schema is built to maintain consistency)
REF_URL	Reference URL of the tag fire; page of tag fire
REFERER_URL	URL visited prior to the tag fire (when available)
MATCH_TYPE	The designation of the type of match for the record. Business, personal, or email.
VARIABLES	Passthrough array of variables included in the tag fire. This includes any specific columns defined within the schema

Was this article helpful?

What's Next

Department