Digital Identity Score

Introduction

Digital Identity score API, helps us in enriching our data fr analysis. This tool is designed to enhance our understanding of each user's digital footprint.

The Digital Identity Score uses basic information such as names, phone numbers, email-addresses, and pin codes to provide insights. These insights include phone and email attributes, which are useful for more targeted marketing and improved risk assessment.

Use Cases

Enhanced Customer Profiling: Utilize the API to gather detailed information about customers, allowing for the creation of more comprehensive customer profiles. This can aid in understanding customer preferences and behaviors.
Targeted Marketing Campaigns: Leverage user data to design and implement marketing campaigns that are more accurately targeted to specific demographics, interests, or behaviors.
Risk Assessment and Fraud Prevention: Use the API to assess the risk associated with customers by analyzing their digital footprint, which can be crucial in identifying and preventing fraudulent activities.
Personalized User Experience: Customize the user experience on platforms or services based on the individual's digital identity score, enhancing customer satisfaction and engagement.s with additional data points, thereby aiding in more informed lending decisions.
Customer Segmentation: Segment customers more effectively based on the enriched data, allowing for more focused and effective business strategies.

Curl

curl --location 'https://api-preproduction.signzy.app/api/v3/data-enrichment/digital-identity-score' \
--header 'Authorization: <auth-token>' \
--header 'Content-Type: application/json' \
--data '{
    "phone": "<phone-number>",
    "email": "<email-address>",
    "name": "<name>",
    "pincode": "<pincode>"
}'

Input Parameters

Input parameters	Description	Required Field	Data Type
phone	Phone number of individual	Required	string
email	Email address of individual	no	string
name	Name of an individual	no	string
pincode	Pincode where the we want to search the person	no	string

Note :

Output Response

{
    "digitalIdentityScore": 376,
    "digitalFootprint": "Medium",
    "ecomFootprint": true,
    "socialFootprint": true,
    "travelFootprint": false,
    "qcomFootprint": true,
    "businessNameFound": null,
    "twitterMatch": "adamjackson",
    "linkedinMatch": "jennifermclean",
    "ageBand": "18-24",
    "gender": "Male",
    "firstNameMatch": true,
    "lastNameMatch": true,
    "nameMatchScore": 75,
    "phoneFirstSeenYear": 2010,
    "emailFirstSeenYear": "1988",
    "phoneEmailMatch": true,
    "phoneEmailFirstSeenYear": "2004",
    "phoneEmailLastSeenYear": "1979",
    "phoneNameFirstSeenYear": 2010,
    "phoneNameLastSeenYear": 2022,
    "emailNameLastSeenYear": "2006",
    "phonePincodeFirstSeenDays": 2,
    "phonePincodeLastSeenDays": 0,
    "phonePincodeMatchCount": 8,
    "phoneUniquePincodesCount": 4,
    "emailPincodeFirstSeenDays": 2,
    "emailPincodeLastSeenDays": 7,
    "emailPincodeMatchCount": 9,
    "emailUniquePincodesCount": 9
}

Output Parameters

Field Name	Data Type	Description
digitalIdentityScore	String	A numerical score representing the digital identity of the individual.
digitalFootprint	String	A qualitative measure of the individual's overall digital presence.
ecomFootprint	Boolean	Indicates whether the individual has a footprint in e-commerce platforms.
socialFootprint	Boolean	Indicates the presence of the individual on social media platforms.
travelFootprint	Boolean	Reflects whether the individual has a significant travel history or presence.
qcomFootprint	Boolean	A specific footprint related to 'qcom' (possibly a proprietary or specific metric).
businessNameFound	String	The name of any business associated with the individual, if found.
twitterMatch	String	The individual's Twitter username, if a match is found.
linkedinMatch	String	The individual's LinkedIn username, if a match is found.
ageBand	String	The age range the individual falls into.
gender	String	The gender of the individual.
firstNameMatch	Boolean	Indicates if the first name provided matches records.
lastNameMatch	Boolean	Indicates if the last name provided matches records.
nameMatchScore	Integer	A numerical score indicating the accuracy of the name match.
phoneFirstSeenYear	Integer	The first year the individual's phone number was seen in the dataset.
emailFirstSeenYear	String	The year the individual's email was first seen in the dataset.
phoneEmailMatch	Boolean	Indicates if the phone number and email provided correspond to the same individual.
phoneEmailFirstSeenYear	String	The year both the individual's phone number and email were first seen together in the dataset.
phoneEmailLastSeenYear	String	The last year both the individual's phone number and email were seen together in the dataset.
phoneNameFirstSeenYear	Integer	The first year the combination of the individual's phone number and name was seen in the dataset.
phoneNameLastSeenYear	Integer	The last year the combination of the individual's phone number and name was seen in the dataset.
emailNameLastSeenYear	String	The last year the combination of the individual's email and name was seen in the dataset.
phonePincodeFirstSeenDays	Integer	The number of days since the individual's phone number was first seen with a specific pincode.
phonePincodeLastSeenDays	Integer	The number of days since the individual's phone number was last seen with a specific pincode.
phonePincodeMatchCount	Integer	The count of how many times the individual's phone number matched a specific pincode.
phoneUniquePincodesCount	Integer	The count of unique pincodes associated with the individual's phone number.
emailPincodeFirstSeenDays	Integer	The number of days since the individual's email was first seen with a specific pincode.
emailPincodeLastSeenDays	Integer	The number of days since the individual's email was last seen with a specific pincode.
emailPincodeMatchCount	Integer	The count of how many times the individual's email matched a specific pincode.
emailUniquePincodesCount	Integer	The count of unique pincodes associated with the individual's email.

Error reponse

Response	Message
200	success
400	All fields are empty
401	Authentication credentials were not provided
404	Not Found
406	service request is not acceptable.
500	Internal Server Error

Getting help

Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.

You can reach out to us at [email protected].