Personator Consumer:Notice: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Personator|← Personator]]
[[Personator Consumer|← Personator Consumer]]
{{CustomTOC}}
{{CustomTOC}}


==Personator Version 4 Update==
==Major Personator Consumer Database Update==
'''Released: 8/14/2015'''
As we continue to improve our service, a newly updated and refined version of the Personator Reference Data will be released.


The new version of Personator (Version 4) can now be consumed using the following endpoint:
The new version will ultimately improve the API’s current ability to:
#Append more accurate demographics and contact information.
#Verify name-address-phone-email correlation to ensure full contact accuracy.
#Perform Moves and provide the latest address for individuals.
 
The Personator Consumer Database is compiled from several sources and industries such as Property Information Data, Loan Data, Credit Data, Telephone Data and several other private sources. The final combined database merges all contact records including Addresses, Phone Numbers, Emails, Names and demographics, amounting to over a billion records of historical and current information. This data is then exposed through the Personator Consumer Web Service which allows for checking, verifying, appending and updating contact records.
 
===Why are we Re-Compiling Personator’s Data?===
Over time, we have deemed some of our data sources to be outdated and inaccurate, thus needing to be purged. We have also acquired new data sources that offer better and more comprehensive consumer data. Hence, the recompilation of Personator’s Reference Data. In order to leverage the newer and better sources as well as removing old and outdated information, a major re-compile of the reference data has been implemented and is set for release.
 
For all inquiries, issues and questions please contact [[Tech Support|Melissa Tech Support]].
 
===Are there any Changes that Need to be Done on the Client Side?===
No. The Data update will be seamless. There is nothing that needs to be done on the client side.
 
===Will there be Any Service Interruption?===
No. There will be no service interruption for this update. As each of the server clusters are drain-stopped and updated, traffic will be re-directed to up and running clusters.
 
===What are the Changes that we will see with this Update?===
Due to the changes and improvements in the Personator Consumer Database, the appended contact information and demographics will change. The affected output fields include:
 
:{|class="alternate01" cellspacing="0"
!Output Field
|-
|NameFull
|-
|PhoneNumber
|-
|EmailAddress
|-
|MoveDate
|-
|HouseholdIncome
|-
|LengthOfResidence
|-
|OwnRent
|-
|Occupation
|-
|PresenceOfChildren
|-
|MaritalStatus
|-
|DateOfDeath
|-
|DateOfBirth
|-
|CreditCardUser
|-
|PresenceOfSenior
|-
|ChildrenAgeRange
|-
|Education
|-
|PoliticalParty
|-
|EthnicGroup
|-
|EthnicCode
|-
|DemographicsGender
|-
|HouseholdSize
|-
|DemographicsResults
|}
 
 
:;Some of the changes include<nowiki>:</nowiki>
<ol>
;<li>Differences in Appended Data</li>
Due to the changes in the data, which includes the removal of old sources and the addition of new ones, it follows that there will be differences in the information appended. Data may change, no longer exist, or append new information depending on the information now available to the service.
 
;<li>Increased/Decreased Append Rates</li>
As we add new sources of data to Personator and remove old ones, changes in append rates will also occur. Append rates will vary and will be heavily dependent on the nature of your data and the information being submitted. In our testing, we have seen an increase in append rates in most cases, however, there may be some cases where append rates may go down.
 
;<li>Differences in Verification</li>
Personator’s verification feature will also go through differences. VR** Codes in Personator are used to indicate whether the entered name is associated to the phone, address and email. As the sources of the data change for this update, so to will the contact information that the service will or will not be able to verify.
 
;<li>Differences in Moves</li>
As Personator makes use of proprietary algorithms and data to determine moves, this update will also affect changes in the individuals that we can and cannot provide a move for.
</ol>
 
 
==Personator 2018 Update==
''Released 03/07/2018''
 
The new version of Personator with structural changes to the WSDL that can now be consumed using the following endpoint:


:;rcpersonator.melissadata.net
:;rcpersonator.melissadata.net


Personator is a continuously growing product that requires the addition of new properties in order to satisfy the demand for new data. The Version 4 update includes the addition of new elements in the Request/Response Structure which in effect also changes the WSDL structure. Please follow proper update procedures to prevent sudden disruption of service.  
Personator continues to grow with demand for new IP Address information and input properties to help track a specific target. The 2018 update includes the addition of new elements in the Request/Response Structure which in effect also changes the WSDL structure. Please follow proper update procedures to prevent sudden disruption of service.
 


===TimeLine===
===Timeline===
The official Personator Endpoint (personator.melissadata.net) will be updated to Version 4 on September 30, 2015. The rcpersonator.melissadata.net endpoint will continue to be online until November 11, 2015, after which it will be taken offline.  
The official Personator Endpoint (personator.melissadata.net) will be updated to the new version on <insert update date>. The rcpersonator endpoint will continue to be online until '''06/01/2018''', after which it will be taken offline.


Here is the official timeline:
Here is the official timeline:


[[File:Personator_Timeline.png|link=]]
{|style="padding:5px;" cellspacing="0"
|-
|
|style="background-color:#0070c0; color:white; padding:5px; border-color:black; border-style:solid; border-width:0px 1px 0px 0px;"|'''03/07/2018'''
|style="background-color:#0070c0; color:white; padding:5px; border-color:black; border-style:solid; border-width:0px 1px 0px 0px;"|'''04/18/2018'''
|style="background-color:#0070c0; color:white; padding:5px;"|'''06/01/2018'''
|- style="border-right:10px solid red;"
|style="background-color:#0070c0; color:white; padding:5px; border-color:black; border-style:solid; border-width:0px 1px 0px 0px;"|'''Release Candidate Endpoint'''<br>(rcpersonator.melissadata.net)
|style="background-color:#c4d79b; padding:5px; border-color:black; border-style:solid; border-width:1px 1px 0px 0px;"|Release: Version 5.2
|style="background-color:#c4d79b; padding:5px; border-color:black; border-style:solid; border-width:1px 1px 0px 0px;"|Version 5.2
|style="background-color:#da9694; padding:5px; border-color:black; border-style:solid; border-width:1px 0px 0px 0px;"|Offline
|-
|style="background-color:#0070c0; color:white; padding:5px; border-color:black; border-style:solid; border-width:1px 1px 0px 0px;"|'''Official Endpoint'''<br>(personator.melissadata.net)
|style="background-color:#da9694; padding:5px; border-color:black; border-style:solid; border-width:1px 1px 0px 0px;"|Version 5.1.31
|style="background-color:#c4d79b; padding:5px; border-color:black; border-style:solid; border-width:1px 1px 0px 0px;"|Update: Version 5.2
|style="background-color:#c4d79b; padding:5px; border-color:black; border-style:solid; border-width:1px 0px 0px 0px;"|Version 5.2
|}




Line 22: Line 128:
Clients whose Web Service Integrations do not support WSDL changes due to the addition of new elements in the request/response structure are strongly advised to follow these update procedures:
Clients whose Web Service Integrations do not support WSDL changes due to the addition of new elements in the request/response structure are strongly advised to follow these update procedures:


#All applications must be re-compiled to use the Release Candidate Endpoint (rcpersonator.melissadata.net) before September 30, 2015.
#All applications must be re-compiled to use the Release Candidate Endpoint (rcpersonator.melissadata.net) before '''04/18/2018'''.
#Come September 30, we will be updating the Official Endpoint with Version 4 of Personator. At this time, all applications must be switched back to use the Official Endpoint before November 11, 2015 when the Release Candidate endpoint goes offline.
#Come '''04/18/2018''', we will be updating the Official Endpoint with Version 5.2 of Personator. At this time, all applications must be switched back to use the Official Endpoint before '''06/01/2018''' when the Release Candidate endpoint goes offline.
 
''Clients whose Web Service Integrations support structure/WSDL additions are still strongly encouraged to follow this update procedure, but are not required to.''
 
 
===Version 5 Changes===
====Input Structure====
:The following elements have been added as a request field:
 
:{|class="alternate01" cellspacing="0"
!Input Field
|-
|IPAddress
|-
|BirthDay
|-
|BirthMonth
|-
|BirthYear
|}
 
:;Please Note
::The BirthDay, BirthMonth and BirthYear Inputs are only place holders for the web service. They currently do not provide any functionality. A separate announcement will be sent for the activation of these new fields and features at a future time.
 
::The IP Address Input however, allows for retrieving IP Address Information. The new output fields for IP Address, are defined below.


Clients whose Web Service Integrations support structure/WSDL additions are still strongly encouraged to follow this update procedure, but are not required to.


===Version 4 Changes===
====Output Structure====
====New Census Output Elements====
:The following elements have been added as part of the response structure.


The following Elements have been added as part of the Response Structure:
:It is now possible to retrieve these fields when entering an input IP Address and requesting for the columns from the GrpIPAddress:


{|class="alternate01" cellspacing="0"
:{|class="alternate01" cellspacing="0"
!Element
!Column Name!!Column Group
|-
|DistanceAddressToIP||rowspan="17"|GrpIPAddress
|-
|IPAddress
|-
|IPCity
|-
|IPConnectionSpeed
|-
|IPConnectionType
|-
|IPContinent
|-
|-
|CensusKey
|IPCountryAbbreviation
|-
|-
|CountySubdivisionCode
|IPCountryName
|-
|-
|CountySubdivisionName
|IPDomainName
|-
|-
|ElementarySchoolDistrictCode
|IPISPName
|-
|-
|ElementarySchoolDistrictName
|IPLatitude
|-
|-
|SecondarySchoolDistrictCode
|IPLongitude
|-
|-
|SecondarySchoolDistrictName
|IPPostalCode
|-
|-
|UnifiedSchoolDistrictCode
|IPProxyDescription
|-
|-
|UnifiedSchoolDistrictName
|IPProxyType
|-
|-
|StateDistrictUpper
|IPRegion
|-
|-
|StateDistrictLower
|IPUTC
|}
|}


In order to retrieve these new elements in the Response, you may enumerate each field in the Columns Request:


:Eg. <Columns>StateDistrictUpper,StateDistrictLower</Columns>
:The new IP Address output fields and their definitions can be found here: [[Personator:Response#IPAddress|Personator Response IP Address]].
 
:There is also a new EstimatedHomeValue column. It currently does not output any data/values. A separate announcement will be sent for the activation of this new field and its features at a future time.
 
:{|class="alternate01" cellspacing="0"
!Column Name!!Column Group
|-
|EstimatedHomeValue||None
|}
 


Alternatively, you may also request for GrpCensus2 in the Columns Request to retrieve all of the new elements :
In order to retrieve these new elements in the Response, you may enumerate each field in the Columns Request or request for the GrpIPAddress column:
:Eg. <Columns>GrpCensus2</Columns>


====MelissaAddressKey Column====
<pre>
The MelissaAddressKey Column has been added as part of the response structure.
<Columns>EstimatedHomeValue,DistanceAddressToIP,IPAddress,IPCity,IPConnectionSpeed,IPConnectionType,IPContinent,IPCountryAbbreviation,IPCountryName,IPDomainName,IPISPName,IPLatitude,IPLongitude,IPPostalCode,IPProxyDescription,IPProxyType,IPREgion,IPUTC</Columns>
</pre>




[[Category:Personator]]
[[Category:Personator]]

Latest revision as of 21:37, 29 September 2021

← Personator Consumer


Major Personator Consumer Database Update

As we continue to improve our service, a newly updated and refined version of the Personator Reference Data will be released.

The new version will ultimately improve the API’s current ability to:

  1. Append more accurate demographics and contact information.
  2. Verify name-address-phone-email correlation to ensure full contact accuracy.
  3. Perform Moves and provide the latest address for individuals.

The Personator Consumer Database is compiled from several sources and industries such as Property Information Data, Loan Data, Credit Data, Telephone Data and several other private sources. The final combined database merges all contact records including Addresses, Phone Numbers, Emails, Names and demographics, amounting to over a billion records of historical and current information. This data is then exposed through the Personator Consumer Web Service which allows for checking, verifying, appending and updating contact records.

Why are we Re-Compiling Personator’s Data?

Over time, we have deemed some of our data sources to be outdated and inaccurate, thus needing to be purged. We have also acquired new data sources that offer better and more comprehensive consumer data. Hence, the recompilation of Personator’s Reference Data. In order to leverage the newer and better sources as well as removing old and outdated information, a major re-compile of the reference data has been implemented and is set for release.

For all inquiries, issues and questions please contact Melissa Tech Support.

Are there any Changes that Need to be Done on the Client Side?

No. The Data update will be seamless. There is nothing that needs to be done on the client side.

Will there be Any Service Interruption?

No. There will be no service interruption for this update. As each of the server clusters are drain-stopped and updated, traffic will be re-directed to up and running clusters.

What are the Changes that we will see with this Update?

Due to the changes and improvements in the Personator Consumer Database, the appended contact information and demographics will change. The affected output fields include:

Output Field
NameFull
PhoneNumber
EmailAddress
MoveDate
HouseholdIncome
LengthOfResidence
OwnRent
Occupation
PresenceOfChildren
MaritalStatus
DateOfDeath
DateOfBirth
CreditCardUser
PresenceOfSenior
ChildrenAgeRange
Education
PoliticalParty
EthnicGroup
EthnicCode
DemographicsGender
HouseholdSize
DemographicsResults


Some of the changes include:
  1. Differences in Appended Data
  2. Due to the changes in the data, which includes the removal of old sources and the addition of new ones, it follows that there will be differences in the information appended. Data may change, no longer exist, or append new information depending on the information now available to the service.
  3. Increased/Decreased Append Rates
  4. As we add new sources of data to Personator and remove old ones, changes in append rates will also occur. Append rates will vary and will be heavily dependent on the nature of your data and the information being submitted. In our testing, we have seen an increase in append rates in most cases, however, there may be some cases where append rates may go down.
  5. Differences in Verification
  6. Personator’s verification feature will also go through differences. VR** Codes in Personator are used to indicate whether the entered name is associated to the phone, address and email. As the sources of the data change for this update, so to will the contact information that the service will or will not be able to verify.
  7. Differences in Moves
  8. As Personator makes use of proprietary algorithms and data to determine moves, this update will also affect changes in the individuals that we can and cannot provide a move for.


Personator 2018 Update

Released 03/07/2018

The new version of Personator with structural changes to the WSDL that can now be consumed using the following endpoint:

rcpersonator.melissadata.net

Personator continues to grow with demand for new IP Address information and input properties to help track a specific target. The 2018 update includes the addition of new elements in the Request/Response Structure which in effect also changes the WSDL structure. Please follow proper update procedures to prevent sudden disruption of service.


Timeline

The official Personator Endpoint (personator.melissadata.net) will be updated to the new version on <insert update date>. The rcpersonator endpoint will continue to be online until 06/01/2018, after which it will be taken offline.

Here is the official timeline:

03/07/2018 04/18/2018 06/01/2018
Release Candidate Endpoint
(rcpersonator.melissadata.net)
Release: Version 5.2 Version 5.2 Offline
Official Endpoint
(personator.melissadata.net)
Version 5.1.31 Update: Version 5.2 Version 5.2


Update Procedures

Clients whose Web Service Integrations do not support WSDL changes due to the addition of new elements in the request/response structure are strongly advised to follow these update procedures:

  1. All applications must be re-compiled to use the Release Candidate Endpoint (rcpersonator.melissadata.net) before 04/18/2018.
  2. Come 04/18/2018, we will be updating the Official Endpoint with Version 5.2 of Personator. At this time, all applications must be switched back to use the Official Endpoint before 06/01/2018 when the Release Candidate endpoint goes offline.

Clients whose Web Service Integrations support structure/WSDL additions are still strongly encouraged to follow this update procedure, but are not required to.


Version 5 Changes

Input Structure

The following elements have been added as a request field:
Input Field
IPAddress
BirthDay
BirthMonth
BirthYear
Please Note
The BirthDay, BirthMonth and BirthYear Inputs are only place holders for the web service. They currently do not provide any functionality. A separate announcement will be sent for the activation of these new fields and features at a future time.
The IP Address Input however, allows for retrieving IP Address Information. The new output fields for IP Address, are defined below.


Output Structure

The following elements have been added as part of the response structure.
It is now possible to retrieve these fields when entering an input IP Address and requesting for the columns from the GrpIPAddress:
Column Name Column Group
DistanceAddressToIP GrpIPAddress
IPAddress
IPCity
IPConnectionSpeed
IPConnectionType
IPContinent
IPCountryAbbreviation
IPCountryName
IPDomainName
IPISPName
IPLatitude
IPLongitude
IPPostalCode
IPProxyDescription
IPProxyType
IPRegion
IPUTC


The new IP Address output fields and their definitions can be found here: Personator Response IP Address.
There is also a new EstimatedHomeValue column. It currently does not output any data/values. A separate announcement will be sent for the activation of this new field and its features at a future time.
Column Name Column Group
EstimatedHomeValue None


In order to retrieve these new elements in the Response, you may enumerate each field in the Columns Request or request for the GrpIPAddress column:

<Columns>EstimatedHomeValue,DistanceAddressToIP,IPAddress,IPCity,IPConnectionSpeed,IPConnectionType,IPContinent,IPCountryAbbreviation,IPCountryName,IPDomainName,IPISPName,IPLatitude,IPLongitude,IPPostalCode,IPProxyDescription,IPProxyType,IPREgion,IPUTC</Columns>