Platform and workflow terms
| Term | Meaning |
|---|---|
| Content Engine | The creation system that crawls, curates, generates, assesses, and reprocesses destination content. |
| Portal | The management dashboard used to manage destinations, content, delivery settings, and users. |
| Management | The platform area that covers setup, review, publishing, and access management in Portal. |
| Destination Setup | The process of setting destination details, rules, and delivery settings in Portal. |
| Approval Workflow | The review and sign-off process a team follows in Portal before content is published live. |
| Launch Scope | The launch scope agreed by the team, including destinations, delivery path, and content priorities. |
| Use Case | The practical business objective a team wants a product path to support, such as SEO visibility, engagement, or guest experience. |
| Section | A component or block on a page that contains content and styles. |
| Content | Copy, imagery, links, and similar editorial elements managed in page editing workflows. |
| Site Editor | The Portal area where Microsite pages are managed and Page Editor is opened for day-to-day updates. |
| Page Editor | The screen used to edit copy, imagery, and styling on an individual Microsite page. |
Content model terms
| Term | Meaning |
|---|---|
| Destination | A location-based entity in Obvlo with its own content and delivery settings. What counts as a destination depends on your business: a property or resort (hotel groups), a city or region (DMOs and tourism boards), a route or trip endpoint (airlines, OTAs, and tour operators), or any other geography relevant to what you sell. Each destination is configured independently, with its own content, brand settings, and delivery setup. |
| Root Page | The microsite’s own top-level hub page. Destination, Area, and Thematic pages sit beneath it as its child pages. |
| Destination Page | A Microsite page type covering key travel information and curated highlights for a single destination. |
| Guide | A collection of listings built around a place or theme. |
| Thematic Guide | A guide focused on an interest or theme, such as food, culture, or wellness. |
| Area Guide | A guide focused on a specific location or neighbourhood within a destination. |
| Topic Page | A Microsite page type that goes deeper on a specific audience or occasion than destination or guide pages. Also referred to as a Campaign page. |
| Listing | An individual recommendation item used across guides and delivery channels. |
| Itinerary | A destination plan created by Obvlo. |
| Content Theme | A strategic topic focus for content planning, such as family, food, wellness, culture, events, or seasonal travel. |
| Content Output | Generated content type such as guides, listings, itineraries, imagery, or related destination data. |
| Template Configuration | Rules defining what content is created, for which audience, and under which criteria. |
| Brand Configuration | Rules used by Obvlo to keep generated content aligned with brand tone, voice, and visuals. |
| Promos | Promotional content units that can be targeted and scheduled by audience and time window. |
Delivery and integration terms
| Term | Meaning |
|---|---|
| Web App | Obvlo’s hosted Digital Concierge experience used across pre-arrival and in-stay journeys. |
| Digital Concierge | The customer-facing name for the hosted Obvlo Web App. |
| Embeddable Widget | The product name for Obvlo’s on-site Trip Planner component that is embedded in an existing website. |
| Trip Planner | The customer-facing name often used for the Embeddable Widget experience. |
| Microsite | The customer-facing name for Obvlo HTML Pages. |
| HTML Pages | Technical product name for Microsite pages served under your domain. |
| API | The API used to send destination content into a customer’s own system. |
| Partner Integrations | Pre-built connectors linking Obvlo with systems such as PMS, CMS, CRM/CDP, and AI chatbot platforms. |
| Reverse Proxy | The technical setup used to serve Obvlo-managed Microsite pages under a customer’s own domain. |
Performance and optimisation terms
| Term | Meaning |
|---|---|
| Guest Journey | The sequence of traveller touchpoints across pre-arrival, in-stay, and post-launch optimisation. |
| Attract Stage | The early guest-journey stage focused on search visibility and destination discovery before booking. |
| Engage Stage | The guest-journey stage focused on on-site interaction depth and conversion support. |
| Journey Coverage | The way a product supports pre-arrival planning, in-stay usage, and post-launch optimisation. |
| Personalisation | The process of adapting ranking and recommendations based on traveller context, intent, or preference signals. |
| Analytics Feed | Event data from Obvlo delivery channels that can be sent to your analytics tools. |
| Reports | Portal dashboards used to review engagement, search, and performance trends. |
| Search Model | The framework used on Microsite pages to support SEO, GEO, and AEO discovery patterns. |
| SEO | Search Engine Optimisation: practices that improve visibility in traditional search results. |
| GEO | Generative Engine Optimisation: content practices aimed at improving visibility in AI-generated search responses. |
| AEO | Answer Engine Optimisation: structuring content so direct-answer systems can retrieve and present it clearly. |
| Change Log | The support page that tracks notable product updates and release communication. |