Creating & Managing Experiences

Events

Canopy > Events > Events

Selecting an event is required to purchase an experience, which means events must be configured in Canopy.  When configuring an event in Canopy, to be used in the marketplace, the following is required: 

• Event Name
• Event date, time, & timezone
• A custom attribute needs to be added to enable the event in the marketplace
  • The label should be marketplace
  • And the value should be true
• No other fields are needed to sell an experience for this event
• Separate experiences by OrderNext Instance
  • When multiple OrderNext instances are used by the same Canopy Organization an additional custom attribute can be added to the event to control which experiences show in which OrderNext instance
  • The label for this custom attribute is instance
  • And the value should be the instance name (i.e. utahjazz)
  • For example:
    • Event A can have an instance of example1
    • Event B can have an instance of example2
    • Any experiences configured with event A will only show on example1.ordernext.com
    • Any experiences configured with event B will only show on example2.ordernext.com
  • If no instance is defined then the experiences will show on all instances

Merchant

As of September 2021, merchants are not used for payment processing with Shift4 i4Go but until further notice, a value (any string) needs to be provided in order to configure an experience.

Canopy > Marketplace > Merchants

A merchant is where the money from credit card purchases of marketplace experiences will settle. Before setting up any experiences, please make sure a merchant exists otherwise you will not be able to save the experience you just configured. 

If this hasn’t been configured for you or you are unsure of what it should be, ask VenueNext by emailing help@venuenext.com. 

Categories

Canopy > Marketplace > Categories

Categories is a way to group experiences in the app.  An experience must belong to at least 1 category for it to display in the app.  Before setting up any experiences, please make sure a category exists otherwise you will not be able to save the experience you just configured. 

When defining a category, the following is required: 

• Category Name
• Icon
• Icons were used in the legacy app, but in the SDK & Web these are actually tout images
• The dimensions for the uploaded image should be 375 x 180
• The display on homepage, display on marketplace homepage, & display in client toggles can be ignored
• (NEW!) Merchant Token - as of September 2021, this is the Shift4 i4Go merchant token that will be used for any experiences purchased in the specific category

Configuring a Global Item

Canopy > Marketplace > Global Items > Create Global Item

Creating a global item is the first step to defining the details of the experience that you want to sell.  Being able to customize price & inventory per event will come after this step. Here is each field when creating a global item explained:

• Item Type - only select Venue Experience
• Redemption Type - see the Redemption Types section for a detailed explanation of each option
• Name - name of the experience (i.e. Locker Room Visit)
• Description - long description displayed when viewing the details of a specific experience
• Short Description (optional) - shorter description displayed when viewing the list of experiences
• Email alert recipients (optional) - comma separated list of operations personnel emails that should be alerted when there are users who have purchased experiences to fulfill
• Metadata - see the Metadata section for a detailed explanation of each option
• Categories - category that the experience should be grouped with
• Item Attributes
  • Single event - this experience will only apply to one upcoming event.
  • All Events - this experience will be offered at every event configured
  • Maximum quantity a single user can purchase per event (this is not per order)
  • OrderNext web will currently not respect any item purchase limit that is configured
  • If the selected item availability is single event then this is a date/ time selector
  • If the selected item availability is all events then this is the number of hours after the event start time that the experience expires
  • If the selected item availability is single event then this is a date/ time selector
  • If the selected item availability is all events then this is the number of hours relative to the event start time that the experience can be redeemed
• Merchant
• Item Availability
• Item Purchase Limit (optional)
• Event - only an option if the selected Item Availability is single event
• Inventory - amount to sell
• Expiration Date
• Redemption Starts At
• Time period item is still visible - no longer used, please ignore
• Transferable - dictates whether a customer can transfer the experience to someone else via email address
• Refundable - dictates whether a customer can change their mind and submit a refund for a purchased experience, if it hasn’t yet expired or been redeemed.  Note that as a venue operator, you can refund an experience from Canopy, regardless of this setting.
• Sale Attributes
  • If use the same start date for all sales is toggled off then the start time entered in the number of hours relative to the event start time
  • If use the same start date for all sales is toggled on then a specific date & time can be entered
• Group - see the Exclusivity section for a detailed explanation of each option
• Price - price that the experience is to be sold for; $0 will display as free
• Use the same start date for all sales - controls the sale start time input
• Sale Start Time
• Sale End time - hours relative to the event start time that the sale ends
• Images - after creating the global item with the above data, then you will be able to upload the following images: 
  • This image will display on the countdown timer card
  • The text defined here will display on the experience card before it is redeemed & the email receipt that the purchaser receives; if not instruction text is defined then the system default is automatically used
• Detail - this is the image for the experience; dimensions for the uploaded image should be 750x492
• Instruction
• All other images can be ignored

Redemption Types

The selected redemption type will vary based on the experience being offered and how it will operationally be supported.  I.e a Birthday Big Board message will not need to be redeemed so No Scan would be selected, but a Mascot Visit will need to be redeemed when the mascot arrives at the fan's seat so Countdown timer would be used. 

• No Scan - no redemption button will be displayed to the purchaser on their digital receipt
• Countdown Timer
  • When selected as the redemption type then an additional input will be required, which is the countdown duration in seconds
  • When available to be redeemed and the redeem button is selected, then a countdown will display, starting at the configured duration; tapping this countdown will change the color to prevent screen recording fraud
• QR / Barcode
  • When selected the purchaser will see a QR code on their digital receipt
  • The values used in the QR code come from what is uploaded into Canopy
  • To upload QR code values into Canopy after the Global Item for the experience is created go to
    • Marketplace > Global Items
    • Click the name of the experience
    • Click view QR / Bar Codes
    • Click Create QR / Bar Code to create one at a time
    • Or click Bulk Upload to enter in many comma-separated code values
  • Each experience purchased will take from the uploaded code values
  • Be sure to upload at least as many codes as inventory allocated, otherwise, the user will see an error when trying to purchase an experience with no available codes
  • Only unused codes will display in the list view
  • The code used for each purchase will be included in the Marketplace User Items export
• Single Scan - not currently supported by the SDK or Web
• Unlimited Scan - not currently supported by the SDK or Web

Metadata

Metadata is a way to collect additional information about the purchaser needed to fulfill the experience. I.e. if a Mascot Visit is being sold then the operations team will need to know the seat location to send the Mascot.  Or if a Birthday Big Board message is being sold then the message to display will need to be defined. 

There are three types of metadata currently supported.  One of them or all of them can be used at the same time. 

• Text String
• Prompts the purchaser to enter free text
• The Name is what the user will see as the text input label (i.e. Enter your Message)
• Required is no longer relevant, it is always required
• Seat Picker
• Prompts the purchaser to enter their seat location
• The seat picker will not be used for this; section/ row/ seat are free text inputs
• The Name is what the user will see as the text input label (i.e. Enter your seat)
• Age
• Prompts the purchaser to enter their birthday
• The Name is what the user will see as the text input label (i.e. Enter your birthday)
• Restrictions based on the purchasers age can optionally be added

Exclusivity

Marketplace experiences can be configured to be exclusive to certain user groups.  All users will see all on sale experiences, but only those in the configured group will be able to complete the purchase. 

• All - aka anyone, so not exclusive
  
  
• Season Ticket Holder
  • No longer used as of 2021
    
    
• Preferred Card Holder
  • Only users that have saved a credit card that matches to a list of preferred credit card holder BIN numbers will be able to purchase
  • Contact help@venuenext.com to have your preferred credit card BIN numbers uploaded and the name of the preferred credit card (i.e. Mastercard)
    
    
• Geo-exclusive
  • When selecting "Geo exclusive" as the group for a marketplace experience 3 pieces of "Metadatum" must be added for it to work
  • The first two are the latitude & longitude of the location that the marketplace experience is exclusive to
  • The third is the distance/radius for which the user must be to be eligible for the geo exclusive experience, this is inputted in meters
  • Without all 3 pieces of metadatum, the geo exclusive experience will not be purchasable by anyone
  • Users are still required to share their location otherwise, they will not be eligible to purchase the experience
    
    
    
    
• Tiered exclusive
  • Leverages the tiers, that are pre-configured, for exclusivity
  • When selected, the tier can be selected using the metadata controls
  • Metadata will be ignored for all other types of exclusivity
  • Hiding Exclusive Experiences
    • By default, exclusive experiences have always been visible to all users, but only purchasable by users in the configured tier
    • A new configuration is now available that will hide exclusive experiences from users not in the configured tier
    • To enable this add an additional metadata call Visible by Affiliation and set it to true
    • Setting it to false (or not adding it all) will keep the default behavior where everyone can see the experience, but it will only be purchasable by users in the configured tier

Modify Event Price & Inventory

Canopy > Marketplace > Global Items > Select the name of the experience to modify

After a global item is created then the price, inventory, and other attributes can be modified per event.  I.e. for a popular game the price and available inventory can be adjusted. To do this in Canopy go to marketplace > global items > and then click the name of the experience.  Then you will see a list of all events the experience is configured for. Selecting the event you want to modify will allow you to modify all of the item & sale attributes for that specific event.

Adding Experiences to New Events

In the scenario where an event is created in Canopy after the global item is created, you will need to setup the experience for that event. 

• To do this in Canopy go to marketplace > global items > and then click the name of the experience.
• Scroll down and click ‘Show Items by Event’ and then click create item for the event you want to create it for.  Then you will be able to define the item & sale attributes.