Customizing the Event Widget?
Event managers, venue managers and meeting managers may customize the TripProximity Event Widget for use with any event page, any blog or any enterprise system that powers ticketing and registration for events or lists/aggregates events.
It can be hard coded with a single event’s information, or an organization that has multiple events or that lists/aggregates events can use our dynamic widget. For the dynamic version of the widget, you would pass the variable parameters to us at time of display of the widget, customizing literally hundreds or thousands of pages.
There are several parameters that need to be passed to the event widget to operate correctly. These must be rendered in the web page as JSON data dictionary within an Html script tag like the sample at the bottom of this page.
The widget can be hardcoded with all of this information for your event (such as on an EVENT page on your corporate website). If the widget is being used for a system that has multiple events, you will substitute the %VARIABLE NAMES% with the correct data from your landing page for the event at transaction time.
The following event date parameters govern how the checkin and checkout dates work for hotel, how the pickup and dropoff dates work for car and the arrival and departure dates work for air.
The Event Widget Variables
The event widget variables drive the hotel checkin and checkout dates and also the car rental and air dates.
|eventStart||The starting date of the event||
|eventLength||The number of days of the event||
|Default is 0 for a single day event. A meeting that is one day, but where travel is the next day, this would be set to 1. This can be modified for multi-day events.|
|daysBefore||The number of days before the event that you would prefer that people checkin.||
|This can be modified to 1, which is checking in the day before the event start date, or 2 for two days before|
|daysAfter||The number of days after the event that you would prefer that people checkout||
|For a single day event that goes into the evening, if eventLength is set to 0 and daysAfter is set to 1, the checkout will be the day after the event.|