We are happy to announce our latest TripBuilder release. Please see these release notes for the most significant changes. Let us know if you have any questions, feedback, or ideas for features or improvements!

This update introduces a new configurable setting for the "Create Own Tour" section in Discovery, allowing users to set a different default for the “Search Flights” option. Previously, the “Search Flights” defaulted to "Roundtrip," requiring agents to switch to "Multi-City" manually.

With this improvement, users can now select "Multi-City" as the default option, streamlining the search process for agents preferring multi-city itineraries.

The new setting is available under TripBuilder settings.

We have fixed an issue in the Picture Library where users could not crop uploaded images. The functionality is now fully operational, allowing users to select and crop images as expected. Additionally, improvements were made to the upload flow to ensure that newly uploaded images appear immediately with the correct metadata, addressing confusion around missing or untitled images.

We have updated our webhook system to address a gap in event notifications when manual itinerary-level actions change component statuses from “on request” to “booked”'.
​

The webhook triggers automatically when the itinerary status changes to “booking completed” due to an itinerary-level manual action. This improvement ensures the webhook logic includes status changes resulting from manual actions.

Find more information here.

We have enhanced our payment webhook events by including a Transaction ID, improving the ability of API users to track and identify specific payment transactions. Previously, the absence of a Transaction ID made it difficult to discern changes in payment transactions.

Now, every payment-related webhook event - e.g. PaymentAdded, PaymentUpdated, PaymentDeleted, RefundAdded, RefundUpdated, and RefundDeleted - includes this information. This enhancement allows seamless updates from Custom Checkout to, e.g. a midoffice platform, ensuring all transactions are accurately tracked.

Find more information here.

All data shown in this chapter is sample data for the purpose of this documentation.

To further complete the analytics through the funnel, we have added the “checkout started” statistics to the Booking Performance of Advanced Analytics. An itinerary/booking is considered to have passed this funnel step when the user has entered the checkout process at least once.

A funnel visualisation has been added to the dashboard “Booking KPIs” of TripBuilder Analytics Advanced. Two variations exist: the first shows the conversion rate compared to the amount of initially created itineraries (left visualisation in screenshot), the second funnel visualisation shows the conversion between the funnel steps (right visualisation in screenshot).

Find more information here.

The “Inventory” dashboard was extended with new filtering capabilities applied to templates:

Further, the “Inventory” dashboard itself has been restructured. Instead of one big tab, there are three tabs: KPIs, Templates + Modules + NBC, and Products. This will enable the addition of more detailed visualisations for the different entities in a scalable way, with better organisation.

Find more information here.

We have introduced the notion of “User Segment” and enhanced the Booking Performance and the Booking KPIs dashboard of TripBuilder Advanced Analytics. Both dashboards now come with a “User Segment” filter. Additionally, the Booking KPI dashboard offers a direct comparison of the different segments in the form of various KPIs.

The user segment is derived from the user who performs a booking or the user who created the itinerary for itineraries that are not booked yet. If the user is unknown, an itinerary/booking is always considered from the “Consumer” segment.

Find more information here.

Nezasa follows the “Now, Next, Later” framework to outline the development trajectory of TripBuilder, enhancing transparency around our progress. We share these insights with our customers in each new release in the TripBuilder - Now, Next, Later article.