Account data structure tagged field list
The Account Data Structure contains a list of fields, some of which are ‘tagged’.
What is a tagged data field?
These are fields containing certain pre-defined types of data in the database. These data fields are considered ‘tagged’ and so we know exactly where this data lives and how this data is to be used.
For example, when your ‘Post code’ field is tagged as ‘Postcode’, then our email-to-target tools know to use this field to lookup the targets for the action. Or, the field that is tagged as Email Address will be used to uniquely identify the supporter, and is also where thank you emails are sent to. There are several other kinds of tagged fields.
The database also contains ‘untagged’ data fields, which are essentially empty placeholders that you can use to create and define your own field types, relating to your organizations’ particular needs and goals. For example, you might want to store your own offline database ID, 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.
Which Tagged Fields Are Available?
The table below provides a description of each of the pre-assigned, tagged fields in the database.
Field | Description | Character Limit |
|---|---|---|
Title | Constituent’s Name Prefix | 50 |
First Name | Constituent’s First Name Value | 500 |
Middle Name | Constituent’s Middle Name Value | 500 |
Last Name | Constituent’s Last Name Value | 500 |
Address 1 | Constituent’s Street Address | 1000 |
Address 2 | Constituent’s Apt, Floor, Suite, Etc. | 1000 |
Address 3 | Additional Address Information | 1000 |
City | Constituent’s City | 500 |
Region | Constituent’s State, Province, etc. | 500 |
Email Address | Constituent’s Primary Email (unique identifier in the software) | 500 |
Postcode | Constituent’s Postal Code | 200 |
Country | Constituent’s Country | 500 |
Phone Number | Constituent’s Phone Number | 200 |
Donation Amount | Amount of the Donation | Numeric value |
Payment Type | Type of Credit Card, PayPal, or Bank Account | 50 |
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 |
Credit Card Expiration Date | Expiration of Credit Card Being Used to Donate | 8 |
Credit Card Verification Value | Verification Code of Credit Card Being Used to Donate | 4 |
Card Holder Name | Name of Owner of Credit Card Being Used to Donate | 500 |
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 |
Bank Routing Transit Number | Routing Number of Bank Hosting Account from which Donation Is Made | 20 |
Bank Account Type | Type of Bank Account (Checking/Savings) from which Donation is Made | 30 |
Bank Name | Name of Bank Hosting Account from which Donation is Made | 500 |
Issue Number | Issue Number of Credit Card Being Used to Donate (not used in USA / UK) |
|
Payment Currency | Type of Currency being Used to Donate | 3 |
Recurring Payment | Flag to Indicate if Donation is Recurring (‘Y’) | 1 |
Recurring Day | Day the Next Recurring Payment Should Occur | 1 to 30 |
Recurring Start Date | Date Recurring Donation Payments Began The recurring start date must be formatted YYYY-MM-DD | 20 |
Recurring End Date | Date Recurring Donation Payments Will Stop The recurring end date must be formatted DD/MM/YYYY | 20 |
Recurring Count | Number of Recurring Donation Payments to Process | 500 |
Recurring Frequency | How Often Recurring Donation Payments Occur | 10 |
Recurring Period | Length of Time Between Recurring Donation Payments | Numeric value |
Tax Deductible | Flag to Indicate if Donation is Tax Deductible (‘Y’) (you can use this for Gift Aid) | 1 |
Pledge Amount | Amount of Donation Being Pledged to a Specific Category | Numeric value |
Recognize Gift | Flag to Indicate if Donor / Donation Should be Specially Recognized (‘Y’) | 1 |
Additional Comments | Additional Comments Related to Transaction / E-cards personalized message field | 4000 |
Anonymous Donor | Flag to Indicate if Donation is Being Made Anonymously (‘Y’) | 10 |
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 |
Inform Email | Email of Person Being Informed of In Memoriam Gift | 400 |
Inform Name | Name of Person Being Informed of In Memoriam Gift | 400 |
Inform Address 1 | Address of Person Being Informed of In Memoriam Gift | 400 |
Inform Address 2 | Address 2 of Person Being Informed of In Memoriam Gift | 400 |
Inform City | City of Person Being Informed of In Memoriam Gift | 400 |
Inform Region | State/Province of Person Being Informed of In Memoriam Gift | 400 |
Inform Postcode | Postcode of Person Being Informed of In Memoriam Gift | 400 |
Inform Country | Country of Person Being Informed of In Memoriam Gift | 400 |
Honoree Name | Name of Person in Whose Honor the In Memoriam Gift is Made | 400 |
Gift Reason | The Reason that In Memoriam Gift is Made | 4000 |
Tribute Options | Choices of Tribute Gifts | 400 |
END IN MEMORIAM FIELDS |
|
|
Direct Gift | Where (Target / Purpose) the Donor Wants to Direct Their Gift to be Used | 255 |
Appeal Code | Extra Field Used for Tracking Data About One Specific Transaction Page | 300 |
Second Address 1 | Constituent’s Secondary Address | 1000 |
Second Address 2 | Constituent’s Secondary Apt, Floor, Suite, Etc. | 1000 |
Second City | Constituent’s Secondary City | 500 |
Second Region | Constituent’s Secondary State, Province, Etc. | 500 |
Second Postcode | Constituent’s Secondary Postal Code | 200 |
Second Country | Constituent’s Secondary Country | 500 |
Second phone number | Consituent’s Secondary Phone Number. If using SMS in automations (beta) this is used to store the supporter’s mobile phone number |
|
Email Address 2 | Secondary Email Address (not the unique identifier) | 500 |
Phone Number 2 | Secondary Phone Number | 200 |
Billing Address 1 | Donor’s Credit Card Billing Address | 1000 |
Billing Address 2 | Donor’s Credit Card Billing Apt, Floor, Suite, Etc. | 1000 |
Billing City | Donor’s Credit Card Billing City | 500 |
Billing Region | Donor’s Credit Card Billing State, Province, etc. | 500 |
Billing Postcode | Donor’s Credit Card Billing Postal Code | 200 |
Billing Country | Donor’s Credit Card Billing Country | 500 |
Supporter Suffix | Constituent’s Suffix | 50 |
Supporter Organization | Constituent’s Organization Name | 500 |
Supporter Language | Constituent’s Preferred Language. (This is nothing to do with the locale functionality – it will just store what is submitted in the field.) | 200 |
Supporter Chapter | Chapter that Constituent’s Belongs To | 500 |
Supporter Birthday | Date of Constituent’s Birth The birthday date must be formatted YYYY-MM-DD | 20 |
Shipping Title | For Premium donation pages, the title the shipping should be sent to | 50 |
Shipping First Name | For Premium donation pages, the first name the shipping should be sent to | 100 |
Shipping Last Name | For Premium donation pages, the last name the shipping should be sent to | 100 |
Shipping Email Address | For Premium donation pages, the email address of the shipping | 100 |
Shipping Address 1 | For Premium donation pages, the first line of the shipping address | 20 |
Shipping Address 2 | For Premium donation pages, the second line of the shipping address | 200 |
Shipping City | For Premium donation pages, the town/city of the shipping address | 100 |
Shipping Region | For Premium donation pages, the region of the shipping address | 100 |
Shipping Postcode | For Premium donation pages, the postcode of the shipping address | 50 |
Shipping Country | For Premium donation pages, the country of the shipping address | 100 |
Shipping Notes | For Premium donation pages, any notes on the shipping | 2000 |
Shipping Enabled | For Premium donation pages, whether the shipping address is different to the donor address (Y or N) | 1 |
Which Un-Tagged Fields Are Available?
You can add untagged fields to your database structure as required.
Your database also allows you to create four placeholder fields, enabling you to create and define your own data types as needed. These fields need to be created with with the tag ‘Other X’, and are currently only available for use with Fundraising type pages.
Other 1 | Client-Defined Transaction Field | 500 |
Other 2 | Client-Defined Transaction Field | 500 |
Other 3 | Client-Defined Transaction Field | 500 |
Other 4 | Client-Defined Transaction Field | 500 |