Column Description for Bulk Uploading Event Tickets
To bulk create event tickets using QRCodeChimp’s bulk upload feature, start by downloading the sample Excel file and entering your customer details.
Refer to the column descriptions provided to ensure accurate data entry, as each column captures specific event details that will be included in the generated QR codes.
Caution: Please do not modify the column names, change their order, or delete any columns.
Column Name | Description |
---|---|
QR Name* | Enter the desired names for the QR codes you want to create in bulk. Note: This column is required—please do not leave it blank. |
Page-code* | Page Code is a unique identifier in your event ticket’s short URL. Enter AUTO to let the system generate it automatically, or manually enter a unique code (minimum 5 characters, lowercase, using only letters, numbers, or hyphens). For example, entering lily1 creates the short URL https://linko.page/lily1. Note: Do not leave this column empty. If you want the system to generate the Page Code automatically, enter AUTO in the Page-code field. |
Event Customer Name | Enter the name of the customer or client for whom the event ticket is being issued. |
Event Name | Enter the name or title of the event for which the ticket is being issued. |
Event Description | Fill a summary or details about the event, such as its purpose or theme. |
Event Photo | You can either enter the Event photo's short path or copy-paste the URL as detailed below. Option 1: Enter the short path of the profile background image as folder_name/image_name.
|
Other Details Section Note: The details in this section are fully customizable. The default labels are provided as examples, and users can add any event-related information as needed. The 1.Field:[SEQ_NO].key will appear as the label, and the 1.Field:[SEQ_NO].value will appear as the corresponding information for that label. |
|
1.Field:1.key | Add label for event related information, suh as Event Date. |
1.Field:1.value | Add event information corresponding to the label added in key. |
1.Field:2.key | Add label for event related information, suh as Venue. |
1.Field:2.value | Add event information corresponding to the label added in key. |
1.Field:3.key | Add label for event related information, suh as Organizer. |
1.Field:3.value | Add event information corresponding to the label added in key. |
1.Field:4.key | Add label for event related information, suh as Summary. |
1.Field:4.value | Add event information corresponding to the label added in key. |
Contact Us Section Note: The fields for this section are intended to be used to share the event organizer/host contact details. |
|
2.Contact Title | Enter the the title for Contact Us section. |
2.Contact Icon | You can either enter your logo/icon image's short path or copy-paste the URL as detailed below. Option 1: Enter the short path of the logo/icon as folder_name/image_name.
|
Floating Button Text | Enter the Floating Button Text, e.g., 'Save Contact,' or use the default text 'Add to Contact.' |
Contact Info:1.number.title | Enter the label for the contact number. |
Contact Info:1.number.Number | Enter the contact number. |
Contact Info: .email.title | Enter the label for the email address. |
Contact Info: .email.Email | Enter the email address. |
Contact Info: .address.title | Enter the label for the address section. |
Contact Info: .address.Street1 | Enter the street name. |
Contact Info: .address.Street2 | Enter the building name. |
Contact Info: .address.City | Enter the city name. |
Contact Info: .address.State | Enter the state name. |
Contact Info: .address.Country | Enter the country name. |
Contact Info: .address.Zipcode | Enter the zip code. |
Contact Info: .address.Action Button Label | Enter the label for the action button. |
Contact Info: .address.Action Button Link | Enter the Google Map location URL of the address. |
Email on scan | Enter the email id on which you want to get scan alerts. |
Email for ticket sharing | Enter the email id on which ticket shoud be sent. |
Track Precise Location | Enter Yes if you want to track the precise location of the ticket scan, fill No otherwise. |