Skip to main content
We have rebuilt the widget from scratch, inside and out. On the outside, a booking flow that converts better. On the inside, measurement you used to have to build yourself, or that simply was not possible: knowing which step a guest drops out at, for instance. Now it comes as standard.

What you gain

A new design, top to bottom

The booking experience, rebuilt from scratch out of the thousands of bookings that go through Restoo every day. With your colors and your fonts, without touching code: how it matches your brand.

New features

Improvements to experience bookings, paella bookings, and beach clubs. And it does not stop here: the next ones are already on the way. 🚀

Full measurement, from the first search to the confirmed booking

Enable the destinations you use in your Restoo account — GA4, Google Ads, Meta Pixel, TikTok Pixel, OpenAI Pixel, or GTM — and Restoo Connect takes care of the rest: no tags, no triggers, no events to map. It sends the availability search, the lead, the contact, and the confirmed booking, and also everything in between: which options the guest sees, which ones they pick, and where they drop out.

Better ad performance and a lower CPC

Your campaigns optimize toward real conversions, in the event model each platform expects. To choose which ones to hand over as the primary conversion, the bidding and optimization guide says which to use and which to leave as secondary. The modal, on top of that, only loads when someone clicks: your page gets lighter, and with it your landing page experience and your ad quality score. Without touching a single bid.

Advanced Matching: recover conversions you are not seeing today

The guest’s email and phone are sent normalized and hashed for Meta Advanced Matching, Google Enhanced Conversions, TikTok’s identify, and the OpenAI Pixel’s user. With that, the platforms attribute bookings that would otherwise stay unidentified and, in some cases, strengthen your remarketing audiences: what is sent and when.

Native Google Ads, TikTok Pixel, and OpenAI Pixel integration

On top of GA4 and Meta Pixel, now Google Ads, TikTok Pixel, and OpenAI Pixel too, with no layers in between: each one receives the conversions exactly as it expects them. You can see how each one is translated.

GDPR compliance by design, with no extra effort

Nothing goes out to any platform until the visitor’s decision is known, and each one receives only what belongs to it. You collect it with your consent platform — Cookiebot or any platform with Consent Mode v2 — and all Restoo needs is which one: how to declare it.

Attribution that survives the guest’s real journey

With Restoo Attribution Transfer the campaign reaches your reports intact even when the ad lands on your homepage, even when the guest wanders around before booking, and even when they come back days later. That way you know which sources, campaigns, and ads generate real bookings, instead of losing the attribution on the first internal click.

Simple to start with. Flexible enough to go as far as you need

Enabling your destinations in the account is all it takes: it is already measuring, without a line of code. If you would rather control it from Google Tag Manager, Restoo pushes every event to your dataLayer and your tags hand it out. And for a custom integration you have the raw widget events, to listen for yourself and take wherever you want.

Less friction, more conversions recorded

On mobile the modal opens the booking full screen, without fighting your page layout or your scroll position. And what gets booked gets recorded: the full funnel arrives, not just the final booking.

What changes and needs your attention

Four changes can break something you have built. The reason for each one is here; what to do about it is in the guide for your case.

The <iframe> is replaced by a script

If your site embeds the booking flow, the <iframe> and its resizing script give way to Restoo.js, which mounts the widget when it is needed — or only when someone presses the button, if you pick the modal — so a visitor who arrives and does not book never downloads it.

GTM no longer loads on Restoo pages

A GTM container can carry any tag inside it, and on a domain we host we cannot vouch for all of them respecting the visitor’s decision. That is why v2 loads none, neither inside the iframe nor on the hosted page. On your own site GTM keeps working exactly as before: there the container is yours and it runs on your page.

GA4 needs to know what you use the property for

A GA4 property linked to Google Ads, with Google signals enabled, or exporting audiences feeds advertising personalization, and that requires the visitor’s advertising consent, not just the analytics one. v1 never asked, so no migrated account has an answer on record. Until there is one, Restoo takes the most restrictive case.

Booking steps are no longer separate URLs

In v1, every step had its own URL and its own HTML. In v2 the view goes in a parameter on the same address, and the booking HTML has been rebuilt from scratch: different tags, different classes, different buttons. Any rule that read those URLs or those buttons — a Meta custom conversion, a GTM trigger — stops matching, and there is no new URL to repoint it at. Instead, Restoo Connect translates every funnel step into the event each platform expects.

What stays the same

Every address you have published — Google, social media, your newsletter — keeps working.

Your bookings

The change affects your website only, not your booking management: none is lost, and it takes effect immediately.

Your guests

There is nothing to tell them and nothing for them to do.

What do I do with this

Which parts apply to you depends on how you use Restoo on your site, and the migration quickstart settles that in one screen.