ForeSee Developer Portal

Everything you need to set up and optimize your ForeSee product. Home of developer documentation, implementation guides, and question/answer forums.

Blueprint

Web SDK FAQ

What is the ForeSee® Web SDK?

The ForeSee® Web-based Software Development Kit is a collection of resources developed for our clients to implement a suite of measurement tools for desktop, mobile, and tablet websites. Web SDK can also be used on Feedback projects and Replay.

Will the ForeSee code slow down my website? What has been done to ensure good performance?

Our ForeSee code has been designed with performance, security, and reliability as top priorities. See this article for details.

I have older ForeSee code that seems to be working fine. Why should I upgrade?

  • Google Mobile Invitation policy change on January 10, 2017. Upgrading to the latest version ensures your compliance with the new policy.
  • The mobile invitation has recently been updated for a better user experience.
  • The ability to customize invitations has also been recently added.
  • iOS change for mobile in September 2016 prevents invitations in iOS 10.
  • Latest versions work correctly in newer browser releases.
  • Smaller, encrypted, compressed cookie is more secure.

Can I change the appearance of the invitation?

There are several options available for customizing the user interface of desktop and mobile invitations. There is also an extension point for creating your own invitation. Read more about this in the Customized Invitations section.

Can I prevent the invitation from showing on certain pages?

The following options are available for blocking the survey invitation from being presented:

  • URL pattern - Do not show the invitation if the URL contains '/checkout/'.
  • Variable - Do not show the invitation if the page contains a variable called 'internalIP' with a value of '10.9.8.7'.
  • Cookie - Do not show the invitation if there is a cookie called 'loggedIn' with a value of 'Yes'.
  • userAgent - Do not show the invitation when the userAgent contains 'selenium'.
  • Browser - Do not show the invitation on IE 10 browsers.
  • Referring URL - Do not show the invitation if the site visitor comes from 'google.com'.

How do I test the code to ensure it's working as expected?

See Testing Client Code section.

Do we have to use the child (tracker) window in the desktop survey experience?

Over the years, ForeSee has found that it is best to show the questionnaire only when a visitor is finished with your site and is ready to provide feedback from a holistic view point. The child (tracker) window waits for the main browser window/tab to be closed, or for the domain to change, to present the survey.

It is possible to present the survey immediately after accepting the invitation. However, this is typically reserved for questions regarding the end of an experience, such as a purchase.

My code is pretty old and I am upgrading to ForeSee® Cloud Deployment. What do I need to do?

Remove any and all references on your site to:

  • <script type="text/javascript" src="/foresee/foresee-alive.js"></script>
  • <script type="text/javascript" src="/foresee/foresee-trigger.js"></script>

Then, follow the instructions for implementing the ForeSee® Web SDK. Once the legacy code has been removed, the Foresee directory/directories can also be removed. ForeSee® Cloud Deployment replaces the existing implementation.

I'm currently using ForeSee® Cloud Deployment. Should I test upgraded code before deploying to my production environment?

Yes. While you should not need to make any revisions to your code snippet or the code itself, it is recommended to test the upgrade in a safe environment to ensure there is no negative impact on your site.

This is the purpose of the two client folders hosted by ForeSee; the Staging folder and the Production folder. Whenever there is an upgrade the code, ForeSee does some local testing to ensure that the code is configured correctly for your business needs. ForeSee then pushes the new code into your ForeSee® Cloud Deployment Staging folder. This prevents any possible interruptions to your live site while you are testing the upgrade with your site.

For testing instructions, see Testing Client Code.

Contact ForeSee when your testing is complete and you are ready to deploy the upgrade to your live site. ForeSee will then push the new code to your ForeSee® Cloud Deployment Production folder.


Note:
In some cases, such as when upgrading from an 18x code (or older) package to the current version, a call does need to be scheduled for a live deployment to your Production folder in order to ensure a smooth transition to the upgraded code. In this case, your ForeSee contact will schedule a live call and web meeting with a member of our Implementation Services team and a technical resource for your organization to deploy the code.

How can I change the sampling criteria for my client code?

At this time, any sampling criteria requests are handled through the ForeSee Implementation Team. Contact your analyst or send a request to support@foresee.com.

What are CPPs?

Customer Passed Parameters are data points that you have on your website that may be sent with the response data. This helps with the segmentation of the satisfaction data for deeper insight. See Customer Passed Parameters for more information.

Does ForeSee collect Personally Identifiable Information (PII)?

Personally identifiable information is never intentionally collected by ForeSee. However, ForeSee does have the capability of collecting parameters identified by our clients through a URL, JavaScript variable, or cookie that could provide segmentation information. See Customer Passed Parameters (CPPs) for more information.

How long before we can invite the same person again?

Typically, ForeSee configures the re-invite period to be 90 days. However, this is configurable and may be different for those who accept the invitation verses those who decline.

When testing, I see different behavior for the different browsers. Is this expected?

Yes. The four major browsers handle our child (tracker) window differently. This is expected behavior and we have provided more information in the Desktop Invitation section.

How does ForeSee know if a site visitor is on a mobile device since my site is responsive?

We use the Wireless Universal Resource File (WURFL), which is the code that identifies the wireless device to allow the system to be configured accordingly. The WURFL device detection service can determine if a visitor is on a mobile or desktop device.