CPPs/EPPs

Customer Passed Parameters (CPPs) and External Passed Parameters (EPPs) are primarily used by clients to segment data within the Portal for an increased level of granularity. Analysts can also use them to increase the relevance of their Satisfaction Insight Reviews (SIRs).

CPP - A Customer Passed Parameter is a data point created by, or currently available from, the client that is captured at the time of survey submission. CPPs can typically be captured with either a variable, cookie, or a URL string that is accessible while the ForeSee code is running. Click here for additional information and to view a list of Default CPPs.

EPP - An External Passed Parameter is a data point provided by an external file. Data fields are sent in a separate data file, are matched up by the client and then loaded to the portal or appended by IS.

Deployment Types That Can Capture CPPs

• Trigger Code
  • Hosted Code
  • Legacy Code
• SDK
• Static Link
  • Email link
  • Site Feedback link (either with or without code on the site)
  • Social Media Link
  • Physical link (vanity URL) on store signage/receipt
• IVR/IVA (for both Store and Contact Center measures)
• Panel Studies

Once a survey is presented, the CPPs no longer updates. So, if a user receives a survey in session or prematurely during onExit, we do not collect CPPs after they have left the survey.

Passing CPPs Through An Intercept Survey

CPPs can be sent with the survey. This passing happens at the time of survey submission.

We have the ability within our code to set any CPP with a default value. This allows us to set the default value for a given event on the site you wish to measure, until it is changed to another value which indicates an action has been taken.

The client can send as many CPPs as they would like to us, though the more CPPs they pass, the larger the session level cookie is, as this data is stored in the cookie until the survey is presented.

Passing CPPs With The URL API

The term "URL API" can be thought of as being synonymous with the term "Survey Link", or the link used in emails and Site Feedback.

If the URL survey link is being used for email or where NO code is running on the site, then only the following default CPPs can be collected at the time of survey submission.

• sid
• survey_time
• survey_submits

If the URL survey link is being used for Site Feedback where code is running on the site, then we can capture a larger list of CPPs than the three mentioned above. You can find this list of CPPs here.

Clients can pass additional CPPs beyond the default mentioned above when using the URL API by adding them to the URL string.

• There is a limit of 2056 characters for the total URL string.
• Multiple CPPs within the URL string must be delimited by an ampersand (&):
  http://survey.foreseeresults.com/survey/display?cid=8NNxB5BIVJdMBEBUBJ1Fpg==&sid=link&cpp[custid]=1234
• The API syntax follows a name/value assignment formula, which can be seen in the above URL string also
  &cpp[name]=value)

How To Pass EPPs

The client must send us a file with the Foresee respondent id or email id. This can be done in the following ways:

• In the case of integration, the client has this information from the thank you page "handshake".
• In other cases, the client may get a custom extract from the analyst, append the data needed in additional columns then send it back to us via the SFTP site.
• Another way to append data is to use a unique identifier that the client is capturing as a CPP to match the data to a respondent.

The client data is delivered to ForeSee through the use of SFTP.

The data file that is sent to ForeSee can be the following formats:

• .csv
• .tsv
• Delimited .txt
• .sql

The file that is sent to us must have column headers, the column order must not change, any additional columns added after the first load must be added as the last column, and we can only have one file per measurement.

Data that is sent to us appears in the Portal the following day.

How does the data/variables they are sending us get matched up to the correct respondent in the portal? Is this done through a specific variable?