Skip to main content

Triptease widget not showing

Triptease widget not showing on my booking engine.

N
Written by Niamh Kiely
Updated over a month ago

Triptease widget not showing on my Booking Engine

If you've previously requested the Triptease Widget to be added to your booking engine (BE) but it's not displaying, here are a few steps you can take to troubleshoot the issue:

1. Check the Client ID: When you requested the widget installation, you would have provided a Client ID. Double-check with Triptease to ensure the Client ID you shared is correct.

Also, reach out to [email protected] to confirm that the correct Client ID was entered on the SHR side.

2. Check the API Key: Similarly, you would have provided an API Key at the time of setup. Please verify with Triptease that the API Key is accurate.
Then, email [email protected] to make sure the correct key was implemented by SHR Group.

3. Check if you were on a trial: Triptease often offers a trial period for their widget. If your trial has ended and you haven’t opted to continue with a full subscription, the widget may no longer be active. Reach out to Triptease to confirm your current status.

4. Make sure the widget is set live. Even if SHR Group has added the widget to your BE, it won’t appear unless Triptease has activated it on their end. Contact Triptease to confirm the widget is set live.

5. Check your Direct price vs the OTA price.The widget may not display if the direct booking price is higher than the lowest OTA (Online Travel Agency) price. Ensure your direct rate is the most competitive.

6. Not showing on mobile only. By default, the Triptease Widget is not enabled on mobile. If you’d like it to appear on mobile devices, contact Triptease to enable this feature. Once it's enabled, you or Triptease can ask SHR Group to apply it on mobile.

If you've reviewed all of the above and the widget still isn't appearing, the best next step is to ask Triptease to contact SHR Group directly at [email protected] to investigate further and resolve the issue.

Did this answer your question?