This document lists and describes pre-defined Contextual tags. Contextual relies on the Streethawk backend for tagging which is why there are Streehawk references in the tagging examples. Code snippets demonstrating tagging an install from the Contextual SDK's can be found in the tagging documentation of the development platform for your application. Please note that the tags highlighted in Bold parameters are recommended for making full use of the features provided by Contextual.
|1||sh_cuid||Use sh_cuid to tag an install with a unique identifier. The sh_cuid tag is used to link users in your backend to our backend, it allows tagging via api call and it can be used to identify the same user across multiple installs. More info||tagString("sh_cuid",md5(email@example.com));|
|2||sh_email||For tagging user's email address. sh_email tag is mandatory to filter experiments based on email||tagString("sh_email","support@Pointzi.com");|
|3||sh_first_name||For tagging user's first name so as to send personalised messages with user's first name||tagString("sh_first_name","Alex");|
|4||sh_last_name||For tagging user's first name so as to send personalised messages with user's last name||tagString("sh_last_name","Smith");|
|5||sh_gender||For tagging user's gender. sh_gender is mandatory to filter experiments based on gender.||tagString("sh_gender","female");|
|6||sh_date_of_birth||For tagging user's birth date. sh_date_of_birth is mandatory to target campaigns based on users birthdate. The string should be in YYYY-MM-DD format.||tagString("sh_date_of_birth","2015-06-23");|
|7||sh_country||The country tag is by default guessed from the ip address if the value is not set. The value can be set using the tagging api.|