CQS

Question with Confirmation#

Occurence: The term 'question' in this context refers to an additional input which can be used to collect data on a page. Rather than storing the data on the supporter's record, a question allows data to be collected transactionally.

This particular transaction type is generated when a question of the type Question with Confirmation is submitted, and is supplied with one of the valid 'status' values. The question functions as a type of 'double Opt-In', meaning that a supporter is not fully opted in until they have carried out two separate actions. The first action is providing a positive response to a question as it is presented on a page, the second is to click on a link in an email.

Co-occurence: Question responses are typically recorded together with any type of page submission, and responses can usually be linked directly to a page submission if needed.

Key Data: The timed question response, which will be one of the described status values, indicates whether the supporter is subscribed to the list or not. The page or other part of the software where the response was generated is also indicated.

In addition to the usual 'Y' or 'N' responses for Opt-in status, an answer of 'P' will indicate if a confirmation is Pending, meaning that the supporter has not yet clicked on the confirmation link in the email which was sent to the supporter when they submitted their response.

Export file columns#

Account ID#

Identifies the subaccount this item belongs to

Example: 94

Supporter ID#

The unique numerical database identifier for a supporter.

Example: 212200 Default: 0

Supporter Email#

The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated. <= 500 characters

Example: otto.nv@example.com

Date Created#

The date a supporter was created. [ISO 8601 format date]

Example: 2024-12-01

Date Modified#

The date a supporter was last modified. [ISO 8601 format date]

Example: 2024-12-01

Campaign Number#

A unique database identifier used to refer to a page, particularly in transactional data.

Where records in transactional data originate outside of a page structure, for example as a result of dashboard actions or imports, this will hold a value of 0, indicating that the transaction outcome should not be associated with a particular page. Default: 0

Example: 10122

Campaign Type#

CQS

Campaign ID#

The name given to this question in the dashboard. <= 100 characters

Example: Opt-in EMAIL

Campaign Status#

The current status of this response. The status is valid for Opt-in questions created to require a confirmation before the response will be accepted as positive.

Occurs as either:

Y N P D

Y Represents a positive response, which in terms of an Opt-in type question means that the supporter has agreed to receive communication.

N Represents a negative response, which in terms of an Opt-in type question means that the supporter does not wish to receive any communication.

P The response to this question is pending, which means that the supporter has not confirmed their Opt-in status by clicking on a confirmation link sent to them. Note that confirmation links sent to supporters are only valid for 24 hours.

Indicates that a response has been denied or deferred. This status is currently reserved.D

Default: N

Campaign Data 1#

The source of this transaction data. This would typically be a page submission carried out by a supporter, but may also be from data management.

Occurs as either:

Page Reference Name ENSAPI MANAGESUPP IMPORT

The internal reference name given to a page. <= 160 characters

ENSAPI A response originated from an external service using an API to submit the question response.

MANAGESUPP A supporter's question response was manually updated by a dashboard user.

IMPORT Available in manual data export only: A supporter's question response was imported from an external system. Note: In order to avoid feedback loops, any question responses imported using the system import.service are only made available through manual dashboard exports, and will not be returned with export.service data.