Exporting data options

After you've run your data export query, you can export your data into a spreadsheet to view or manipulate the data outside of the Engaging Networks account.

You can export the data into XLS and CSV (Comma Separated Values) file types. Additionally, the following data formats are available: User data, Transactional data, and Hybrid data.

You can use 'User data' option to export only personal data columns of users who fulfil your selected criteria. Use the 'Transactional data' option if you need to access detailed information for each transaction (you will be able to view each individual transaction data in a separate row). Exporting with the 'Hybrid data' format will provide you with the list of personal data columns followed by columns corresponding to participation in selected campaigns or answers to selected questions.

Independently of the format you use, the default supporter record fields will be presented exactly as they are set up in Hello > Account settings > Account Data Structure. Alternatively you can create a customized list of fields using the 'Create export group' function in Hello <Your Name> > Account settings > Account Data Structure. Please see the relevant file on that page for further details.

Please note: Files larger than 65K rows must be downloaded as CSV.

Downloading data

The export process will run in the job monitor until it is ready to be downloaded. Within the monitor, you can check the percentage completed of the export, and when ready download the exported file by clicking the download icon .

Three types of data formats

User data format

The "user data" format only provides static default supporter record data of all supporters who fulfilled your selected export criteria. Transactional information and question answers will not be included in the file.

The data will be presented by default in the same format as your default user record, as displayed in the example below:

First name

Last name

Address 1

City

Postcode

Email

Josh

Miller

Engaging Networks

Washington

20036

josh@engagingnetworks.net

James

Seddon

Engaging Networks

London

WC2H 9NJ

james@engagingnetworks.net

Hybrid data format

The exported file will combine default supporter record data of all supporters who fulfilled your selected export criteria with some basic transactional information.

Hybrid combines data for each supporter into a single row, with the final columns giving information about the transaction or transactions associated with the query.

Please see the 'Campaign status values' table below for explanation of values in the columns related to transactions.

Here is an example Hybrid file:

First name

Last name

City

Postcode

Email

Campaign X

Opt in

Marta

Fornal

London

SW9 7AB

marta@email.com

:R:06/01/2012::P:06/01/2012

Y

Transaction format

In this format, each transaction (created when a supporter participates in an action, answers a question or opt-in, donates, opens an email and so on) will be displayed in a separate row of data. This offers the most detailed and complete data export.

For example, if a single user made a donation and answered two questions, that will result in three rows of data for this specific user: one row providing donation details and two rows providing question answers correspondingly.

The data file is divided into three main sections: basic data, transaction data, and default record.

The titles in bold will appear as column headers.

Transaction format section 1 - basic data

This section gives you basic data identifying the supporter who the record relates to, and by default makes up the first five columns in the file.

Account ID: The unique ID of the subaccount from which the data are being exported.Supporter ID: A unique ID number identifying the supporter in the datbase.Supporter email: The email address of the supporter the activity record relates to (this acts as a unique identifier in the software).Date created: The date on which the user data record for the supporter (not the specific activity record) was created.Date last modified: The date of the last occasion on which the data of the supporter was modified.

Transaction format section 2 - transactional data

This section contains data relating to the specific activity involving the supporter.

Campaign number: This column gives a unique number that refers to the campaign that the transaction relates to. Note that this is not the same as the page ID you see in page-builder's URLs. You can search for the page in the system using this number by searching for cid:XXX, e.g. cid:12345Campaign type: This column identifies which type of activity the record relates to. For campaign type codes, see the table 'Campaign type codes' below. Note that QCB transactions are not recorded for imported data.Campaign ID: This identifies the specific campaign the record relates to. By default this will be the reference name you have given the campaign in your account.Campaign date and campaign time: These two columns give the specific time and date the supporter's transaction took place. Note that Engaging Networks displays times in the US Eastern timezone. For email broadcast transactions, the date and time refers to when the page was submitted or when the first email transaction occurred, e.g. Open. Subsequent activity, e.g. a click, does not update the time but will record a click in the relevent column (see Campaign Data columns 1 to 6 on the next pages)Campaign status: This gives information about whether an activity has been successfully completed or not. The precise value that appears depends on the type of activity. See the 'Campaign status values' table below.Campaign data columns 1 to 35: The content of these 35 columns also depends on the type of activity. See the 'Campaign data information' over the next pages for more details.

Transaction format section 3 - supporter record

The final section of the data export contains the details of the particular supporter taking the action. The columns that appear correspond to the form fields you have defined in the account data structure (default supporter record) in your account, so the number of columns appended to the export will vary between clients.