Client Code (Web SDK) - Implementing Client Code

ForeSee® Cloud Deployment

To implement ForeSee’s web-based measurement products, customers need only make a small change to their website template. This is a departure from the past model where customers needed to change their templates as well as host JavaScript and CSS files. Customers receiving code upgrades from older legacy code can take advantage of the new cloud-hosted model as well. If you are using a tag manager like the Google Tag Manager, this should be a quick change, not unlike the steps it takes to implement Google Analytics or Omniture.

Customers receive a small HTML snippet that must be added to their global website templates so that it appears on every page of your website. The purpose of this is to manage the asynchronous loading of any ForeSee products that you may be using. The snippet causes a small JavaScript file to be downloaded from the cloud. This file manages the injection of the ForeSee script, which is used to track usage of the site, and present survey invitations as needed.

In most cases, the ForeSee Implementation Team has worked with the client and possibly a Technical Contact to pre-configure the JavaScript library so that there are minimal changes required to implement this code.

Some of the pre-configured requirements are:

  • When and where to present an invitation.
  • Where to prevent an invitation from appearing.
  • How frequently to present the invitation.
  • The look and feel of the invitation.
  • This library may also contain logic to collect additional client specific data points that are available on the site to be passed along with the survey results through the use of Customer Passed Parameters (CPPs).

The basic implementation is simple:

  1. The client takes their custom HTML snippet and places it in their global website template.
  2. The client works with the ForeSee team to decide when users will be invited to participate in a survey.
  3. The ForeSee analyst implements the triggering rules and deploys the code to the cloud.

Multiple deployment models are supported to accommodate the specific needs of customers. Read on to learn more about these options.

Benefits of ForeSee® Cloud Deployment

The default option for deploying ForeSee products to your website is to use our hosted JavaScript. We host the assets for getting ForeSee products onto your website and you make a single, one-time change to your website template that you don’t need to touch from that point forward. The benefits of this approach include:

  • One-time code change. This greatly simplifies the process of implementing our code package on your site. Once you have our embed-snippet in your HTML template, you don’t need to make further changes when you want to tweak the way products trigger or behave on your site – we can take care of those steps for you.
  • No need to host ForeSee files. With this system you no longer need to host any ForeSee scripts, stylesheets, or images, making the process of implementing our code easier than before.
  • A reliable, enterprise-grade Content Delivery Network (CDN). We partner with an industry-leading CDN that provides low-latency, high-reliability, geographically distributed edge servers to ensure content is delivered to your website visitors quickly.
  • Asynchronous loading. Content is loaded onto your site in parallel with the rest of your content, meaning that ForeSee scripts have negligible impact on page-load times in the unlikely event the content server is slow or unreachable.

Articles in this section:

  1. Deployment Options
  2. The Embed Snippet
  3. ForeSee® On-Premises Deployment