How the Restoo Widget Works

The three ways to install the Restoo widget, the four pieces around it, and who is responsible for what.

The widget is the form your guests book and buy on. It can appear inside your own site, or on a page Restoo hosts for you.

Around it sit four more pieces: three to measure and one to decide what may go out to your platforms.

The three ways to install it on your site

• Modal over your page (recommended): a button opens the form on top of your site, full screen on mobile. You install it with Restoo.js.
• Inline in your page: the form appears as part of the content, also with Restoo.js.
• Hosted on Restoo: your guests book on your Restoo page and you just link to it, without touching code.

The first two leave the form embedded in your site; the third leaves it hosted on Restoo. That is what the rest of this guide calls them.

You can combine them. And the link to your Restoo page does not have to stay on your site: it works just as well in your Google profile, your socials, or your newsletter.

Which one should I use?

We recommend the modal over your page in almost every case:

• Your guests never leave your page: they book right there, without you sending them somewhere else.
• Better SEO and cheaper campaigns: the widget is not downloaded on every visit, only when someone clicks the button, so your page loads faster. That lifts your PageSpeed score, which affects both your SEO and what your campaigns cost.
• A better experience on mobile: it opens full screen, so your site’s navigation stays visible and fixed.
• No layout conflicts: it renders in its own fixed layer, isolated from your page’s CSS, its width constraints, and whatever surrounds it.

What each piece does

Piece	What it does	What you do, and where
The widget	Takes what your guests book and buy	Configured in your Restoo account, and installed with Restoo.js if you embed it
Integrations	Declares your analytics and advertising platforms, once	Configured in your Restoo account
Restoo Connect	Translates every booking step into the event each platform expects	Nothing: it loads with the widget
Consent	Decides what is sent to each platform and what isn’t	Collected in your cookie notice, or Restoo’s if you host it
Restoo Attribution Transfer	Keeps the campaign and the ad click alive while the visitor browses your site	Installed on every page of your site

How the pieces fit together

The booking is stored whatever happens: what depends on consent is its attribution, and which destinations receive the event.

Responsibilities, embedded or hosted

The difference is mostly in who puts the measurement tags in place, and who asks for consent and passes the decision on.

The full split:

Responsibility	Hosted on Restoo	Embedded in your site
Installing Restoo.js on your site	Restoo	You
Installing Restoo Attribution Transfer on your site, and asking for its consent	You	You
Adjusting the form’s appearance: colors and fonts	You, in your account	You, in your account or in code
Putting the measurement tags on the page	Restoo	You
Sending each event in the format each platform expects	Restoo Connect	Restoo Connect, or you if you listen to the widget events
Asking the visitor for consent	Restoo	You
Passing that decision to the widget	Restoo	You
Applying that decision per destination	Restoo Connect	Restoo Connect, or you if you listen to the widget events
Configuring your GTM container’s Consent Mode	N/A: GTM never loads	You

Next steps

Installation Quickstart

Put the widget on your site and start taking bookings.

Set Up Your Integrations

Enable GA4, Google Ads, Meta, TikTok, ChatGPT Ads, or GTM in your account and start measuring.