Lexaily, answered.
Straight answers on recovery, attribution, integrations, data, pricing, and setup, and on what the plugin and standalone sites each do. Something missing? Ask us.
All questions
Lexaily is booking recovery and attribution software for vacation rental operators, built by Zima Enterprises. It runs two ways, and your PMS decides which. The WordPress plugin, for Track PMS, captures guests who leave without booking and follows up with automated email, sends each booking and its revenue to your Google Analytics 4 and Google Ads so you can see which marketing earns bookings, and sets up the tracking with a guided wizard and a ready-made Google Tag Manager container. A standalone site is one we build and host on your Guesty account: guests search and get quotes from Guesty, exit prompts capture leads into your Lexaily portal, where you log in to see and export them, and the Book button hands guests to your existing booking engine, with every hand-off counted.
On the WordPress plugin, a guest who starts to leave sees an exit prompt offering a price alert or a reminder for their dates, and leaves their email. Four kinds of automated email can follow: a lead follow-up, a price drop alert when the rate falls, up to three abandoned quote recovery emails that stop once the guest books, and a reminder to finish an incomplete booking. A Recovered Revenue report in your WordPress dashboard shows the bookings they brought back. Lead follow-ups and abandoned quote recovery are part of the recovery add-on. On a standalone site, exit prompts capture the lead into your Lexaily portal for your team to follow up or export. Standalone sites do not send automated recovery emails.
On the WordPress plugin, each visitor gets an ID and a session on their first pageview, and their searches, property views, and quotes are recorded in your WordPress database. When a guest books, the booking and its revenue go to your Google Analytics 4 and Google Ads, which credit the channel that brought the guest. Lexaily does not store traffic sources itself. Your Google accounts do the channel reporting, and the plugin's own reports show your funnel and the revenue recovery won back. On a standalone site, guests finish booking on your existing booking engine, so Lexaily counts every hand-off instead, by home and by where on the site the guest clicked Book.
Not on your own. On the WordPress plugin, a setup wizard walks you through Google Tag Manager, GA4, and Google Ads step by step, and gives you a ready-made container with the booking events in place, so you import it instead of building tags by hand. On a standalone site, our team adds your Google Tag Manager or Google tag IDs for you. Booking events are not sent to Google from standalone sites, because the booking itself finishes on your own engine.
Track PMS and Guesty, each in its own way. The WordPress plugin runs on Track PMS: rates, availability, photos, and property content sync in, and confirmed bookings are written back to Track. Standalone sites run on Guesty: listings, photos, amenities, availability, and rates sync on a schedule, stay totals come from Guesty's own quote engine, and guests complete the booking on your existing booking engine. Card payments on the plugin run through SlimCD. On the roadmap: Guesty bookings and checkout, Guesty on the WordPress plugin, Track PMS on standalone sites, Streamline, OwnerRez, Escapia, and Barefoot.
It depends on your PMS. On Guesty, no: we build and host a standalone Lexaily site for you on your own domain, running on your Guesty account. It covers search, Guesty quotes, lead capture, and a hand-off to your existing booking engine, and your Lexaily portal holds every lead and every hand-off. On Track PMS, yes for now: Lexaily runs as a WordPress plugin, and Track PMS on standalone sites is on the roadmap. Automated recovery emails, checkout, and booking revenue sent to Google Analytics run on the WordPress plugin.
Direct. On the WordPress plugin, guests book and pay on your own domain. On a standalone site, they search and get a quote on your site, then finish on your existing booking engine. Either way there is no OTA commission on those bookings, and the guest relationship is yours.
You do. On the WordPress plugin, every lead and funnel event is stored in your own WordPress database, on your hosting. On a standalone site, leads and booking hand-offs are stored in your account on Lexaily's service. They belong to you, and you can export your leads at any time as a CSV file ready for HubSpot, Salesforce, or Mailchimp.
Checkout runs on the WordPress plugin with Track PMS: quotes against your availability, promo codes, and card payment through SlimCD, with the confirmed booking written back to Track. Card data is handled by SlimCD, not stored by Lexaily. Standalone sites have no checkout. Guests finish on your existing booking engine.
It depends on how you run it. On the plugin, we help connect Track PMS during onboarding and the setup wizard covers the tracking. A standalone site takes longer, because we build it around your brand and your Guesty listings. You get a timeline on the demo, and you can see the whole flow there first.
Pricing is custom. It depends on your unit count, your PMS, and whether you run the WordPress plugin or a standalone site, so there is no public price list. You get a quote, with the ROI math, before you commit.
No. Lexaily connects to your PMS and is set up with you during onboarding, so it is not a free self-serve widget.
A 30-minute walkthrough of recovery and attribution on a demo site, a look at which setup fits you, plugin or standalone, and a straight answer on what it would cost for your portfolio.
Rather see it than read about it?
A 30-minute walkthrough on a demo site, with your questions answered as we go.