This guide is for you if the booking form appears inside your own website. If your guests book on a Restoo page, go to the guide for hosted on Restoo.
Do I need to change anything?
Find your case in this list. If more than one applies, work through them top to bottom.
Prerequisites
- The widget already migrated to v2, following the installation migration guide.
- Access to your website’s code.
- Access to your Restoo account settings.
What is on you
With the widget inside your site, measurement runs on your page, and half of this guide comes from that:
- Each platform’s tags have to be there, and load before the widget. Restoo Connect forwards to the ones it finds, but installs none; if the widget loads first, the first events are lost.
- You collect the consent and pass it to Restoo.
1. Choose where your booking events should arrive
This affects you if you measure bookings with Google Tag Manager, with each platform’s measurement code placed directly on your site — the Meta Pixel, gtag.js, TikTok’s, OpenAI’s — or with both.
What changed. v2 no longer loads any GTM container, neither inside the iframe nor on the page Restoo hosts for you: if you have one configured in Restoo, it will stop measuring as soon as you migrate.
What to do. With the widget inside your site, the events leave the iframe and Restoo Connect receives them on your page. From there you have three options. Pick one:
- Use your Google Tag Manager container (recommended if you already have one). If it isn’t on your own site yet, install it there: it’s yours, so your tags come inside it. Then save its ID in your Restoo account to enable the
gtm destination: Connect pushes every event to your dataLayer and your tags hand them out as they already did. Your triggers go by event name, and the names are in the GTM reference.
- Send the events to each platform directly. Configure the destinations in your Restoo account — Google Analytics, Google Ads, Meta Pixel, TikTok Pixel, or OpenAI Pixel — and Connect will call
gtag, fbq, ttq, and oaiq on your page. That requires each platform’s base code to be there: Restoo installs none, and until now your GTM was loading them. What each destination needs.
- Listen for the events yourself (for very advanced setups only). The widget emits them on your page as Restoo Widget Events, so you can pick them up with your own listeners and take them wherever you want: there you have how to listen for them and their payloads. It requires your own development, and the consent is your responsibility: with no destination enabled, Connect is not initialized and nobody applies those rules for you.
Do not leave two options active for the same platform. If your GTM forwards
bookings to Meta and the metaPixel destination is enabled as well, every
event arrives twice. Keep only what you use in your account, or switch the rest
off for this installation with connect: { metaPixel: false }.
2. Declare what you use your GA4 property for
This affects you if the ga4 destination is enabled in your account and you have never declared what you use that property for. If you measure GA4 through your GTM, this doesn’t apply: the declaration belongs to the Restoo integration, not to your tag.
Why it needs a look. A property that feeds advertising requires advertising consent, and v1 never asked. Until you declare it, Restoo takes the most restrictive case and only measures visitors who also accept those cookies.
What to do. Answer it once in your Google Analytics integration settings. Only the account administrator can do it, even when an agency or a webmaster handles the rest of this guide.
3. Move your conversions, events, and triggers to Restoo Connect
This affects you if you have custom measurement of the booking funnel. For example:
- Meta custom conversions defined by a URL rule, the kind that says “URL contains
reservar/seleccionar-horario”, created in Events Manager.
- Events set up by click, pointing at the booking flow’s buttons with Meta’s event setup tool.
- URL-based conversions or events in Google Ads or Google Analytics 4.
- Google Tag Manager triggers tied to the URL of a booking step, to a button, or to an element on the page.
Why it needs a look. Those rules cannot match again, because the steps are no longer separate URLs and the booking HTML has been rebuilt from scratch: different tags, different classes, different buttons.
What to do. Rebuild each conversion on the Restoo Connect event that replaces it, not on a URL. The events are already reaching you: Restoo Connect translates every funnel step into the event each platform expects.
In Meta, for instance, the guest-details form arrives as ViewContent, a confirmed booking as Schedule, and one left pending confirmation or on a waiting list as Lead. Each booking fires a single conversion.
To decide which ones to mark as the primary conversion in your campaigns, see the bidding and optimization guide.
4. Replace the UTM transfer script
This affects you if either of these URLs appears anywhere in your website’s code:
Why it needs a look. That script is what gets your campaigns’ UTM tags into your Restoo reports, even when a visitor goes through several pages of your site before booking. v2 has its own.
What to do. Remove it and add the new script in its place: Restoo Attribution Transfer has the code and where to paste it.
Bear in mind that it goes on every page of your site, not just the one carrying the widget.
Checklist
Go through this when you are done, before calling the change good.
- The widget is already migrated to v2, following the installation migration guide.
- Only one option is active for your events: your GTM, the direct destinations, or your own listeners.
- Your destinations’ libraries are on your page and the widget loads after them.
- Your consent platform is declared or your site calls
setConsent(): with the widget embedded in your site you collect the consent.
- If you measure in GA4, the property is declared.
- Your conversions are built on events, not on URLs or buttons.
- The old UTM transfer script is gone, and Restoo Attribution Transfer is on every page.
- Each platform’s extension shows the events arriving.
- The old conversions and triggers are deleted.
- If you work with a marketing agency, they know you have migrated.
Need help?
Email us at soporte@restoo.me. If an agency or an external webmaster runs your campaigns, you can forward them this page as it is. 
