ForeSee Developer Portal

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

Analytics Integrations

What Is ForeSee Data Integration?

  • The ability to connect ForeSee satisfaction data with your clickstream behavioral data.
  • By importing clickstream variables into the ForeSee Portal, you can create a profile of key visitor segments based on specific behaviors and survey data. For example, low satisfaction visitors with a high shopping cart value.
  • Examples of what can be passed are days since last visit, total visits, products viewed, search engine terms and customer specific traffic or conversion variables as well survey response data including model scores and custom question responses.

Why Use It?

  • Forward thinking organizations need to see how their customers’ experiences are impacting sales and ultimately shaping their business.
  • ForeSee Integration - Respondent-Level data can be loaded from various business systems into ForeSee adding context for decision making and providing a comparative format for detail analysis.
  • Deep, segmentation-level analysis can be performed to help guide strategies within specific customer segments, audience profiles, etc.

Adobe - ForeSee Integration

  • Passing ForeSee survey data into Adobe can help optimize your clickstream reporting.

Benefits of Data Integration

  • Ability to tie ForeSee Voice of Customer data back to visitors within your Adobe analytics suite.
  • Ability to use ForeSee’s Portal to segment survey data by the clickstream data passed from Adobe.
  • Adds context for decision making and providing a comparative format for detail analysis.
  • Deep, segmentation-level analysis can be performed to help guide strategies within specific customer segments, audience profiles, etc.

Why Integrate: Use Cases

How It Works

What Data Should I Integrate?

ForSee -> Adobe
Adobe -> ForeSee
  • Pass the data points that will allow you to create meaningful segments within your clickstream data.
  • Focus on the core model and custom questions you currently monitor:
    • Satisfaction
    • Key Future Behaviors
    • Top Priority Elements
    • Primary Visit Reason
    • Task Accomplishment
    • Previous Purchase
    • Product Shopping For
  • Pass the data points that will allow you to create meaningful segments within ForeSee
  • Focus on transactional metrics
    • Did they download a piece of content
    • Did they watch a video
    • Did they sign up for an account
    • Did they add items to basket
    • Did they use the search box
    • Core population segmentations (Membership Level, etc.)

Adobe-ForeSee Integration

Step 1: Data Identification

  • Work together with ForeSee to decide what data will be exchanged between Adobe and ForeSee.

Variables eligible to be passed to ForeSee

Omniture Standard Variables
Description

Cart Additions

Orders metric

Cart Removals

Shopping cart metric

Cart Views

Shopping cart metric

Carts

Shopping cart metric

Checkouts

Shopping cart metric

Clicks to Page

The page sequence number in the current visit

Connection Type

Connection type: Example "LAN" or "Modern"

Customer Loyalty

Category of customer based on number of purchases, example "new" or "return"

Days Before First Purchase

Number of days that pass between the first time a customer visits and when they actually make a purchase

Days Since Last Purchase

Number of days that have passed since the customers last purchase

Days Since Last Visit

Grouping for days passed since last visit, example "Group A: less than 1 day"

Entry Page

The page name the visit started on

File Download

Name for file download

Step 2: Adobe Setup

a) ForeSee will make updates to the survey trigger code in order to send context variables to Adobe. These are the survey Measurement ID and Respondent ID.
b) Please add a new processing rule in Adobe_ to map the context variables created by ForeSee to the eVar(s) you will use for integration in Data Connector. ForeSee will provide the survey_mid variable.
You will need Adobe Certification in order to set up a processing rule.
c) Please complete the Data Connector Wizard in Adobe to authorize the data trade; you will use the Integration Mapping Workbook as a guide.

Step 3: Data Exchange

  • ForeSee will build the data exchange between the two systems.

    • Cannot begin work until the Adobe Data Connector is completed.
    • Process typically takes 2 – 3 weeks to fully build and test data exchange.
    • For testing and validation, please provide either:
      • A point of contact (with Adobe access)
      • -or- A login for ForeSee access your Adobe suite
  • Once both systems are receiving data we will schedule a meeting to review the data in each of the portals.

    • Validate data is sent in its most usable form.
    • Ensure both teams have an understanding of integrated data metrics.

Google - ForeSee Integration

How It Works

What Data Should I Integrate?

Google -> ForeSee
  • Pass the data points that will allow you to create meaningful segments within ForeSee
    • Focus on transactional metrics
      • Did they download a piece of content
      • Did they watch a video
      • Did they sign up for an account
      • Did they add items to basket
      • Did they use the search box
      • Core population segmentations (Membership Level, etc.)
      • Source / Campaign / Keyword
    • Send up to 7 dimensions
    • Send up to 10 metrics
    • Google dimensions and metrics information: https://developers.google.com/analytics/devguides/reporting/core/dimsmets

Google Set-Up

Please complete the following:
1.Provide your Tracking ID (e.g., UA-XXXXX-Y).

  1. Create and provide two custom Dimension IDs.
    • One to store the ForeSee Respondent ID, set the scope to session.
    • Another to store the ForeSee Modelinstance ID, this is optional.
      3.Provide your account username or set up an additional account for ForeSee.
  2. Identify and provide a list of the dimensions and metrics you would like to send into the ForeSee portal to be paired with the respondent-level data.
    • Limited to 7 dimensions and 10 metrics.
    • NOTE: One dimension must be reserved for the ForeSee Respondent ID

Other Analytics Integrations

How It Works

Set-Up Process

Integration Link

  1. Survey Thank You Page
    • Requires Javascript code from clickstream vendor to create the link.
    • ForeSee integrates code and begins to send survey respondent details.
    • You confirm receipt of ForeSee RespondentID and ForeSee will push all updates to production.
      2.Customer Passed Parameters
    • Requires a visitor unique identifier passed to ForeSee with the survey response.
    • Unique identifier can be provided via cookie or Javascript variable.

Data Exchange

  1. Create a data extract file that includes the RespondentID and associated behavioral data points.
  2. Drop the data extract file to the ForeSee SFTP; data is processed and available the next day.
  3. ForeSee creates a data extract that includes the visitor unique ID and sends to client via SFTP.

Additional notes for the Adobe integration

  • The ForeSee Respondent ID is used as a common identifier for data integrations. The process of making this key available in the clickstream data is called the “integration handshake”.
  • When a website survey is submitted the survey thank you page will send the ForeSee Respondent ID to Adobe and it will be associated with that visitor’s session ID.
  • This handshake is the priority first-step for data integration, because once IDs are successfully trading between both tools integration data can be backfilled to that point.
  • ForeSee Survey Trigger Code Updates: An update to ForeSee’s survey code allows the Adobe session ID to be captured as a customer passed parameter (CPP) during the user’s website visit. Important: Foresee can only send integrated data to the report suite used during the user’s website session.
    • Survey code identifies the Adobe report suite responsible for the site visit.
    • Captures the Visitor ID of the session.
  • Thank You Page Updates: ForeSee thank you pages are updated to create Context Variables for completing the integration. Context variables are temporary values ForeSee can submit to Adobe to contain our respondent IDs. By default the code will create two such values: foresee_rid and foresee_mid which store the respondent ID and measurement ID respectively. A processing rule takes these temporary values, and commits them to an eVar for storage and use with the integration
    • survey_rid stores the respondent ID that marks each unique submission of the survey
    • survey_mid stores the parent measurement ID of the integrated survey
    • survey_xid stores an additional 3rd party ID for integration (optional)
  • Unique eVar Per Integration (ForeSee Recommended):
    • A single eVar should be used to hold respondent IDs for each survey integration. This provides the most accessible format of the integrated data.
    • The survey_mid is used to conditionally map survey_rid values to a unique eVar for each survey.
      • Example: If survey_mid = “Survey1ID” then eVar1 = survey_rid
        Else If survey_mid = “Survey2ID” then eVar2 = survey_rid
  • (Not Recommended) Two eVars for all Integrations. If there are insufficient eVars available to map each integration to its own eVar, an alternative approach can be used to contain all integrations in only two eVars. Access to integration data is significantly more difficult when using this method.
    • survey_rid is stored in one eVar for all integrations
    • survey_mid is stored in a second evar for all integrations
  • Creation of processing rules requires access and certification before your first rules can be created.
  • Conditional rules apply only to Adobe Sessions that meet all criteria.
  • ForeSee measures available for integration: Desktop website and Tablet/Phone (in-session survey only).
  • Once an eVar has been established to hold the Foresee Respondent ID the integration handshake is “live”. Data can be historically appended as far back in time as that go-live date
  • Types of ForeSee data that can be passed to Adobe
    • Latent level Element, Satisfaction, and Future Behavior scores
    • Closed-Ended Custom question responses
    • Customer Passed Parameters
    • Up to 15 total data-points can be sent per measure.
      • To reach the full 15, a minimum of 5 data-points must be latent scores from the Foresee Model.
      • Custom questions are limited to 10 total.
  • Types of analytical data that can be passed from Adobe to ForeSee
    • All Standard Adobe Omniture variables
    • Up to (5) Customer specified Traffic Variables (sProps)
    • Up to (5) Customer specified Conversion Events (eVars)
  • Many integration data-points will be sent to ForeSee as multiple values for the session. In these cases a pre-processing rule must be applied to the data before it can be displayed in the Foresee Portal. Processing Rules for Adobe Data in Foresee Portal:
    • Append: All values are concatenated together. Duplicated values can appear in the final result.
    • Unique Append: All unique values are concatenated together. No duplicate values are in the final result.
    • First: The preprocessed file will use the first non-empty value. In Omniture preprocessor mapping files, this rule is normally used for the visitor ID.
    • Last: The preprocessed file will use the last non-empty value
    • Sum: This rule is for numeric values only. The sum of all the values is the final result.
  • ForeSee sends data once a day after the ForeSee portal is updated and scores calculated. Expect a 2 day lag for Adobe data to be available in the ForeSee portal.
    • Day 1: Surveys collected. Scores/Impacts calculated overnight.
    • Day 2: Scores/Impacts available. ForeSee-Adobe data exchange occurs.
    • Note: ForeSee servers reside in the Eastern time zone (GMT – 5) and a “day” ends at 11:59pm EST.
  • Adobe/ForeSee can only guarantee an 80% data match on integration data.

Appendix Additional Information

  • MeasurementID, respondentID, questionID, and answerID are all alphanumeric. This may cause some issues during the data transmission and append process for clients whose internal database is set up to expect numeric IDs only.

Analytics Integrations