FIM
Fundraising In Memoriam#
Occurence: The supporter selected to make a gift as an 'In Memoriam' donation on a page.
Key Data: The transaction holds the specific 'In Memoriam' details relating to a donation. While the campaign data indicates whether the gift is single or recurring, actual details about the donation processing (such as recurring schedule, if applicable) should be referred to the associated fundraising transaction. Depending on what has been included for capture on the page, the columns for 'Campaign Data 8' to 'Campaign Data 20' contain data populated from the tagged supporter fields.
Reconciling payments#
While amounts are also present in this transaction type, they should not be used for reconciliation purposes. This gift type will always have a corresponding 'FCS' or 'FCR' transaction associated with it, so the amount processed as a donation would be reflected there. The transaction identifiers can be used to link the In Memoriam dedication to the gift.
Export file columns#
Account ID#
Identifies the subaccount this item belongs to
Example: 94
Supporter ID#
The unique numerical database identifier for a supporter.
Example: 212200
Default: 0
Supporter Email#
The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated.
<= 500 characters
Example: otto.nv@example.com
Date Created#
The date a supporter was created. [ISO 8601 format date]
Example: 2024-12-01
Date Modified#
The date a supporter was last modified. [ISO 8601 format date]
Example: 2024-12-01
Campaign Number#
A unique database identifier used to refer to a page, particularly in transactional data. Where records in transactional data originate outside of a page structure, for example as a result of dashboard actions or imports, this will hold a value of 0. Default: 0
Example: 10122
Campaign Type#
FIM
Campaign ID#
The internal reference name given to a page.
<= 160 characters
Campaign Status#
The status of this transaction, as reported by the designated payment gateway.
Occurs as either:
success The transaction was successfully processed by the payment gateway.
reject The transaction was rejected by the payment gateway.
refund The transaction has been marked as refunded.
Example: success
Campaign Data 1#
The internal database identifier assigned to a fundraising transaction.
Example: 4913255
Campaign Data 2#
The transaction identifier as provided by a payment gateway. If the current transaction is a refund, then this identifier points back to the transaction being refunded. The specific formatting of the identifier will be dependent on the gateway.
Example: ND8390T284740397745210972__cus_O20rrZCTq8iTpw__ch_3NFwqEHh8CrK50QS1uUEXjck
Campaign Data 3#
No output for this transaction type.
Campaign Data 4#
An amount presented as a decimal number without any currency symbols. This amount may be omitted for pagetypes where the amount to be processed by a payment gateway needs to be calculated, for example when purchasing tickets for events or certain types of symbolic gifts.
Example: 5.0
Campaign Data 5#
The ISO 4217 code of the currency used for this transaction. When processing payments, it is important to note that currency support is gateway dependent, so be sure to check with your designated payment gateway that the selected currency is supported and has been enabled for your account.
Example: GBP
Campaign Data 6#
Passed as a value or determined by a payment gateway, this describes the payment type to use for the transaction. Valid types may vary depending on the payment gateway used. Some payment types, e.g CASH, CHECK or WIRE may be used to indicate offline donation, or to process 'free' items. Such donations will not be possible to reconcile with an external payment gateway. In output, the prefix TEST: indicates a transaction carried out in a DEMO mode. These transactions should also not be considered for reconciliation purposes. The prefix digitalwallet: is added if the payment was made using a digital wallet integration.
<= 50 characters
Allowed values:
Venmo
cartes_bancaires
Master
card
American Express
AMEX-SSL
diners
Discover
DI
Visa electron
JCB
DELTA
MC
ECMC-SSL
VI
MASTERCARD
Visa
VISA
VISA-SSL
AMEX
AMX
unionpay
discover
AX
CASH
CHECK
WIRE
wire
eCheck
en_bank
unknown
Bank
BANK
Checking
Savings
EC
EFT
PayPal
DDT
ACHEFT
ACH
ach
BACS
SEPA
bacs_debit
sepa_debit
Direct Debit
DAF
refund
Example: VISA
Campaign Data 7#
The frequency for this transaction, which can be a one-off payment or part of a recurring schedule.
Occurs as either:
S The payment was made as a one-off (single).
R The payment was set up according to a recurring schedule.
Campaign Data 8#
Indicates if the In Memoriam Gift should be specially recognised.
<= 1 characters
Allowed values:
Y
N
Example: Y
Campaign Data 9#
Specific choices of tribute options for an In Memoriam Gift.
<= 400 characters
Example: In memory of
Campaign Data 10#
The reason the In Memoriam Gift is being made.
<= 4000 characters
Example: Tom was such a crucial member of our local community, and left such an impression on everyone he met.
Campaign Data 11#
The name of the person in whose Honor the In Memoriam Gift is made.
<= 400 characters
Example: Major Tom
Campaign Data 12#
Name of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 13#
Email address of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 14#
Address line 1 of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 15#
Address line 2 of the person being informed of an In Memoriam Gift - floor, apartment, suite, etc.
<= 400 characters
Campaign Data 16#
City of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 17#
Region, State/Province of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 18#
Postcode of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 19#
Country of the person being informed of an In Memoriam Gift.
<= 400 characters
Campaign Data 20#
Where (the target or purpose) the donor specified that they want their gift to be used.
<= 255 characters
Campaign Data 21#
Other 1: A client defined tagged field which can be used to store any additional data that may relate to the current transaction.
<= 500 characters
Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.
Campaign Data 22#
Other 2: A client defined tagged field which can be used to store any additional data that may relate to the current transaction.
<= 500 characters
Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.
Campaign Data 23#
Other 3: A client defined tagged field which can be used to store any additional data that may relate to the current transaction.
<= 500 characters
Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.
Campaign Data 24#
Other 4: A client defined tagged field which can be used to store any additional data that may relate to the current transaction.
<= 500 characters
Example: Text containing some information that could prove useful when we handle this transaction, for example additional notes from a supporter directly relating to this particular donation.
Campaign Data 25#
Any additional comments submitted by the user to accompany this transaction.
<= 4000 characters
Example: I suffer from this illness, and would be happy to share my story if it could help.
Campaign Data 26#
Amount in USD if available - use for reporting only - converted at the time of transaction
Example: 1.3
Campaign Data 27#
Amount in GBP if available - use for reporting only - converted at the time of transaction
Example: 1.0
Campaign Data 28#
Amount in EUR if available - use for reporting only - converted at the time of transaction
Example: 1.19
Campaign Data 29#
Amount in CAD if available - use for reporting only - converted at the time of transaction
Example: 1.77
Campaign Data 30#
Amount in AUD if available - use for reporting only - converted at the time of transaction
Example: 1.91
Campaign Data 31#
The database identifier of a supporter who has been identified as the referrer for this transaction
Example: 5348788
Campaign Data 32#
Details about the user agent used when submitting the content. The string consists of key/value pairs that are separated by a ~ (tilde) character.
mobile: N or Y depending on whether the user agent identifies as a mobile device. tablet: N or Y depending on whether the user agent identifies as a type of device classed as a 'tablet'. device: The manufacturer of the type of device used by the user agent. os: The underlying operating system of a user agent. browser: The type of web-browser that was used.
Example: mobile:N~tablet:N~device:APPLE~os:Mac OS X~browser:Firefox 11
Campaign Data 33#
A URL identified as the referral origin for this transaction
Example: https://example.com/page/12272/donate/1
Campaign Data 34#
Used to note the origin of incoming page traffic, and is typically passed in links to pages using the query parameter ea.tracking.id
<= 300 characters
Example: linkshare
Campaign Data 35#
An appeal code assigned to this submission.
The code can be considered transactional as it is typically submitted as part of a page submission and associated with the page transaction, however the 'latest' appeal code applied to any supporter submission is also held on the supporter's record.
<= 300 characters
Example: EOY
External Reference 1#
When used outside of API page processing, this field may be populated using the URL parameters utm_source or by the generic parameter en_txn1. Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 2#
When used outside of API page processing, this field may be populated using the URL parameters utm_medium or by the generic parameter en_txn2. Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 3#
When used outside of API page processing, this field may be populated using the URL parameters utm_campaign or by the generic parameter en_txn3. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 4#
When used outside of API page processing, this field may be populated using the URL parameters utm_content or by the generic parameter en_txn4. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 5#
When used outside of API page processing, this field may be populated using the URL parameters utm_term or by the generic parameter en_txn5. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 6#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn6. When added as a page parameter, the field is referred to as Campaign Reference 1 in the dashboard settings.
If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 7#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn7. When added as a page parameter, the field is referred to as Campaign Reference 2 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 8#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn8. When added as a page parameter, the field is referred to as Campaign Reference 3 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 9#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn9. When added as a page parameter, the field is referred to as Campaign Reference 4 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
External Reference 10#
When used outside of API page processing, this field may also be populated by a user-defined page property [Page > Admin > Campaign References], or by the url query parameter en_txn10. When added as a page parameter, the field is referred to as Campaign Reference 5 in the dashboard settings. If a value is presented in both places, the url query parameter will take precedence. Note: Content will be automatically truncated if the maximum length is exceeded, and the last three characters replaced by '...' to indicate that a string has been truncated.
<= 100 characters
Email Address#
The primary email address of a supporter, which will typically be used as the basis for identifying a unique supporter to which any transactions will be associated.
<= 500 characters
Example: otto.nv@example.com
Title#
A supporter's title to be used in salutations
<= 50 characters
Example: Dr
First Name#
A supporter's first name
<= 500 characters
Example: Otto
Middle Name#
A supporter's middle name
<= 500 characters
Example: Niemand
Last Name#
A supporter's last name
<= 500 characters
Example: Normalverbraucher
Address 1#
The first line of the supporter's address
<= 1000 characters
Address 2#
The second line of the supporter's address
<= 1000 characters
Address 3#
The third line of the supporter's address
<= 1000 characters
City#
The city in a supporter's address
<= 500 characters
Example: Musterstadt
Region#
The supporter's region, state, county, province or similar
<= 500 characters
Example: Musterregion
Country#
The supporter's country
<= 500 characters
Example: DE
Phone Number#
The primary phone number for a supporter
<= 200 characters
Example: +49 4066969123