Troubleshoot your widget

1. Check the snippet actually installed on that website page. Set its data-success-url and copy the updated code after any change.
2. Use that page's destination explicitly. The language attributes do not change the URL.
3. Use a path beginning with / or a URL with the same protocol, domain and port. Check the exact spelling, including www, and open the destination directly to confirm it exists.
4. Wait for a confirmed booking, then save or skip any optional questions. A pending payment or failed answer save does not redirect.
5. Use the website embed. Quick preview, direct booking links and fallback links do not use your website's confirmation-page setting.

1. Confirm online booking is enabled and bookings are not paused.
2. Confirm at least one tour is ready, published, and has upcoming availability.
3. Use the current snippet and public widget key from Ways to sell.
4. Allow JavaScript and give the Widget at least 320 CSS pixels of width.
5. Try the direct link. If it works, check the embed installation. If you still need help, contact support with the full page address.

Preview can show saved drafts before setup is complete. Finish the blocking notices for your tours and enable online booking. For paid tours, check Stripe readiness and payment approval.

Confirm the tour is published, open, and not archived. Check its season dates, weekday and start time, one-date exceptions, booking horizon, sales-open setting, cutoff, capacity, shared capacity, language filter, and schedule-preview warnings. Save your changes. On a language-specific page, a departure must match the selected language to appear.

Edit the Booking Option's ticket categories. Clear Required for the optional category, set its minimum to 0, and save your changes. Required means every booking must contain at least one ticket of that exact type.

Confirm the rate period covers the selected date and weekday. Check ticket prices, currency, traveler quantities, extras, promotion scope, and included or added taxes and fees. Save your changes, then begin a new Widget selection so TourDash creates a fresh quote.

Free bookings do not wait for Stripe. Paid bookings appear after successful payment is confirmed and the order is finalized. Do not ask the traveler to pay again. Use Check payment status, inspect the order in Payments, and compare the amount and time in Stripe. If Stripe says success but no Booking exists, contact support with the public reference.

Confirmation normally completes within seconds. Keep the page open and select Check payment status when it appears. Never submit a second payment. If Stripe shows a successful charge but TourDash remains pending, send support the public reference, time, amount, and currency. Do not send card details.

Connected is not always Ready. In the matching Payments card, confirm setup is complete and charges and payouts are enabled. Resolve any Stripe verification request, then check whether online booking is enabled and payment approval is complete.

Make sure the TourDash script loads once and uses popup or assistant mode. Add data-tourdash-open to the button and place it before the script. Only the first matching button is connected. In assistant mode, data-show-launcher="false" hides the separate floating button. First test the generated snippet unchanged before adding custom code.