Skip to main content
Skip table of contents

Lookup Supporter Gadgets – Transaction History

The Supporter Lookup’s Transaction History gadget displays a list of the supporter’s transactional history stored within Engaging Networks by transaction type. Therefore it is a good overview of how the supporter has interacted with your pages and emails.

Each transaction item includes the three-letter transaction type, reference name of the transaction (such as page name or question name) and the date when the interaction occurred.

You can customize the type of transactions displayed and how many are displayed at once. You can also include multiple gadgets of this type in your layout with different filters and give each a custom display name.

What is displayed in the gadget?

Here’s an example of how the gadget might look for a supporter:

There are several pieces of information:

  • Colour – the colour of the bar gives you some quick information on the transaction. Green denotes a successful donation or event, red a failure. Blue are advocacy actions, light orange are opt-in submissions, dark orange are email activities
  • Type – the three-letter code denotes the type of transaction. See below of more information
  • Name – the name is the page name of an advocacy or fundraising transaction or email. For opt-ins it is the name of the opt-in itself
  • Date – when the transaction occurred (EST timezone)

The “Transaction History” gadget is meant to be a visual representation of the transaction only and does not allow you to accomplish transaction-specific tasks. The transaction-specific gadgets have additional functions built in to do this.

Getting more details

If you click on any of the items, it will slide open to reveal more information about that transaction. What is displayed depends on the transaction type. But some common ones are:

  • Time – the time the transaction occurred
For page completion types, e.g. ETT or FCS, these rows are also available:
  • Campaign ID – this is the campaign ID of the advocacy, donation or event page. Note that this is not the same to the page builder ID that can be seen in the URL
  • Tracking parameter – the tracking used on the transaction, if this was set up
  • Appeal code – the appeal code of the transaction, if this was set up
  • Device – the device (browser) used

In addition to these, we’ll list some of the more common transaction types and additional information available here:

EBC: Email broadcast transaction

Email broadcast transactions are denoted as EBC. Only emails that have been opened, clicked, completed or unsubscribed will be displayed here. You can click on the item to display more information on these activities.

Click here for more on email broadcast transaction data

ETT: Email to target transactions

Email to target transactions are denoted as ETT. Only fully participated ETTs (rather than registrations) are displayed, although you can export registrations as well. In addition to the standard information that is shown, ETT transactions include a Contact that is the target of the ETT, and a Contact Organization which is the Organization (often the area they represent, e.g. constituency) of the target.

QCB: Opt-in transactions

Opt-in transactions are denoted as QCB.

  • Source – the name of the page that the opt-in was submitted on
  • Response – the response (Y or N) to the opt-in
  • Opt in statement – the content of the opt-in that was submitted. Note that this will only appear if you have amended or re-saved your opt-ins after 20 April 2018 which is when this facility was added to the software

Transaction History Download

You can click the down arrow to download all transactions, or user data, for the supporter. Read more here.


By default this gadget loads with a default name, every transaction type displayed and only ten transactions are loaded at a time.

To customize the display name, which transaction types are displayed, or to change the number of transactions loaded at a time click on the settings icon


  • Enter the new name into the text field provided
  • You can choose to load 5, 10, 20, 30, and 50 transactions per page
  • Click on the transaction types you would like to disable/enable
  • Click “Save” once you are complete customizing the gadget to apply your changes.

In order to view the custom display name of your gadget you must first exit the supporter record.

Campaign types

Type of activityDefault code
Email to TargetETT
Tweet to TargetTWT
Click to callCTT
Legacy only
Data Capture FormDCF
Email SubscribeEMS
Advocacy PetitionPET
Email subscription management pageUNS
Broadcast Email
Email sends do not generate this transaction. Only email interactions do, e.g. opens, clicks
Marketing Automation EmailMBC
Checkbox questions are also recorded as QCB, but are not included in this gadget
Fundraising Credit/Debit Single
e.g. card donation
Fundraising Credit/Debit Recurring
a recurring card payment managed by Engaging Networks
Unmanaged recurring payment
a recurring payment not managed in Engaging Networks e.g. PDD
Fundraising Bank Single FBS
Fundraising Bank RecurringFBR
Fundraising In MemoriamFIM
Fundraising CashFCA
Fundraising CheckFCH
Fundraising One ClickFOC
Refund transactionRFD
Memberships payments
Legacy only
Peer-to-peer RegistrationAMR
Peer-to-peer Credit SingleACS
Peer-to-peer Credit RecurringACR
Peer -to-peer donation
Legacy only
Peer-to-peer registration
Legacy only
Event Purchase – Credit/Debit SingleECS
Event Purchase – Bank SingleEBS
Event Purchase – Free/Cash ticketsECC
Premium ItemPTM
Ecommerce ItemETM
Peer-to-peer check or cash paymentACC
Peer-to-peer event registration credit feeACF


NOTE: The following transaction types are not visible in the transaction history gadget: ENS – Supporter Service Create  SSC ENS – Supporter Service Update SSU Event Ticket Attendee ETA Event Ticket Purchase ETK Hub Supporter Update HSU Manage Supporters Create MSC Manage Supporters Update PTM Manual Supporter Update MSU Question Confirmation QCS Question Multiple Response QMR

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.