Properties

SamplingPriorityField

Restriction: DEPRECATED This feature is for the obsolete pool-based sampling mechanism.

This integer field assigns priority to records during pool-based sampling. Records with the lowest value in this field are presented first to the sampler.

MemberDuplicateFields

Identifies fields used for duplicate-record testing when uploading invitations using the Manual Invitations screen and for the Stay Model (STAY_IMPORT processor in LEGO importer). 

Leave this option empty to suppress duplicate checking.

When creating invitations, if all of the Member Duplicate Fields values in the potential record match the values in an existing record, the invitation is rejected. For example, a hospitality company might use Email, Property ID, and Checkout Date as duplicate check fields. A potential invitation is rejected only of a survey record already exists with the same email, ID, and date.

The Auto Importer has its own duplicate field-check mechanism and is not affected by this setting. Instead, the Survey Auto Importer only checks values in the survey table, while the Episode Auto Importer only checks the episode table.

For pool-based invitations, the system only checks values that are stored in the episode table. Any changes to survey records (such as through a SURVEY_UPDATE LEGO) do not impact the duplicate checker, because SURVEY_UPDATE does not alter the episode table.

Important: Best practice is to create a unique episode combination when picking fields. Include a field that is unique to the episode. DO NOT, for example, pick just email, first, and last name because that block the user from ever seeing another survey.

MemberOptOutFields

Identifies the fields to be made available and used for opting out of receiving invitation from the company. When an invitee chooses to opt-out, the information about that invitee in these MemberOptOutFields is copied from the associated survey record into the opt-out database. Future sampling excludes email invitations who survey record fields match the values in any of these fields. 

The opt-out field is usually just the invitee's email address, though might be phone number for SMS surveys. The logic statement between assigned fields in MemberOptOutFields is OR. This means that when there are multiple fields, a matched value in ANY field excludes the email. For example, if both Email and FirstName are selected, any record having the same First name value is excluded. To create an AND condition, add a field whose value is a concatenation of the target fields, and the concatenation is performed during the import process.

Warning: Opt-out processing of TEXT and AUTOINDEX_TEXT data type is case-sensitive. For example, these two ID values are not equal:

qr12mp2
QR12MP2

When using Auto Importer to load opt-out records, ensure the data is processed appropriately. For example, if case-sensitivity is not an issue for the fields, consider transforming the fields to all lower-case during import. Otherwise, verify the fields always use the same case considerations for all import feeds.

This does not affect fields of type EMAIL.

MemberInvitationHiddenFields

Hides Event fields from the Manual Invitations screen where you manually create individual invitation. Only the unselected fields are available to the administrators.

Note: When a field is marked as internal in its definition, the LEGO STAY_IMPORT process cannot see the field, but SURVEY_IMPORT can.

SelectedReportingHiddenQuestions

Hides selected questions from reports.