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 > Account settings > Account Data Structure. Please see the relevant file on that page for further details.

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

1) 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

2) 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

In this example, they have taken “Campaign X” twice, which is why two dates are in the single cell. The R means registered, and the P means fully participated.

3) 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.

Transaction format layout

As the most complex and detailed version of the data export, we’ll go into the transaction export format in more detail. This export is split into three main sections, detailed below. 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 database.
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:12345
Campaign 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.

Transaction export columns

Campaign type codes

Type of activity

Default code

Email to Target

ETT

Tweet to Target

TWT

Tell-a-friend

TAF

Data Capture Form

DCF

Email Subscribe

EMS

Advocacy Petition

PET

Broadcast Email

EBC

Marketing Automation Email

MBC

Question Checkbox

QCB

Question Confirmation

QCS

Question Multiple Response

QMR

Fundraising Credit/Debit Single

FCS

Fundraising Credit/Debit Recurring (managed by Engaging Networks)

FCR

Recurring payment not managed in Engaging Networks (e.g. PDD)

FUR

Fundraising Bank Single

FBS

Fundraising Bank Recurring

FBR

Fundraising In Memoriam

FIM

Fundraising Cash

FCA

Fundraising Check

FCH

Memberships

MEM

Manage Supporters Update

MSU

Manage Supporters Create

MSC

Manual Supporter Update

MSU

Manual Supporter Create

MSC

Peer-to-peer Registration

AMR

Peer-to-peer Credit Single

ACS

Peer-to-peer Credit Recurring

ACR

Event Purchase – Credit/Debit Single

ECS

Event Purchase – Bank Single

EBS

Event Purchase – Free/Cash tickets

ECC

Event Ticket Purchase

ETK

Event Ticket Attendee

ETA

Premium Credit Single

PCS

Premium Item

PTM

Campaign status values

Type of activity

Status value

Meaning

Email to Target and Tweet to Target

R

Registered – Supporter has completed the first page of the action, but has not submitted the message

P

Participated – Supporter has completed the action and submitted a message to their target

Data Capture Form

P

Participated

Email Subscribe Form

P

Participated

Advocacy Petition

P

Participated

Engaging Networks tell-a-friend

P

Participated

Broadcast email

For a transactional export, the Campaign Status is always R. Campaign data columns 1-6 will contain information on the interactions with the email (open, click, formsub, hbounce, sbounce, unsub)

For a hybrid export, these different values will be contained within the single cell value in the email campaign column. O means message opened, CT means link clicked, SB means message soft bounced, HB hard bounced, U means unsubscribed. 

R

Message received by supporter

Membership

New Membership

This indicates a brand new membership purchase

Renewal Term

The amount of days remaining in the membership

Lapsed

The membership has expired

Question checkbox

Y

Box ticked

N

Box not ticked

Question Confirmation

Y

Box checked

N

Box unchecked

P

Pending – Constituent needs to click the link in the email

D

Declined – The subscription was not approved

Question multiple

Y

Question answered (whatever the response). The response will be 

N

Question left unanswered

Fundraising Credit/Debit Single

Success

The payment was successful

Reject

The payment gateway rejected the payment

Pending

The payment has not yet been verified by the payment gateway

Fundraising Credit/Debit Recurring

Success

The payment was successful

Reject

The gateway rejected the payment

Fundraising Bank Single

Success

The payment was successful

Reject

The gateway rejected the payment

Fundraising Bank Recurring

Success

The payment was successful

Reject

The gateway rejected the payment

Fundraising In Memoriam

Success

The payment was successful

Reject

The gateway rejected the payment

Fundraising Cash/Check

Success

The payment was successful

Reject

The gateway rejected the payment

Peer-to-Peer Credit Single

P

The payment was successful

R

The gateway rejected the payment

Peer-to-Peer Credit Recurring

P

The payment was successful

R

The gateway rejected the payment

Campaign data columns 1 to 6

This shows what each “Campaign data” column will contain for a transaction export. See the attached file (at the bottom) for a downloadable template. 

 

Campaign data column

Type of activity

1

2

3

4

5

6

Email to Target or Tweet to Target

Target first name

Target last name

Target Organization

Target Database Name (if assigned)

BLANK

BLANK

Email Subscribe Form

BLANK

BLANK

BLANK

BLANK

BLANK BLANK

Advocacy Petition

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Data Capture Form

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Email-A-Friend

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Broadcast Email

‘Open’ – Email was opened

‘Click’ – Any tracked link clicked

‘Formsub’- Form was subitted after click

‘Hbounce’ – Hard Bounce recorded

‘Sbounce’-Soft Bounce Recorded

‘Unsub’-Unsubscribe was clicked

Question Check Box

Name of page that question was used on

BLANK

BLANK

BLANK

BLANK

BLANK

Question Confirmation

Name of page that question was used on

BLANK

BLANK

BLANK

BLANK

BLANK

Question Multiple Reponse

Question value 1

Question value 2 (if applicable)

Question value 3 (if applicable)

Question value 4 (if applicable)

Question value 5 (if applicable)

Question value 6 (if applicable)

Fundraising Credit/Debit Single

Database assigned unique ID

Gateway assigned unique ID

Gateway assigned error code – if reject

Payment Amount

Payment Currency

Credit Card Name

Fundraising Credit/Debit Recurring

Database assigned unique ID

Gateway assigned unique ID

Gateway assigned error code – if reject

Payment Amount

Payment Currency

Credit Card Name

Fundraising Bank Single

Database assigned unique ID

Gateway assigned unique ID

Gateway assigned error code – if reject

Payment Amount

Payment Currency

Account Type – Checking/Savings

Fundraising Bank Recurring Database assigned unique ID

Gateway assigned unique ID

Gateway assigned error code – if reject

Payment Amount

Payment Currency

Account Type – Checking/Savings

Fundraising In Memoriam Database assigned unique ID

Gateway assigned unique ID

BLANK

Payment Amount

Payment Currency

In Memoriam Indicator – Y or N

Fundraising Cash/Check Database assigned unique ID

Check Number

BLANK

Payment Amount

Payment Currency

Payment Method – Cash/Check

Membership

Membership Status – ‘Active’ or ‘Lapsed’

Database assigned unique member ID

Alternate Member ID

Gateway assigned unique ID – if applicable

Amount Paid – If applicable

Currency – if applicable !23

Manage Supporters Create

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Manage Supporters Update BLANK BLANK BLANK BLANK BLANK BLANK
Peer-to-Peer Registration Database assigned Peer-to-Peer unique Site ID Peer-to-Peer site reference name Donation page ID Peer-to-Peer site reference name BLANK BLANK
Peer-to-Peer Credit Single Database assigned unique ID Gateway assigned unique ID Gateway assigned error code – if reject Payment Amount Payment Currency Credit Card Name
Peer-to-Peer Credit Recurring Database assigned unique ID Gateway assigned unique ID Gateway assigned error code – if reject Payment Amount Payment Currency Credit Card Name
Event Purchase – Credit/Debit single Database assigned unique ID Gateway assigned unique ID Gateway assigned error code – if reject Payment Amount Payment Currency Credit Card Name
Event Purchase – Bank single Database assigned unique ID Gateway assigned unique ID Gateway assigned error code – if reject Payment Amount Payment Currency Credit Card Name
Event Ticket Purchase Database assigned unique ID Event page Reference name Gateway assigned unique ID Ticket(s) purchased cost Payment Currency Quantity (of tickets for this type)
Event Ticket Attendee Database assigned unique ID Event page Reference name Gateway assigned unique ID Event Ticket ID Attendee Title Attendee First Name

Campaign data columns 7 to 12

Note: Records relating to email to target, data capture, email a friend, cash/check donations, broadcast emails, or question activity do not contain any further data in this section.

 

Campaign data column

Type of activity

7

8

9

10

11

12

Fundraising Credit/Debit Single

‘S’ – transaction frequency (single)

BLANK

BLANK

BLANK

Transaction refunded: “Y”

Gateway Name

Fundraising Credit/Debit Recurring

‘R’ – transaction frequency (recurring)

Day of the month recurring payment occurs

Transaction recurring frequency

Recurring Status – ‘active’, ‘suspended’, or ‘canceled’

Gateway assigned unique ID of parent transaction

Gateway Name

Fundraising Bank Single ‘S’ – transaction frequency (single) BLANK BLANK BLANK

Transaction refunded: “Y”

Gateway Name

Fundraising Bank Recurring ‘R’ – transaction frequency (recurring)

Day of the month recurring payment occurs

Transaction recurring frequency

Recurring Status – ‘active’, ‘suspended’, or ‘canceled’

Gateway assigned unique ID of parent transaction

Gateway Name

Fundraising In Memoriam

‘S’ or ‘R’ – transaction frequency (single/recurring)

Recognize Gift-‘Y’ or ‘N’

Tribute Options form value

Reason for Gift (form value)

Honoree Name

Inform Name

Membership

‘S’ or ‘R’ – transaction frequency (single/recurring)

Membership Type

Number of Members

Membership Start Date

Current Membership Term Start Date

Current Membership Term End Date

Manage Supporters Create

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Manage Supporters Update

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Peer-to-Peer credit single

‘S’ – transaction frequency (single)

BLANK

BLANK

BLANK

Transaction refunded: “Y”

Gateway Name

Peer-to-Peer credit recurring

‘S’ – transaction frequency (single)

BLANK

BLANK

BLANK

Transaction refunded: “Y”

Gateway Name

Event Purchase – Credit/Debit single

BLANK

BLANK

BLANK

BLANK

Transaction refunded: “Y”

 

Event Purchase – Bank single

BLANK

BLANK

BLANK

BLANK

Transaction refunded: “Y”

 

Event Purchase – Cash/Free tickets

‘S’ – transaction frequency (single)

BLANK

BLANK

BLANK

Transaction refunded: “Y”

 

Event Ticket purchase

Ticket Type (‘single’ or ‘group’)

Discount code

Is during a ticket sale period (‘Y’ or BLANK)

Event Ticket ID

BLANK

BLANK

Event Ticket Attendee

Attendee Last Name

Attendee Email Address

Attendee Address 1

Attendee Address 2

Attendee City

Attendee Region

Campaign data columns 13 to 18

Note: Records relating to email to target, data capture, email a friend, cash/check donations, broadcast emails, or question activity do not contain any further data in this section.

 

Campaign data column

Type of activity

13

14

15

16

17

18

Fundraising Credit/Debit Single

Credit Card Expiration Date

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

BLANK

BLANK

Receipt ID – if enabled in ‘Account Settings’

Fundraising Credit/Debit Recurring

Credit Card Expiration Date

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

Recurring Start Date

Recurring End Date

BLANK

Fundraising Bank Single

BLANK

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

BLANK

BLANK

Receipt ID – if enabled in ‘Account Settings’

Fundraising Bank Recurring

BLANK

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

Recurring Start Date

Recurring End Date

BLANK

Fundraising In Memoriam

Inform Email Address

Inform Address 1

Inform Address 2

Inform City

Inform Region

Inform Postcode

Membership

Number of Days Left in Current Term

Number of Renewal Terms

Membership Cost

Amount of Cost Paid to Date

Membership Fully Paid – ‘Y’ or ‘N’

Member 1 Name

Manage Supporters Create

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Manage Supporters Update

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Peer-to-Peer credit single

Credit Card Expiration Date

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

BLANK

BLANK

Receipt ID – if enabled in ‘Account Settings’

Peer-to-Peer credit recurring

Credit Card Expiration Date

Tax Deductible-‘Y’ or ‘N’

Apply to pledge: “pledge ID”

BLANK

BLANK

Receipt ID – if enabled in ‘Account Settings’

Event Purchase – Credit/Debit single

           

Event Purchase – Bank single

           

Event Purchase – Cash/Free tickets

           

Event Ticket purchase

BLANK

BLANK

BLANK

BLANK

BLANK

BLANK

Event Ticket Attendee

Attendee Postcode

Attendee Country

 
Updated on August 21, 2019

Article Attachments

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support