ForeSee Data Integration is 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. Some examples of this type of data are; days since last visit, total visits, products viewed, and conversion variables.
Forward thinking organizations want to see how customer experience impacts sales and ultimately shapes their business. With ForeSee Data Integration, respondent-Level data can be loaded from various business systems into ForeSee tools that add context for decision making, as well as provide a comparative format for detail analysis. Deep, segmentation-level analysis can be performed to help guide strategies within specific customer segments, audience profiles, etc.
Passing ForeSee survey data into Adobe can help optimize your clickstream reporting.
- Ability to tie ForeSee Voice of Customer data back to visitors within your Adobe Analytics suite.
- Ability to use ForeSee’s Advanced Analytics Portal and CX Suite to segment survey data by the clickstream data passed from Adobe.
- Adds context for decision making and providing a comparative format for detailed analysis.
- Deep, segmentation-level analysis can be performed to help guide strategies within specific customer segments, audience profiles, etc.
ForeSee -> Adobe
Adobe -> ForeSee
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
Shopping cart metric
Shopping cart metric
Shopping cart metric
Shopping cart metric
Clicks to Page
The page sequence number in the current visit.
Connection type: Example "LAN" or "Modem".
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 customer's last purchase.
Days Since Last Visit
Grouping for days passed since last visit, e.g., "Group A: less than 1 day."
The page name the visit started on.
Name for file download.
GeoSegmentation Cities, GeoSegmentation State, etc.
User's geographic information
- ForeSee makes updates to the survey configuration code in order to send context variables to Adobe. These are the survey Measurement ID and Respondent ID.
- You add a new processing rule in Adobe_ to map the context variables created by ForeSee to the eVar(s) you intend to use for integration in Data Connector. ForeSee provides the survey_mid variable. See image b below.
- Please complete the Data Connector Wizard in Adobe to authorize the data trade using the Integration Mapping Workbook as a guide. See image c below.
Special Note for Native Mobile Apps
ForeSee supports integrations with Adobe Analytics running on native mobile apps. However, a few extra steps are required:
- ForeSee builds 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 to access your Adobe suite.
- Once both systems are receiving data, ForeSee schedules 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.
Separately from the Adobe integration with ForeSee® CX Measure, Adobe integration with ForeSee® Feedback surveys is another offering. The integration sends data from ForeSee® Feedback surveys into Adobe Analytics, allowing you to see your data in one place.
- One eVar is required for the Feedback-Adobe Analytics integration, which covers all of the Feedback surveys. This eVar is separate and additional to any eVars already used for a CX Measure integration.
- One List Variable is required for the Feedback-Adobe Analytics integration, which covers all of the Feedback surveys.
- Multiple data connectors can send data to the same Adobe Report Suite.
- All Respondent data (including the useful CPPs) is sent to Adobe Analytics.
- Collect the following information:
- Feedback Survey MID (Called "Account ID" in Adobe): Obtained from within CX Suite -> Survey editor -> Collection Methods -> Click the pencil icon next to Site Badge -> Copy the ID from within the code sample (e.g. ‘Hb2rIOBB2XzZ0C9uL2BZRl3VNaj9TMrz’).
- Adobe Analytics Report Suite ID (e.g. 'Berkshire-prod').
- You can create a new one (requires a new list variable) or reuse an existing one (must pick an existing list variable).
- Adobe Tracking Server URL (e.g., https://foresee.sc.omtrdc.net).
- API Token: Please use the following for the API token: 42901d7ee7cccfb8c4d3c6e3b2932c36.
Create or Edit an existing Report Suite in Adobe Analytics:
- Navigate in Adobe Analytics to Admin -> Report Suites.
- Select the relevant Report Suites, then go to Edit Settings -> Conversion -> List Variables.
- Add a Custom Conversion List Variable, e.g. "ForeSee® Feedback Response List" (no other details needed).
Create a new Data Connector in Adobe Analytics (you need one data connector for each Feedback survey):
- Navigate in Adobe Analytics to Admin -> Data Connectors -> Click Add New and find "ForeSee® Feedback" (not "ForeSee 2.0"). Note: each Feedback survey requires a unique Data Connector. Enter the following settings for the connector:
- Integration Settings:
- Specify the Survey MID as "Account ID" under Integration Settings.
- Specify the ForeSee API token as "API Token" under Integration Settings.
- Variable Settings:
- Specify the response list variable defined in the report suite.
- Specify an eVar to be used for the Feedback Respondent ID.
- Specify an event to be used for Feedback Submission count (e.g, "Page Views").
- Specify your tracking server.
Log into CX Suite and set the Report Suite ID on the Global Settings -> Integrate page. This is necessary to accurately capture the Adobe session and User IDs.
Once steps 1-4 are complete, please contact ForeSee Support to turn on the flow of data to Adobe Analytics. (ForeSee must activate the integration pipeline in order for the data to begin transferring).
Google -> ForeSee
Please complete the following:
- Provide your Tracking ID (e.g., UA-XXXXX-Y). (Note: This is sometimes referred to as a Google Analytics API Name or a Web Property ID).
- 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.
- Provide your account username/email address or set up an additional account for ForeSee. (This account needs both Read and Analyze permissions). ForeSee also needs the Service Account Key file (p12 file). Instructions on obtaining the file are located here.
- The p12 file is needed so that the integration can be configured to use your Google Analytics API for data transmission. (Due to Google Analytics API quota limitations, it is not possible for the integration to flow through ForeSee's API quota.) In most cases, clients have enough capacity for the ForeSee-Google Analytics integration.
- You should have an API quota of at least 50,000 API calls per day, while most integrations require less than 10,000 daily API calls. A conservative estimate of the amount of quota needed for the integration is determined by this formula: np(d + m), where n = number of respondents, p = number of GA profiles, d = number of dimensions (max is 7), and m = number of metrics (maximum is 10).
- 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 seven dimensions and 10 metrics.
- NOTE: One dimension must be reserved for the ForeSee Respondent ID.
- Smart Thank You Page (STYP):
- ForeSee integrates code and begins to send survey respondent details.
- You confirm receipt of ForeSee RespondentID and ForeSee pushs all updates to production.
- Customer Passed Parameters:
- Requires a visitor unique identifier passed to ForeSee with the survey response.
- Create a data extract file that includes the RespondentID and associated behavioral data points.
- Drop the data extract file to the ForeSee SFTP; data is processed and available the next day.
- ForeSee creates a data extract that includes the visitor-unique ID and sends to client via SFTP.
- The ForeSee Respondent ID is used as a common identifier for data integration. 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 sends the ForeSee Respondent ID to Adobe and it is 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 back-filled to that point.
- ForeSee survey configuration updates: An update to ForeSee’s survey configuration 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 creates 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 third 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
- Example: If survey_mid = “Survey1ID” then eVar1 = 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 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. Combined between Latents and Custom Questions.
- Types of analytical data that can be passed from Adobe to ForeSee:
- All Standard Adobe Omniture variables
- Up to five Customer specified Traffic Variables (sProps)
- Up to five Customer specified Conversion Events (eVars)
- Many integration data-points are 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 pre-processed file uses the first non-empty value. In Omniture pre-processor mapping files, this rule is normally used for the visitor ID.
- Last: The pre-processed file uses 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 two-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.
- 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.
Updated about a year ago