Kapta · 15/09/2026
First choose the experience visitors should open: a specific activity, calendar or selection of options. Then configure the link or component provided by FareHarbor and test it on the pages and devices where it will be used.
Do I need a custom API integration for website bookings?
Not necessarily. FareHarbor documentation describes links, buttons and embedded components produced by its tools. A custom API integration has a different scope. FareHarbor links and embeds.
How should I choose a button or calendar?
A button may suit a page already explaining one experience. A calendar can help when the date is the main decision. Test the journey with visitors: can they understand the activity, find a date and return to its details without losing context?
What are the practical steps?
- Identify the FareHarbor account and activity.
- Choose the appropriate booking option in the generator.
- Obtain its code or link.
- Place it on a website test page.
- Check additional requirements for the selected option, including the plugin when using a WordPress shortcode.
- Validate the full journey before repeating it across other pages.
What should I test on mobile?
Check button visibility, whether the component hides essential controls and whether participants can be selected. Test language, dates, displayed amounts and an unavailable activity. Opening the booking system does not prove the entire journey works.
How should success be measured?
Separate button clicks from confirmed bookings. Agree measurable events with the provider and the site's consent configuration. Do not report every outbound click as a completed sale.
What should I send Kapta?
The website address, platform, activity to connect and expected behaviour. Include Portuguese and English pages where available. Connecting bookings to invoicing should be described as an additional requirement.
