Feedback record events
When events happen during the life of a record.
A-fields and E-fields both track information about feedback record events. E-fields record information about the record, while A-Fields record information about the feedback signal itself. The difference is subtle so, if there is not an A-Field with the information you want, search if there is an E-field that does.
Sequence of record events
This is the sequence of events that happen in a feedback record. Depending on the type of record and the types of processing performed on it, not all of these events occur in every record. For example, Anonymous surveys do not have Sampling or Invitation events. When an event does not happen, the field value is set to null.
These fields, which display a date, are created and updated at each stage in the life of a record:
- Importing
-
e_creationdate — Record created, but incomplete.
- Ready for sampling
-
e_record_creation_date — Record created and ready for export or sampling.
- Sampling
-
a_sampled_date — Sampling completed.
- Survey ready
-
e_survey_available_date — Record is ready for a respondent to interact with it.
- Inviting
-
e_delivereddate — When the Invitation email was sent.
a_survey_first_bounce_date — When the first invitation bounced (not delivered).
e_remindeddate — Reminder email was passed to the SMTP (mail) server for delivery.
a_invite_first_opened_date — The Invitation email was first opened.
- Survey started
-
a_startdate — The first page of the survey was sent to the survey taker. When
a_startdateis set,a_survey_is_partial = true.e_lastupdated — An externally visible field changed. It may be updated later.
a_page_path_timestamps — When each survey pages was sent.
e_responsedate — The survey taker completed the survey.
a_survey_response_date — The survey taker completed the survey. When
a_survey_response_dateis set,a_survey_is_partial = false. - Alerting
-
a_alert_date_created — The alert was created.
a_alert_date_resolved — The alert was resolved. It may be updated later.
a_alert_date_closed — The alert was closed. It may be updated later.
- Rapid response
-
a_rapid_response_send_date — The first response was sent. It may be updated later.
a_rapid_response_business_time — Elapsed time between first alert and first response. It may be updated later.
- Text Analytics
-
e_ta_eligible_date — Record is first marked for Text Analytics processing. The record is set with Tag status = TAGGING_NEEDED. This date is usually less than or equal to
e_ta_completed_date.e_ta_completed_date — Completed Text Analytics processing. In general, Tag status are updated after being processed by Text Analytics. However, this date is also set when:
The record is discarded during a pre-filtering process. This happens when there is no content for Text Analytics to process.
The recorded is updated in the database engine (Pump). This happens when there is no content for Text Analytics to process.
Note: Generally,e_ta_eligible_dateis less than or equal toe_ta_completed_date. - Reporting
-
e_initialfinishdate — When the record was first accepted for reporting. It is set when the record is updated in the database engine (Pump) and when its status is COMPLETION_PENDING or EXIT_AUTO_EXCLUDED. It never changes.
Note: There is no way to ensure thate_initialfinishdateis less or greater thane_ta_completed_datease_initialfinishdateis defined independently from Text Analytics processing. It may change depending on the order of certain events.e_accepteddate — When the record was last accepted for reporting. It may be updated later.
Anonymous survey event differences
For Anonymous surveys, the record is created after the first page of the survey has been submitted. As such, Creation date happens after some survey-taking timestamps. In the case of a one-page survey, the creation date happens after the survey has been completed (e_responsedate).
