Skip to main content

Platform and workflow terms

TermMeaning
Content EngineThe creation system that crawls, curates, generates, assesses, and reprocesses destination content.
PortalThe management dashboard used to manage destinations, content, delivery settings, and users.
ManagementThe platform area that covers setup, review, publishing, and access management in Portal.
Destination SetupThe process of setting destination details, rules, and delivery settings in Portal.
Approval WorkflowThe review and sign-off process a team follows in Portal before content is published live.
Launch ScopeThe launch scope agreed by the team, including destinations, delivery path, and content priorities.
Use CaseThe practical business objective a team wants a product path to support, such as SEO visibility, engagement, or guest experience.

Content model terms

TermMeaning
DestinationA location-based entity in Obvlo with its own content and delivery settings.
GuideA collection of listings built around a place or theme.
Thematic GuideA guide focused on an interest or theme, such as food, culture, or wellness.
Area GuideA guide focused on a specific location or neighbourhood within a destination.
ListingAn individual recommendation item used across guides and delivery channels.
ItineraryA destination plan created by Obvlo.
Content ThemeA strategic topic focus for content planning, such as family, food, wellness, culture, events, or seasonal travel.
Content OutputGenerated content type such as guides, listings, itineraries, imagery, or related destination data.
Template ConfigurationRules defining what content is created, for which audience, and under which criteria.
Brand ConfigurationRules used by Obvlo to keep generated content aligned with brand tone, voice, and visuals.
PromosPromotional content units that can be targeted and scheduled by audience and time window.

Delivery and integration terms

TermMeaning
Web AppObvlo’s hosted Digital Concierge experience used across pre-arrival and in-stay journeys.
Digital ConciergeThe customer-facing name for the hosted Obvlo Web App.
Embeddable WidgetThe product name for Obvlo’s on-site Trip Planner component that is embedded in an existing website.
Trip PlannerThe customer-facing name often used for the Embeddable Widget experience.
MicrositeThe customer-facing name for Obvlo HTML Pages.
HTML PagesTechnical product name for Microsite pages served under your domain.
APIThe API used to send destination content into a customer’s own system.
Partner IntegrationsPre-built connectors linking Obvlo with systems such as PMS, CMS, CRM/CDP, and AI chatbot platforms.
Reverse ProxyThe technical setup used to serve Obvlo-managed Microsite pages under a customer’s own domain.

Performance and optimisation terms

TermMeaning
Guest JourneyThe sequence of traveller touchpoints across pre-arrival, in-stay, and post-launch optimisation.
Attract StageThe early guest-journey stage focused on search visibility and destination discovery before booking.
Engage StageThe guest-journey stage focused on on-site interaction depth and conversion support.
Journey CoverageThe way a product supports pre-arrival planning, in-stay usage, and post-launch optimisation.
PersonalisationThe process of adapting ranking and recommendations based on traveller context, intent, or preference signals.
Analytics FeedEvent data from Obvlo delivery channels that can be sent to your analytics tools.
ReportsPortal dashboards used to review engagement, search, and performance trends.
Search ModelThe framework used on Microsite pages to support SEO, GEO, and AEO discovery patterns.
SEOSearch Engine Optimisation: practices that improve visibility in traditional search results.
GEOGenerative Engine Optimisation: content practices aimed at improving visibility in AI-generated search responses.
AEOAnswer Engine Optimisation: structuring content so direct-answer systems can retrieve and present it clearly.
Change LogThe support page that tracks notable product updates and release communication.