Process-independent Variables
Many LoyJoy process modules automatically create process-independent variables, when customers interact with the chat. For example such process-independent variables can be the first name a customer has entered in the chat. Process-independent means, that the variable is available in the current process, and all other processes. This makes sense for variables regarding the customer, e.g. for the first name or postal address.
Process-independent Variables List
The following list covers most process-independent variables, which are created by process modules. Please note that:
- The variable names do not form a forever constant API, as they may be extended and changed with the further development and growing feature set of LoyJoy. So you can use these variables, however they belong to their corresponding process module and might change occasionally, if the process module is further developed.
- Additional variable names may and certainly will be created that are not included in this list, as many process modules such as the Variable process module and Questionnaire process module can create arbitrary variables as decided by the modeller.
| Variable name | Variable description |
|---|---|
| auth_email | The customer email address, verified in an authentication step. (Sign-In, Auth0, ReachFive, ProCampaign, Beiersdorf) |
| birthdate | The customer birthdate. (Birthdate) |
| consent_double_opt_in_sms | true if a SMS double opt-in has been given via TAN code. (SMS Opt-In) |
| consent_single_opt_in_newsletter | true if a newsletter single opt-in has been given. (Newsletter Opt-In) |
| consent_single_opt_in_profiling | true if a profiling single opt-in has been given. (Profiling Opt-In) |
| consent_single_opt_in_reminder | true if a reminder single opt-in has been given. (Reminder Opt-In) |
| consent_single_opt_in_sms | true if a SMS single opt-in has been given. (SMS Opt-In) |
| consent_single_opt_in_web_push | true if a Web push single opt-in has been given. (Web Push Opt-In) |
| country | The customer country. (Postal Address) |
| The customer email, not verified in an authentication step. (Email) | |
| firstname | The customer first name. (First Name, Postal Address) |
| house_number | The customer house number. (Postal Address) |
| gender | The customer gender. Values can be male, female or diverse. These values are not exhaustive as additional values might occur depending on the process configuration. (Gender) |
| language_iso_6391 | The customer ISO 6391 language code. |
| lastname | The customer last name. (Last Name, Postal Address) |
| locality | The customer locality, e.g. city. (Postal Address) |
| loyalty_balance | The customer loyalty balance, if the customer has received loyalty points. (Code, Coupon Code, Loyalty, Loyalty Referral, Redemptions, Rewards, Win) |
| participation_num | The number of participations a customer has made in all processes. (Participation) |
| phone | The customer phone numer. Can be any format, however should be according to E.164. (Phone) |
| region_iso_31662 | The customer region according to ISO 31662. |
| salutation | The customer salutation or honorific prefix, e.g. Mr. or Ms.. (Postal Address) |
| sign_up_ip_address | The customer sign-up IP address. (Sign-In) |
| sign_up_referrer | The customer sign-up referrer. (Sign-In) |
| sign_up_timestamp | The customer sign-up timestamp. (Sign-In) |
| sign_up_user_agent | The customer sign-up user agent, i.e. web browser. (Sign-In) |
| street | The customer street address, optionally including the house number. (Postal Address) |
| tags | An array of tags that has been assigned to the customer. (Tag) |
| zipcode | The customer zip code. (Postal Address) |