The following page contains frequently asked questions for our Trip Element
It is not possible to add custom disclaimers for our Trip Element solution. We recommend placing the disclaimers above or below the iframe that loads the Trip Element if you require custom information alongside our solution.
We do not support this functionality but do highly recommend partners discuss this with your Partner Success representative. We would love to know the business and use the case to review and help improve the product for the future.
Sherpa° supports domestic restrictions for Australia, Canada and the United States only.
If there are multiple scripts the page is trying to load, delaying Sherpa°'s widget load, we suggest attempting to load the trip element asynchronously with instructions located here. If you still experience delays for the Trip Element loading, please contact our technical support team to review further and triage the issue.
Sherpa° recommends the use of the following placement values as custom values won't appear in dashboards.
Placement | Description |
---|---|
homePage | Home Page |
discovery | Generic pre-booking marketing page |
mmb | Manage My Booking |
search | Trip search |
bookingConfirmation | Booking Confirmation |
destinationPage | dedicated marketing page for a destination |
The trip element SDK will display a 'warning' message on the console that can be ignored.
Certain airports are not on your list. What is the process to get these airports added in for us? We highly suggest passing country code instead of airport code where possible. The end-users will receive the exact travel requirements. If the passing of country code does not meet your business requirements, we add airports to our database on a bi-monthly basis. If there is a list of airports your traveller's visit that isn't supported by sherpa°, please reach out to your account lead with a list and the airport three-letter codes with some traffic data for review by our product team.