QCB

Question CheckBox#

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 transaction type is typically produced as the response to a question of type Opt In, which is a primary method used to handle messaging subscription lists within the software.

The transaction type may also be generated if a supporter's answer to a question of type General or Opt-in is provided as a single character value of either Y, N, P or D.

Co-occurence: Question responses are typically recorded together with page submissions, and responses can usually be linked directly to a page submission.

Key Data: The timed question response, which for an Opt-in type question is typically either Y or N, indicates whether the supporter is subscribed to the respective list or not. The data will also indicate the page where the response was submitted, unless the response was submitted through an administrative interface or via import. Note that Imported Opt-in responses will not be available via the export.service, but may be accessed using the dashboard export facility.

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#

QCB

Campaign ID#

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

Example: Opt-in EMAIL

Campaign Status#

The response provided for a question was a checkbox type input with specific values.

Occurs as either:

Y N P D

Indicates a positive answer. For questions designated as Opt-in, the software typically uses a positive answer as an indication of consent.Y

Indicates a negative answer. For questions designated as Opt-in, the software typically uses a negative answer to indicate the withdrawal or absence of consent.N

Indicates that a response is pending. The pending status is particular to Opt-in questions which require confirmation, but may occur if any Opt in or General type question receives this value.P

Indicates that a response has been denied or deferred. This status is currently reserved, but may occur if any Opt in or General type question receives this value.D

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.