You can use Secure Variable Storage (SVS) to store sensitive information that you need to use in User Journeys. For example; email addresses, passwords, API keys, usernames, etc can now be stored in an encrypted vault but are available to use in scripts. Their values will never be displayed in your account, scripts or results.
Every RapidSpike account has its own, dedicated variable vault signed using its own encryption key. The vault is hosted in AWS’s Secret Manager and encrypted using AWS’s Key Management Service.
|Activate SVS||Admins, users|
|Create Variables||Admins, users|
|Read Variable Keys||Admins, users and restricted users|
|Read Variable Values||Not supported|
|Updating Variables||Not supported|
- Login to your RapidSpike account
- Navigate to Settings > Global Settings > Secure Variable Storage
- Activate SVS (if this has not already been done)
- Click “Add Variable”
- Enter the key – this is what you will use in user journey scripts to reference the variable
- Enter the value – this is the sensitive piece of information you wish to store securely
- Add more variables now if you wish
- Click “Save”
In this example, we are adding two variables; an email address and a password. The keys are prefixed with “rsLoginTest_” so that I can differentiate between these credentials which are for a journey that logs into RapidSpike, and other credentials for other user journeys.
Updating is not allowed. This is because it would require reading variable values, which is not allowed.
Therefore, to update a variable you must first delete it and then recreate it with the new value. Note; deleting variables is only allowed for Admins.
As an admin user, you are able to delete variables. They will immediately be unavailable to the scripts that use them so you must first be happy that they are no longer referenced, or you are going to immediately recreate the key with a new value.
Using Variables in Scripts
You can reference your variables in synthetic user journey scripts when using actions that input text into input fields:
These actions include a helper to view your available variables when you are editing the actions (see screenshot below).
Variables are accessible from the
$SecureVariable namespace using dot notation. For example, if you have a variable with a key of
rsLoginTest_emailAddress then you can enter that into a login form on your website using a
SendKeys action with the
Value set to
Please note that screenshots or videos will show the variable values entered into a web form. Use these with caution.
If you require help setting this up or have any questions, please do not hesitate to get in touch via your account manager or our support desk.