Account Data Structure Tagged Field List

The Account Data Structure contains a list of fields, some of which are tagged. Tagged fields contain certain pre-defined types of data and are mapped for specific use in the platform. For example, the field tagged as Postcode is used to lookup a Supporter’s representatives for an Email to Target or Click to Call pages and the tagged Email Address is used to uniquely identify the supporter.

There is also an option to use untagged fields, which have no pre-define use and can be defined based on an organizations’ particular needs and goals. For example, an organization may create an offline database ID field, to make it more easy to match supporters between the two systems. Because this field is not used by the Engaging Networks platform for any special purpose, it would be added as an untagged field. Untagged fields have a maximum length of 2000 characters.

Field	Description	Character limit	URL Parameter
Untagged	No defined meaning in Engaging Networks. Can be used for data unique to individual organizations	2000	`supporter.NOT_TAGGED_XX` Parameters for untagged fields vary. Read here for how to find the correct parameter in the HTML.

Available Tagged Fields

The table below provides a description of each of the pre-assigned, tagged fields in the Account Data Structure.

Field	Description	Character Limit	URL Parameter (case sensitive)
Title	Constituent’s Name Prefix	50	`supporter.title`
First Name	Constituent’s First Name Value	500	`supporter.firstName`
Middle Name	Constituent’s Middle Name Value	500	`supporter.middleName`
Last Name	Constituent’s Last Name Value	500	`supporter.lastName`
Address 1	Constituent’s Street Address	1000	`supporter.address1`
Address 2	Constituent’s Apt, Floor, Suite, Etc.	1000	`supporter.address2`
Address 3	Additional Address Information	1000	`supporter.address3`
City	Constituent’s City	500	`supporter.city`
Region	Constituent’s State, Province, etc.	500	`supporter.region`
Email Address	Constituent’s Primary Email (unique identifier in the software)	500	`supporter.emailAddress`
Postcode	Constituent’s Postal Code	200	`supporter.postcode`
Country	Constituent’s Country	500	`supporter.country`
Phone Number	Supporter's Phone Number	200	`supporter.phoneNumber`
Donation Amount	Amount of the Donation	Numeric value	`transaction.donationAmt`
Payment Type	Type of Credit Card, PayPal, or Bank Account	50	`transaction.paymenttype`
Credit Card Number	Number of Credit Card Being Used to Donate We do not store card numbers in the system, but this field is required for that information to be entered by the supporter.	18	`Sensitive data shouldn't be passed over a URL`
Credit Card Expiration Date	Expiration of Credit Card Being Used to Donate	8	`transaction.ccexpire`
Credit Card Verification Value	Verification Code of Credit Card Being Used to Donate	4	`Sensitive data shouldn't be passed over a URL`
Card Holder Name	Name of Owner of Credit Card Being Used to Donate	500	`supporter.creditCardHolderName`
Card Start Date	Date that Credit Card Being Used to Donate was Issued	20
Bank Account Number	Number of Bank Account being Used to Donate	50	`supporter.bankAccountNumber`
Bank Routing Transit Number	Routing Number of Bank Hosting Account from which Donation Is Made	20	`supporter.bankRoutingNumber`
Bank Account Type	Type of Bank Account (Checking/Savings) from which Donation is Made	30	`supporter.bankAccountType`
Bank Name	Name of Bank Hosting Account from which Donation is Made	500	`N/A`
Issue Number	Issue Number of Credit Card Being Used to Donate (not used in USA / UK)	2	`N/A`
Payment Currency	Type of Currency being Used to Donate	3	`transaction.paycurrency`
Recurring Payment	Flag to Indicate if Donation is Recurring (‘Y’)	1	`transaction.recurrpay`
Recurring Day	Day the Next Recurring Payment Should Occur Supported values are 1-30	2	`transaction.recurrday`
Recurring Start Date	Date Recurring Donation Payments Began The recurring start date must be formatted YYYY-MM-DD	20	`transaction.recurrstart`
Recurring End Date	Date Recurring Donation Payments Will Stop The recurring end date must be formatted DD/MM/YYYY	20	`transaction.recurrend`
Recurring Count	Number of Recurring Donation Payments to Process	500	`transaction.recurrcnt`
Recurring Frequency	How Often Recurring Donation Payments Occur	10	`transaction.recurrfreq`
Recurring Period	Length of Time Between Recurring Donation Payments	Numeric value	`transaction.recurprd`
Tax Deductible	Flag to Indicate if Donation is Tax Deductible (‘Y’) (you can use this for Gift Aid)	1	`transaction.taxdeductible`
Pledge Amount	Amount of Donation Being Pledged to a Specific Category	Numeric value	`N/A`
Recognize Gift	Flag to Indicate if Donor / Donation Should be Specially Recognized (‘Y’)	1	`transaction.recnzegft`
Additional Comments	Additional Comments Related to Transaction / E-cards personalized message field	4000	`transaction.comments`
Anonymous Donor	Flag to Indicate if Donation is Being Made Anonymously (‘Y’)	10	`supporter.anonymousDonor`
Send Offset	Field values for supporter time offsets from GMT (+00:00) for use with Send Time Optimization.	Acceptable values: `+10:00 +09:30 +09:00 +08:00 +05:30 +03:00 +01:00 -00:00 +00:00 -03:00 -04:00 -05:00 -06:00 -07:00 -08:00`	`supporter.sendOffset`
IN MEMORIAM ONLY BELOW
In Memoriam	Flag to Indicate if Donation is Being Made in Memory/Honor of Someone (‘Y’ value must be submitted)	1	`transaction.inmem`
Inform Email	Email of Person Being Informed of In Memoriam Gift	400	`transaction.infemail`
Inform Name	Name of Person Being Informed of In Memoriam Gift	400	`transaction.infname`
Inform Address 1	Address of Person Being Informed of In Memoriam Gift	400	`transaction.infadd1`
Inform Address 2	Address 2 of Person Being Informed of In Memoriam Gift	400	`transaction.infadd2`
Inform City	City of Person Being Informed of In Memoriam Gift	400	`transaction.infcity`
Inform Region	State/Province of Person Being Informed of In Memoriam Gift	400	`transaction.infreg`
Inform Postcode	Postcode of Person Being Informed of In Memoriam Gift	400	`transaction.infpostcd`
Inform Country	Country of Person Being Informed of In Memoriam Gift	400	`transaction.infcount`
Honoree Name	Name of Person in Whose Honor the In Memoriam Gift is Made	400	`transaction.honname`
Gift Reason	The Reason that In Memoriam Gift is Made	4000	`transaction.gftrsn`
Tribute Options	Choices of Tribute Gifts	400	`transaction.trbopts`
END IN MEMORIAM FIELDS
Direct Gift	Where (Target / Purpose) the Donor Wants to Direct Their Gift to be Used	255	`transaction.dirgift`
Appeal Code	Extra Field Used for Tracking Data About One Specific Transaction Page	300	`supporter.appealCode`
Second Address 1	Supporter’s Secondary Address	1000	`supporter.secondAddress1`
Second Address 2	Supporter’s Secondary Apt, Floor, Suite, Etc.	1000	`supporter.secondAddress2`
Second City	Supporter’s Secondary City	500	`supporter.secondCity`
Second Region	Supporter’s Secondary State, Province, Etc.	500	`supporter.secondRegion`
Second Postcode	Supporter’s Secondary Postal Code	200	`supporter.secondPostcode`
Second Country	Supporter’s Secondary Country	500	`supporter.secondCountry`
Second phone number	Supporter’s mobile phone number. For use with SMS, must be in e.164 format which includes country code.	200	`supporter.phoneNumber2`
Email Address 2	Secondary Email Address (not the unique identifier)	500	supporter.emailAddress2
Billing Address 1	Donor’s Credit Card Billing Address	1000	`supporter.billingAddress1`
Billing Address 2	Donor’s Credit Card Billing Apt, Floor, Suite, Etc.	1000	`supporter.billingAddress2`
Billing City	Donor’s Credit Card Billing City	500	`supporter.billingCity`
Billing Region	Donor’s Credit Card Billing State, Province, etc.	500	`supporter.billingRegion`
Billing Postcode	Donor’s Credit Card Billing Postal Code	200	`supporter.billingPostcode`
Billing Country	Donor’s Credit Card Billing Country	500	`supporter.billingCountry`
Supporter Suffix	Supporter’s Suffix	50	`supporter.suffix`
Supporter Organization	Supporter’s Organization Name	500	`supporter.organization`
Supporter Language	Supporter’s Preferred Language. (This is nothing to do with the locale functionality – it will just store what is submitted in the field.)	200	`supporter.language`
Supporter Chapter	Chapter that Supporter belongs to	500	`supporter.chapter`
Supporter Birthday	Date of Constituent’s Birth The birthday date must be formatted YYYY-MM-DD	20	`supporter.dateOfBirth`
Shipping Title	For Premium donation pages, the title the shipping should be sent to	50	`transaction.shiptitle`
Shipping First Name	For Premium donation pages, the first name the shipping should be sent to	100	`transaction.shipfname`
Shipping Last Name	For Premium donation pages, the last name the shipping should be sent to	100	`transaction.shiplname`
Shipping Email Address	For Premium donation pages, the email address of the shipping	100	`transaction.shipemail`
Shipping Address 1	For Premium donation pages, the first line of the shipping address	200	`transaction.shipadd1`
Shipping Address 2	For Premium donation pages, the second line of the shipping address	200	`transaction.shipadd2`
Shipping City	For Premium donation pages, the town/city of the shipping address	100	`transaction.shipcity`
Shipping Region	For Premium donation pages, the region of the shipping address	100	`transaction.shipregion`
Shipping Postcode	For Premium donation pages, the postcode of the shipping address	50	`transaction.shippostcode`
Shipping Country	For Premium donation pages, the country of the shipping address	100	`transaction.shipcountry`
Shipping Notes	For Premium donation pages, any notes on the shipping	2000	`transaction.shipnotes`
Shipping Enabled	For Premium donation pages, whether the shipping address is different to the donor address (Y or N)	1	`transaction.shipenabled`
Other 1	Client-defined transaction field (fundraising pages only)	500	`transaction.othamt1`
Other 2	Client-defined transaction field (fundraising pages only)	500	`transaction.othamt2`
Other 3	Client-defined transaction field (fundraising pages only)	500	`transaction.othamt3`
Other 4	Client-defined transaction field (fundraising pages only)	500	`transaction.othamt4`

Additional ways of capturing data

In additional to tagged fields in the account data structure, there are also additional ways of capturing data for a supporter or transaction.

Field

Description

Character Limit

URL Parameter (case sensitive)

Tracking parameters

Value added as a URL parameter and is stored with the transaction

100

ea.tracking.id

External reference fields 1 - 5

Values added as a URL parameters (typically used to capture UTMs) and stored with the transaction

100

UTMs

Non UTMs

utm_source

utm_medium

utm_campaign

utm_content

utm_term

en_txn1

en_txn2

en_txn3

en_txn4

en_txn5

External reference fields 6 - 10

Values added in the page admin settings or as URL parameters and stored with the transaction

100

en_txn6

en_txn7

en_txn8

en_txn9

en_txn10

Origin source

Value added in the page admin settings or as a URL parameter and stored on the supporter record to capture their originating action.

100

en_og_source