Below, you will find several example configuration for the Trip Element from real-world integrations. The screenshots shown are illustrations and only updated from time to time.
Reach out to your partner success manager if you require additional examples for your specific use-case.
The following configuration shows how to define the passport of a traveler using the Traveller Model.
The following configuration shows how to define the language to display the Trip Element in one of the supported languages.
This will help make analytics reports clear, allowing our team to allocate resources more effectively. Not setting a placement can impact your attributions.
The following configuration shows travel restrictions for a return trip from USA to Mexico.
The following configuration shows travel restrictions for a return trip from Mexico to Canada via a connection in USA.
The following configuration shows travel restrictions via connection outbound and return. The use case takes into account origin as Germany (DEU) to Mexico via USA, while the return leg will be Mexico to Germany (DEU) via Canada.
This configuration shows a multi-transit trip with three segments on the outbound journey. Two of these segments are transit segments (YYZ -> USA and USA -> MEX) and the third is a regular outbound trip (MEX -> TUR).
The following configuration highlights the ability to show an extended segment. Consider a trip between the USA to Mexico with a return from Mexico to the USA. The below codes highlights the USA to Mexico leg segment.
The following configuration allows you to hide the title taking a trip that goes from USA to Mexico and has a return leg from Mexico to USA.
The following configuration will allow you to hide the 'Edit my Trip Button.
The following configuration sets a cookie policy that allows all cookies on the Element. This cookie policy will also apply to all existing and future Embedded Elements and Application Widgets.
To specify a restrictive cookie policy, include only the 'functionality_storage' and 'security_storage' cookie consent types