Context
A hotel on the coast at Puerto Escondido with its rooms, its restaurant and its own booking engine already in place. The site in front of all of it was the part that was not pulling its weight.
The problem
Two problems that are really one. A booking made through an online travel agency carries a commission the hotel never sees again, so every reservation the site fails to take costs money on the way out. And because the booking itself happens on another domain, the campaign that produced it is lost at the jump: you can see that an ad was clicked and that a room was sold, with nothing joining the two.
The solution
The site is static Astro, in Spanish and English with its own slugs in each language, and every path through it ends at the hotel’s own engine — the English version opening it already in English with the currency set, and the offers linking straight to the promotion they advertise rather than to a generic search.
The measurement layer is the part that matters commercially. The campaign parameters a visitor arrives with are kept for the session, first touch is kept apart from the current one, and a Google click id survives ninety days, because a holiday is decided over weeks and not in one sitting. When the visitor goes through to the booking engine, those parameters are written into the link, so the reservation lands on the other side still carrying where it came from. Traffic coming back from the engine is excluded from the referrer logic, which would otherwise credit the booking engine with its own booking.
What it does
- Bilingual site with its own slugs per language, hreflang and sitemap
- Direct booking through the hotel’s Zavia ERP engine, with language and currency set for English
- Offers that deep-link to the specific promotion rather than a generic search
- Campaign attribution carried across into the booking engine
- First-touch kept separate from the current touch, with a ninety-day window for paid clicks
- Each call to action reports where on the page it was pressed: room card, header, offers, activities
- Restaurant reservations through OpenTable, tracked as their own conversion
- Structured data for the hotel, its location, its amenities and its reservation action
Architecture
Astro compiled to static HTML, so the pages are files on a CDN and there is no server to keep running. The interactive parts — carousel, hero video, mobile menu, form, map — are vanilla JavaScript inside each component. Reservations are not handled by the site at all: they belong to Zavia ERP, and the site’s job is to hand the visitor over with their context intact.
My role
Built the site, the booking-engine integration and the measurement layer. Astro for the pages, Zavia ERP for the reservation, and the tracking that joins the two.
Built with