...
The data file is divided into several main sections: basic data, transaction data, external reference fields, origin source, and default supporter record. The transactional data section “reuses” columns to represent different pieces of information depending on the campaign type.
| Info |
|---|
Transactional data reference template Click here to download an XLSX template of the transaction export file that shows what these columns represent |
Read more on this format below.
2) 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.
...
First name | Last name | Address 1 | City | Postcode | |
Josh | Miller | Engaging Networks | Washington | 20036 | josh@engagingnetworks.net |
James | Seddon | Engaging Networks | London | WC2H 9NJ |
3) Hybrid data format (legacy)
In this format, the exported file will combine default supporter record data of all supporters who fulfilled your selected export criteria with some basic transactional information.
...
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 emailEmail: The email address of the supporter the activity record relates to (this acts as a unique identifier in the software).
Date createdCreated: The date on which the user data record for the supporter (not the specific activity record) was first created.
Date last modifiedModified: The date of the last occasion on which the data of the supporter was modified. Data is counted as being modified when any transaction is created (for example, taking action, donating, opening an email), if data is imported, if data is updated via the Supporter Lookup tool, if Data Mapping updates a supporter record, and if data is updated via our APIs.
Transaction format section 2 – transactional data
...
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: Imported QCB updates are not included in export API 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. Check this the attached Excel document for more information.
Transaction format section 3 – external references
...
Campaign | Transactional code | ||
|---|---|---|---|
Email to Target | ETT | ||
Tweet to Target | TWT | ||
Click to call | CTT | ||
Data Capture Form | DCF | ||
Email Subscribe | EMS | ||
Advocacy Petition | PET | ||
Survey | SVY | ||
Ecard | ECF | ||
Email subscription management page | UNS | ||
Broadcast Email | EBC | ||
Marketing Automation Email | MBC | ||
Opt-ins and checkbox questions Radio opt-ins are also recorded as QCB. Note: Imported QCB updates are not included in export API data. | QCB | ||
Question Confirmation | QCS | ||
Question Multiple Response | QMR | ||
Fundraising Credit/Debit Single | FCS | ||
Fundraising Credit/Debit Recurring | FCR | ||
Unmanaged recurring payment | FUR | ||
Fundraising – Recurring Update | FRU | ||
Fundraising Bank Single | FBS | ||
Fundraising Bank Recurring | FBR | ||
Fundraising In Memoriam | FIM | ||
Fundraising Cash | FCA | ||
Fundraising Check | FCH | ||
Fundraising One Click | FOC | ||
Refund transaction | RFD | ||
Memberships payments | MSP | ||
Memberships – member association | MMR | ||
Memberships | MEM | ||
Manage Supporters Update | MSU | ||
Manage Supporters Create | MSC | ||
Manual Supporter Update | MSU | ||
Manual Supporter Create | MSC | ||
Legacy Peer-to-peer Registration | AMR | ||
Legacy Peer-to-peer Credit Single | ACS | ||
Legacy Peer-to-peer Credit Recurring | ACR | ||
Legacy Peer-to-peer Bank Single | ABS | ||
Legacy Peer-to-peer Bank Recurring | ABR | ||
Legacy Peer-to-peer Cash or Check | ACC | ||
Legacy Peer-to-peer Registration Credit Fee | ACF | ||
Legacy Peer-to-peer Registration Bank Fee | ABFPeer -to-peer donation | P2P | Peer-to-peer registration |
Event Purchase – Credit/Debit Single | ECS | ||
Event Refund Single/Recurring | EFD | ||
Event Purchase – Bank Single | EBS | ||
Event Purchase – Free/Cash tickets | ECC | ||
Event Ticket Purchase | ETK | ||
Event Ticket Attendee | ETA | ||
Premium Item | PTM | ||
Ecommerce Symbolic giving Item | ETM | ||
Manage Supporters Update | MSU | ||
Manage Supporter Create | MSC | ||
Hub Supporter Update | HSU | ||
ENS – Supporter Service Create | SSC | ||
ENS – Supporter Service Update | SSU | ||
SMS Broadcast | SBC |
Campaign status values
Campaign type | Value | Description |
|---|---|---|
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 will contain transaction specific data. See this template of the transactional export file for more details on each transaction type.
| View file | ||
|---|---|---|
|