1. Date-based pop-ups tied to the guest’s travel dates
We’d like the ability to trigger a pop-up only when a guest is searching for dates that include a specific date within their stay. For example:
A Christmas Day message should only appear if the guest’s selected travel dates include 25 December.
If their stay does not include that date, the message would not display.
2. Pop-ups based on length of stay
It would also be very helpful to trigger pop-ups based on the number of nights selected in the booking search. For example:
If a guest selects a 2-night stay, we could show a message such as: “Extend your stay to 3 nights and receive 10% off.”
Essentially, we’re hoping to show more relevant promotional messages based on the guest’s selected travel dates and stay length, rather than only general scheduling.
Hi @Max, thank you for your reply.
Our accommodation booking engine is powered by Mews. This is the API info on their booking widget if it helps Mews Booking Engine Guide | Booking Engine | Mews Open API but I feel this implementation would be of great benefit to all of your travel-based partners.
My best guess is that if we were able to add rules for the check-in dates, length of stay and even lead time within elfsight we would then need to embed some code on the Mews booking engine to make this work. We currently run our pop-ups via another partner, and I would love to transfer all of them over to elfsight but as so many of our pop ups are information-based messages, contingent on when the guest is wanting to travel / their search.
I see what you mean, but, unfortunately, it’s impossible to implement this idea now. However, we’ll keep it in mind and if it gets more votes, we might look into this in the future
Hi, I’ve actually created a similar logic using the Calculator App, and it could help achieve exactly what you’re describing. The idea is to use the calculator logic to detect the selected dates or number of nights, and then trigger the relevant message inside the Popup widget by embedding the calculator code within it. For example, the calculator can: Detect if the selected dates include 25 December and trigger a Christmas message. Detect the length of stay (number of nights) and show a promotional message like “Extend your stay to 3 nights and receive 10% off.” The advantage of this approach is that the calculator allows conditional logic, which makes it possible to show highly targeted messages, and the popup can include a clear call-to-action button (for example: Extend Stay, See Offer, etc.). It’s actually a very flexible solution and works well when you want promotions to react dynamically to the user’s input rather than using fixed schedules. If helpful, I’d be happy to share how the logic can be structured.
I actually built something similar using the Calculator App with conditional formulas. The logic uses IF and CONTAINS rules, which means some calculation lines only activate when a specific option is selected, while the others stay inactive and don’t affect the result. For example, in one formula we created, the system checks the selected service and vehicle type. If the user selects Airport Transfer, only the pricing line for IST is used, while the lines for SAW or tour destinations stay inactive. Another example is vehicle upgrades: if a user selects Sprinter, only the Sprinter pricing rule activates, while the Vito and Maybach rules don’t run. So each selection triggers only the relevant part of the formula. The same logic could be used for @Alicia_Szerszyn’s case — for example: If the selected dates include December 25, the Christmas message appears. If a guest selects 2 nights, a message could appear suggesting “Extend to 3 nights for a discount.” This way the popup content becomes dynamic and based on the user’s input, rather than showing the same message to everyone.
Ah, I see. Thanks so much for sharing your use case!
This logic works great in the Calculator widget because it has built-in conditional fields that react to user inputs, and these inputs trigger the conditional logic since they’re part of the widget.
Unfortunately, we can’t apply the same logic in the Popup widget right now. The Popup already has triggers that activate after interaction with the widget or its loading, but in Alicia’s case, the popup would need to be triggered by an input from an external booking engine.
For this to work, the popup would need to be connected to the booking widget or have a complete integration, which isn’t available at the moment.
I hope that helps clear things up! Thanks again for being so involved and helping us look for a solution — we really appreciate it
