Getting Started: Content

This guide covers terminology, where content is consumed, customer end objectives, and data import strategies. Additionally, it details media management, including import and assignment processes.

Terminology

For a full glossary related to Content, see this article.

Content: An object/data table within Salesforce containing static text descriptions of various elements within Kaptio Travel, e.g., Services, Packages, Location, etc.
Product Content: An umbrella term for all text articles and media needed for providing information on the product catalog or related information in the process of marketing, quoting, or informing the end customer.
Product Attributes: Custom or standard attributes (fields on an object in Salesforce) that sit at the Supplier, Service, Price Category, or Package levels. These attributes can be exposed through multiple use cases (Itinerary Documents, website, reporting, etc.) and through multiple channels (direct & indirect trade channels).

Product Location: A specific type of attribute representing where a service, price category, or package is physically located.

Service Content: Descriptions (or body text) detailing a service or price category, available in multiple languages and accessible through multiple channels.
Package Content: Descriptions (or body text) detailing a package or package day, available in multiple languages and accessible through multiple channels. Intended for consumption in Itinerary Documents.
Package Tour Content: Content related to a package via the Package Day object based on its index number (day within package). Generally intended for marketing purposes and are not available for Itinerary Documents using standard components.
Destination Content: Descriptions of a specific destination usable through multiple channels (direct and indirect).
Location Content: Descriptions of a specific destination usable through multiple channels (direct and indirect).

Location Hierarchy: The setup of destination hierarchies (e.g., Continent, Country, Region, City) to which all products are tagged.
Departure Template Location Content: Descriptions of specific destinations during a Cruise or Multi-Day Rail service. Stored in Departure Templates.
Service Departure Location Content: Descriptions of specific destinations during a Cruise or Multi-Day Rail service, overriding Departure Template Location Content for specific departures.

Generic Content: Descriptions not tagged to a specific product or destination, e.g., Terms & Conditions or other content useful for customer travel documents.
Content Media: Video and image files attached to a content record, with images hosted on AWS or a chosen third-party storage and videos embedded from YouTube or Vimeo.
Content Languages: Any content described here can be created in multiple languages within Kaptio.

Where Content Gets Consumed

Itinerary Documents: Content generated inside Kaptio Travel Reservations, either manually by a sales user (e.g., quote) or automatically by a time trigger (e.g., scheduled creation of travel documents). Shared via HTML websites with private URLs or as PDF documents via email.
Transactional Emails: Content used within emails sent from Kaptio Travel Reservations, e.g., distributing invoices, travel documents, or other data. Kaptio recommends managing customer-facing email communication within Kaptio/Salesforce.
Website: Content to be presented on your website.
Kaptio Commerce: Content displayed as part of a checkout flow using Kaptio Commerce.
Other API Distribution: System-to-system partner integrations for live product and availability between tour operators and travel agents/wholesalers.

Customer End Objective

Master Data Ownership In each project, clearly define where content is mastered (managed/maintained) versus where it might be published (synchronization from/to CMS or Kaptio Travel system).

Kaptio Recommended Approach Store content in a CMS as the "source of truth" and push relevant content into KaptioTravel. This approach provides flexibility in managing rich content and allows seamless integration with other systems.

Headless Content Hub Approach

Define how content gets distributed across multiple systems using a headless content hub approach.

Kaptio Recommended Approach

Product Attributes, Service Content, Product Media, Package Tour Content, and Destination Content: These are relatively static and best cached within a consumption system (such as a CMS website platform) via a scheduled stored procedure polling mechanism. Product pricing & availability should always use live requests via Kaptio APIs.

Content in the Consumption System but Not in Kaptio Travel

Define where variations should be managed based on channel-specific needs.

Kaptio Recommended Approach

Ensure flexibility in styling and presentation in the consumption system. In a CMS context, have static product pages linked by an ID between the CMS and Kaptio Travel, allowing the website teams to augment the content with additional information not needed by Kaptio Travel. This enables the website team to tailor the presentation and styling of content to meet specific channel needs without complicating the reservation processes in Kaptio Travel.

For more detailed insights and updates, refer to the article on our hub: Getting Started with Content.

Terminology
Where Content Gets Consumed
Customer End Objective
Headless Content Hub Approach
Content in the Consumption System but Not in Kaptio Travel