Data Normalization

This topic describes how to perform data normalization for the Twitter connector.

The users should prepare their data as per the table given below to get a good match rate on Twitter. The following table lists the data format layout information for Twitter connector:


Field Name	Description
`Email Address`	The Email Address. Use all lowercase and remove leading and trailing spaces. Link twitter connector also check the data and normalize it as per specification given above. Example: `support@twitter.com`
`Twitter Username`	The Twitter Username. Use all lowercase, do not include @, and remove leading and trailing spaces. Link twitter connector also check the data and normalize it as per specification given above. Example: `jack`
`Twitter UserID`	The Twitter UserID. Use standard integers (0-9) only. Link twitter connector also check the data and normalize it as per specification given above, it will remove other characters except numbers from the data. Example: `143567`
`iOS Advertising ID (IDFA)`	The IDFA ID. Use all lower-case letters with dashes. Link twitter connector also check the data and convert it into lowercase. Example: `4b61639e-47cc-4056-a16a- c8217e029462`
`Google Advertising ID (AdID)`	The Ad ID. Original format on device is required, not capitalized with dashes. Link twitter connector also check the data and convert it into lowercase. Example: `2f5f5391-3e45-4d02- b645-4575a08f86e`
`Android ID`	The Android ID. Original format on device is required, not capitalized without dashes or spaces. Link twitter connector also check the data and convert it into lowercase, remove the hyphens and leading and trailing spaces if sent. Example: `af3802a465767e36`
`phone_number`	Phone number(s) for the user. Link connector does not do anything for data normalization EXCEPT HASHING, the user has to make sure that he is sending correct data.
`Partner User ID`	The User's ID in the partner's system. Link connector does not do anything for data normalization, the user has to make sure that he is sending correct data.

Note:

All the earlier mentioned fields except, except Partner UserID, must be hashed using SHA256.
Additionally, the final output hash must be in lower case. For example: 49e0be2aeccfb51a8dee4c945c8a70a9ac500cf6f5cb08112575f74db9b1470d and not 49E0BE2AECCFB51A8DEE4C945C8A70A9AC500CF6F5CB08112575F74DB9B1470D.