Importing Contributors
Updated
by
Jon Doehling
Download the latest import file here
When filling with data, there are a few things to consider.
- You CAN repeat names
- You CAN repeat email addresses (although you shouldnt with Messaging/Express Check-In)
- You CAN repeat phone numbers
- You CANNOT repeat cell phone numbers
- You CANNOT import a bid# that is already in the system
Associations, Bidder Numbers and Groups
Associations are made between two or more Contributors in order to pair them together for:
- Bidding/Buying - such as when couples or members of a household wish to pay and sit together.
- Seating/Grouping - such as when companies or individual sponsors buy a large number of tickets and wish to have the group sit together.
Associations can be made in imports one of two ways:
- By filling in the same Bidder# - when this is found we will assume this is a household and pair them together under the same bidder#.
- By filling in the same Group - here we will pair together members of the group to make seating easier - but will NOT have them share bid#s unless specifically specified in the import.
Column Details
* Denotes a REQUIRED field
Paid | Y/N | Affects the paid status of the Contributor's Admission Ticket as displayed at Check-In. No means they will be required to pay at the door. | ||||||||||||
Bidder# | Number | Highly reccommended you assign a bid# to any [Attending; Patron] Type you are importing, for speed and fidelity. All Attending Patrons must be 3 or 4 digits based on the setting selected in Setup > App Settings > Bid# Digits. All other Patrons must be 5 digits. | ||||||||||||
First Name* | Text | First Name of the Contributor. REQUIRED. | ||||||||||||
Middle Initial | Text | Middle Name or Initial of the Contributor | ||||||||||||
Last Name* | Text | Last Name of the Contributor. REQUIRED. | ||||||||||||
Group | Text | Group Name shared amongst all Attendees that are part of the same reservation. If filled, each Contributor with the same group name will be associated together for easy seating and check-in. HIGHLY RECCOMMENDED for Express Check-In and overall ease of registration and seating. Each row must be spelled identically for the Group to be recognized. | ||||||||||||
Title | Text | Job title for the Contributor. | ||||||||||||
Contributor Type | Text | Seperate additional types with a simcolon and space. Example: Patron; Attending
| ||||||||||||
Contributor Since* | Date | MM/DD/YY format. REQUIRED. | ||||||||||||
Affiliation Type | Text | Must match existing Affiliation Types as found in Setup > Affiliations. Seperate additional types with a simcolon and space. Example: Parent; Alumni | ||||||||||||
Table Number | Number | Table must already exist in Seating, and there must be enough open seats at the table to proceed. | ||||||||||||
Phone# | 10 digits | Home or Business line | ||||||||||||
Address | Text | Home or Business Address, line 1 | ||||||||||||
Address2 | Text | Home or Business Address, line 2 | ||||||||||||
City | Text | Home or Business City | ||||||||||||
State | Text | Home or Business State (abbreviations only) | ||||||||||||
Zip | Text | Home or Business postal code | ||||||||||||
Company | Text | Company or Personal Name, used for Sponsor recognition text. | ||||||||||||
Text | Must be a valid email address. To be used for evebnt related messaging, receipts, and notifications. Can be duplicated, but not reccommended. | |||||||||||||
Notes | Text | Notes for the registration staff to consider at check-in. Such as balance due or special instructions. | ||||||||||||
#of Bidders | Number | Generally 1, but may be adjusted to 2 or more if your list is in a format listing couples instead of individuals. When multiple people share a single contributor record, certain features are limited to one person such as cell phone and email notifications. | ||||||||||||
Cell Phone | 10 digits | Cell Phone number, required for SMS text message notifications. Despite having someones cell phone number in the system, the user MUST opt-in before receiving SMS text notifications, which they can do upon logging in to the mobile bidding app for the first time, or by checking-in at the event. | ||||||||||||
Fax | 10 digits | Fax number | ||||||||||||
Website | URL | Must be a valid URL with http:// or https:// | ||||||||||||
Salutation | Text | Must be one of the following: Mr., Mrs., Ms., Hon., Dr., Ptr., Rev., Sis., Br. | ||||||||||||
Email Opt Out | Y/N | Default is N, but set to Y if the user has explicitly opted-out of email communication from your organization. | ||||||||||||
Anonymous | Y/N | Default is N, but set to Y if the user wishes to remain anonymous. | ||||||||||||
Alternate Key | Text | Unique identifyer for 3rd party software applications. Very useful if needing to track Contributor purchases and payments for import into a 3rd party system post event. | ||||||||||||
Meal Type | Text | Meal must exist in Setup > Meals | ||||||||||||
VIP | Y/N | Used to designate VIP attendees in reporting, seating and event check-in. | ||||||||||||
Ticket Package | Text | Used to assign a ticket package to the attendee. Must match an existing Tickets & Admission or Sponsorship package (with admissions). REQUIRED if planning to use the "Update Guest Names" feature in Messaging, or if importing/associating Groups. |
