Before releasing new or updated survey settings to production, it is critical your team performs testing and QA to ensure proper behavior on your site.
Here are the main testing steps:
- Verify the ForeSee gateway tag has been included (instructions below)
- Activate the survey and test survey loading rules and data collection
- Verify Replay Capture
For the initial installation of the ForeSee Web SDK refer to the Cloud Deployment article.
As part of the installation, ForeSee provides you a staging code snippet that can be used for testing. This code snippet can live in your testing environment in order for you to thoroughly test any changes prior to promoting them to your production environment. The staging snippet, used in conjunction with the administration page below, gives you all you need to test your specific code configuration.
Either one of these URL's work for most clients. Clients new to ForeSee as of February 7, 2017 are using the "gateway.foresee.com" snippet below.
- //gateway.foresee.com/sites/[sitekey goes here]/staging/gateway.min.js
- //gateway.answerscloud.com/[sitekey goes here]/staging/gateway.min.js
Example of a Staging Snippet:
It is important to be sure that the entire tag is included without mutation, and that it is placed within the <HEAD> section of your pages. The tag can be deployed directly on the website, or through the use of tag management tools such as Tealium, DTM, etc.
To verify that a tag is included, you can use your browser's developer tools. Examples here use Chrome, although similar tools are available in other browsers.
- To view the developer tools, press F12 (opt + CMD + I for Mac)
- Navigate to the Sources tab (1)
- In the left hand pane (2), locate either:
- Expand that source (its name will vary depending on the version of your current ForeSee code)
Once you have located the ForeSee code source in your developer tools, you can use this information to verify that the correct tag has been placed for the environment.
Expand the gateway source, and view the contained folders.
You should see one of these two folders:
The CLIENT_ID value is a unique name assigned to your code package, and typically closely mirrors your company’s brand name. However, the folder that follows that client ID (/staging or /production) is critical; please be sure the correct folder is shown in each environment: use staging in pre-release environments, and use production on client/customer facing platforms.
When ForeSee makes future updates to your code, the updates are pushed to the staging snippet first for pre-release QA. Only after changes are approved by your teams are they then promoted to your production snippet. Therefore, it is critical that the staging snippet is not used in production environments.
The triggering code embedded on your site comes pre-configured for the business rules related to your production environment. This could potentially make testing difficult. Therefore, in order to receive the invitation/survey while testing, a Survey Configuration Testing page (Figure 1) is provided which allows the invitation to display at a frequency of choice for the testing session only.
A further explanation of the rules that can be configured in the testing tool is found in the Invitation Behavior article.
Note on the Testing Tool
To access the Survey Configuration page, simply add the hash
#fscommand=fstest to the end of any URL of your site, and then refresh the page. For example, if your site is located at
http://www.site.com, you would edit the address bar to read
http://www.site.com#fscommand=fstest, press enter, and then refresh the page. You should see something like what is depicted in the screenshot below.