Skip to main content

Decipher Support

All the topics, resources needed for Decipher.

FocusVision Knowledge Base

Imperium Real Answer Integration

Overview

Imperium's Real AnswerTM is a third-party service used to validate open-end text responses while a respondent is taking a survey. Real AnswerTM  will help you make sure that users are inputting valid responses by providing you with a Real Answer ScoreTM (“RAS”) for each open-ended response as it is submitted by a respondent.

The RAS allows you to score how valid a respondent’s responses are (i.e. does it contain gibberish, profanity, copied text from another source, etc.) while they are taking your survey, instead of having to look at the data after the respondent has finished the survey.

A response’s RAS is determined by an analysis of the following factors:

  • “Bad” language – Words and phrases not likely found in a newspaper.
  • Garbage words – Words not found in the lexicon for the specified language.
  • Robot-submitted responses – Text filled in programmatically.
  • Pasted-in responses – Text filled in from a computer clipboard.
  • Similarity – Text very similar to previously submitted content.
  • Engagement – Length of response in comparison to other responses to the same question.

Note: This functionality is achieved without the knowledge of the respondent and therefore no consent is required. There are no client-side application downloads of any kind and no personally identifiable information is gathered.

You can use the Logic Library to add Real Answer to your survey. This can be done using either the "Imperium Real Answer Integration" element in the Survey Editor or the "realanswer" logic node in the survey XML.

Using the Survey Editor  

To add Real Answer validation using the Survey Editor, click "+ Add Survey Element" under the staging area:

dec_LLaddelement001.png

In the Element Library, click "Custom" and select the "Imperium Real Answer Integration" element from the list. Then click "Insert":

dec_LLintegrateira_000.png

The new element will appear in the staging area, where you can specify the settings for your integration:

dec_LLintegratera_002.png

The following options are configurable:

  • Client ID: Your client ID, as provided by Imperium.
  • Username: Your Imperium username.
  • Password: The password associated with your Imperium client ID. To encrypt your password, click "Encrypt Field".
  • SurveyID: The ID for the survey you would like to use.
  • Target: The label for the open-end that is to be validated.
  • Billing Code: A billing code with your RealAnswer data for reporting purposes (optional).
  • Engaged Word Count: The minimum word count to consider the respondent engaged. Responses shorter than the minimum will trigger the NonEngaged flag (optional and disabled by default). Click into the text-box to enter a number or hover over it to display and use the single-digit increase arrows.
  • Suppress Similarity: Set to "1" to disable similarity checking against previous answers in the same SurveyID/QuestionID.
  • Language Code: The two-letter language code matching the respondent's language (e.g., EN, PT, or DE).
  • Custom Factor 1: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.
  • Custom Factor 2: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.
  • Custom Factor 3: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.
  • Custom Factor 4: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.
  • Custom Factor 5: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.
  • Custom Factor 6: Set to "1" to perform a check for a custom factor to see if the string matches any of the previously defined phrases for this factor.

Using the XML

To include Real Answer functionality in a survey using the real answer logic node, add the following <logic> tag to your survey XML. This tag should be added after the question you are validating and appear on the same page as that question:

<logic label="realanswer1"
realanswer:ClientID="00000ABC-00AB-00AB-00AB-000000ABCDEF"
realanswer:Password="abcd1234"
realanswer:SurveyID="TestSurvey1"
realanswer:Target="q1.r3"
realanswer:Username="userid"
uses="realanswer.1"/>

The original Real Answer logic node is not compatible with trackVars="checkbox". To include Real Answer in a survey with trackVars="checkbox", use version 2 (realanswer.2) instead.

Parameters

Required Attributes

The following attributes are required for the logic node to function properly:

  • ClientID–  Unique ID assigned to client by Imperium
  • Password–  Password assigned to client
  • SurveyID–  SurveyID
  • Target–  Which open-end needs to be sent
  • Username–  User ID assigned to client

Note: The attributes above should be provided by ImperiumYou will need to purchase an Imperium license to use this integration.

Once added, the realanswer.1 logic node takes the answer from an open end, sends it to the Real Answer webservice, and returns a response including the Real Answer Score (RAS) for that response.

Optional Attributes

You can add the following additional attributes to further define the Real Answer validation parameters for each open-end. Adding these attributes is entirely optional, and you can use one or all of them within your logic node:

  • BillingCode – Used if they want to submit a billing code for the submission.
  • EngagedLength –  Minimum length of response in words before the NonEngaged factor will be triggered. Anything under the specified number will trigger that flag.
  • SupressSimilarity –  If set to "1" will perform a similarity check on other responses to this question.

Note: The BillingCode attribute defaults to "Empty".

Additionally, you can use the LanguageCode attribute to set a new language for the validation check, or add one or more CheckCustomFactor variables to check responses against custom phrases that you define. 

LanguageCode

The LanguageCode attribute is a two-letter language code. The default validation language is English (EN), but you can use any of the supported language codes below:

LanguageCode

Language

EN

English

ZH-CHS

Chinese - Simplified

ZH-CHT

Chinese - Traditional

PT

Portuguese

DE

German

ES

Spanish

FR

French

NL

Dutch

SV

Swedish

NN

Norwegian

RU

Russian

IT

Italian

JA

Italian

PL

Polish

TR

Turkish

DA

Danish

FI

Finnish

MS

Malay

HU

Hungarian

RO

Romanian

SK

Slovak

ID

Indonesian

CS

Czech

BG

Bulgarian

VI

Vietnamese

 

CheckCustomFactor

There can be up to six CheckCustomFactor attributes in any survey, and these can be defined using custom phrases. Set each CheckCustomFactor attribute to "1" to run a check against its previously defined phrase:

CheckCustomFactor1

Perform a check for custom factor 1 to see if the string matches any of the previously defined phrases for this factor.

CheckCustomFactor2

Perform a check for custom factor 2 to see if the string matches any of the previously defined phrases for this factor.

CheckCustomFactor3

Perform a check for custom factor 3 to see if the string matches any of the previously defined phrases for this factor.

CheckCustomFactor4

Perform a check for custom factor 4 to see if the string matches any of the previously defined phrases for this factor.

CheckCustomFactor5

Perform a check for custom factor 5 to see if the string matches any of the previously defined phrases for this factor.

CheckCustomFactor6

Perform a check for custom factor 6 to see if the string matches any of the previously defined phrases for this factor.

 

Note: The CheckCustomFactor attributes all default to"0".

Additional Considerations

Using Conditional Logic

When using conditional logic in a Real Answer logic node, you may encounter an issue with the condition not propagating through the logic node. If this happens, you can encase your logic node in a <block> tag and apply the desired logic to that tag instead.

For example, the following is a logic node based onQ1.r1:

<block label="Block_1" cond="Q1.r1"> 
<logic label="Q2" 
realanswer:ClientID="clientID" 
realanswer:EngagedLength="3" 
realanswer:Password="password" 
realanswer:SurveyID="surveyID" 
realanswer:Target="Q1.r1" 
realanswer:Username="username" 
uses="realanswer.2" /> 
</block>
  • Was this article helpful?