Demographic Data Sent through the Container Tag

Note: The codes shown below should all go under the container tag.

 When the site has demographic information about the users (for example, information obtained at the time of the registration of a user), there is the possibility of sending that information to the DMP to enrich the information of the users within the platform. To achieve this, you must implement a JavaScript code with this format:

<script>
_rely.push({
'gender': parametro_genero,
'age' : parametro_edad
});
_rely.send();
</script>

First the information is stored in the _rely array, being able to do only one or successive calls to _rely.push, determining the different characteristics to report. Then, they must be sent with _rely.send (); All features should be stored in _rely. The following code is equivalent to the previous one:

<script>
_rely.push({'gender': parametro_genero});
_rely.push({'age' : parametro_edad});
_rely.send();
</script>

Below is a detailed list of attributes that can be sent:

To inform user gender:

Key: gender

Values: 'F' or 'M' (F reports female gender, M reports male gender).

To inform user age there are different alternatives:

Key: age

Values: (current age of the user. Ex: 35).

Key: born

Values: (year of birth of the user. Ex: 1987)

Key: date

Values: (date of birth in yyyymmdd format. Ex: 19890319).

With only one attribute (age, born or date) it is enough to send the age information, it is not necessary to send all the attributes simultaneously.

- User Contact Information

The DMP platform allows the storage of user contact data securely through hash storage. A hash on an attribute (e-mail, telephone, national identifier) ​​is an indecipherable value, which cannot be decrypted (the original value can never be obtained again). When the DMP platform receives contact information, that hashed attribute is always saved in the SHA256 and SHA512 formats (without private key).

In this way, suppose the following scenario:

The email info@retargetly.com is sent

The DMP platform will effectively store two values:

Value in SHA256: 0e06ca8fb7433001b38b189ad677e591f44a934e50c771112179df4c93f53ad5

Value in SHA512: c9302ce11aaf5a813296b7576fec7fb13256a2ee08b9d2fd194979a556f7a4dc8fee4010625d766761be6ab3e0575ae27117dfbbd49c3983b147c39f4efc0272e

To send user contact information then you can use the same JavaScript code from the beginning, but on the following variables:

(In the event that the value is sent already hashed, the same prior to the hashing need to have a specific format. In that case, it is specified as "Format" in the list below. If present, it is mandatory that send with the specified format, otherwise the DMP may lose% match rate by wanting to overflow user lists by contact data)

To send e-mail information:

Password: ml_raw

Value: (unformatted user email)

Password: ml_sh2

Value: (user email in SHA256 format)

Format: all lowercase

Password: ml_sh5

Value: (user email in SHA512 format)

Format: all lowercase

To send cell phone number information

Password: mb_raw

Value: (unformatted user cell)

Password: mb_sh2

Value: (user cell phone in SHA256 format)

Format: country code + area code without zeros + subscriber number. Only numbers, there are no special characters or spaces in the middle. Example: 541151190123

Password: mb_sh5

Value: (user cell phone in SHA512 format)

Format: country code + area code without zeros + subscriber number. Only numbers, there are no special characters or spaces in the middle. Example: 541151190123

To send national identifier information

Password: nid_raw

Value: (national identifier of the unformatted user)

Password: nid_sh2

Value: (national user identifier in SHA256 format)

Format: no space characters or spaces

Password: nid_sh5

Value: (national user identifier in SHA512 format)

Format: no space characters or spaces

Example:

<script>
_rely.push({'mb_raw': "541151190123"});
_rely.push({'ml_sha256': "0e06ca8fb7433001b38b189ad677e591f44a934e50c771112179df4c93f53ad5"});
_rely.push({'ml_sha512': "c9302ce11aaf5a813296b7576fec7fb13256a2ee08b9d2fd194979a556f7a4dc8fee4010625d766761be6ab3e0575ae27117dfbbd49c3983b147c39f4efc0272"});
_rely.send();
</script>