> ## Documentation Index
> Fetch the complete documentation index at: https://restoo.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Setting Up Your Integrations in Restoo
> Where and with what data GA4, Google Ads, Meta Pixel, TikTok Pixel, OpenAI Pixel, and Google Tag Manager are enabled in your Restoo account.
Your analytics and advertising platforms are declared **once in your Restoo account**, not in your site's code: from there they apply to every installation you have. [Restoo Connect](/widget/connect) is the script that then sends them the booking events.
They live in **Settings → Integrations**, under *Marketing*. Each platform is a separate integration.
| Platform | Field in Restoo |
| ------------------ | ------------------------------------------------------------------------ |
| Google Analytics 4 | **Google Analytics (measurement ID)**, the one starting with `G-` |
| Google Tag Manager | **Google Tag Manager (container ID)**, the one starting with `GTM-` |
| Meta Pixel | **Meta Pixel ID** |
| TikTok Pixel | **TikTok Pixel ID** |
| OpenAI Pixel | **OpenAI Pixel ID** |
| Google Ads | **Conversion ID** and one **label** per action: [see below](#google-ads) |
**An empty field is a destination switched off.** Restoo Connect only sends to
the platforms whose identifier is saved here; clearing it is how you stop
sending.
## Google Analytics 4
When you save a measurement ID, Restoo also asks you to answer **What do you use the data from this Google Analytics property for?** It is not optional: without an answer the ID cannot be saved.
* **Measurement only**: to see how the site and the booking funnel perform.
* **Advertising too**: remarketing, audiences, or Google Ads campaigns.
The answer decides what consent Restoo requires before it sends anything to that property. With *advertising too*, events are only sent when the visitor also accepts advertising cookies.
If you are not sure which one applies, look in Google Analytics: a property
with [Google signals](https://support.google.com/analytics/answer/9445345)
enabled, [linked to Google
Ads](https://support.google.com/analytics/answer/9379420), or exporting
audiences to Ads is the second case. When in doubt, pick *advertising too*.
## Google Tag Manager
Saving the container ID enables the `gtm` destination: Restoo pushes the booking events to `window.dataLayer`, where the tags in your container pick them up. Those tags are yours to define, with custom event triggers: the event names are in [Event Mappings](/widget/connect-mappings#google-tag-manager).
**This field only does something with the widget installed on your own site.**
Hosted on Restoo no container is loaded, so it does nothing. To use GTM,
[install the widget on your own site](/widget/quickstart).
## Meta Pixel
The ID you save is the one of the pixel you already have installed. Restoo also uses it for Advanced Matching, so this ID decides **who receives your guests' hashed email and phone**: see [Customer identity](/widget/consent#customer-identity) for what is sent and under which permission.
If you have the **Facebook Business** integration active, the field is locked:
the pixel is managed from there. To edit it here, deactivate that integration
first.
## TikTok Pixel
The ID you save is the one of the pixel you already have installed on your site. Restoo Connect uses whichever `ttq` it finds there and scopes every call to this ID, so the other pixels on the page receive nothing.
## OpenAI Pixel
The ID you save is the one of the ChatGPT Ads pixel you already have installed on your site: you will find it in the conversions tab of its [Ads Manager](https://ads.openai.com). Restoo Connect uses whichever `oaiq` it finds there and scopes every call to this ID, so the other pixels on the page receive nothing.
As with Meta, this ID also decides **who receives your guests' hashed email and phone**: see [Customer identity](/widget/consent#customer-identity) for what is sent and under which permission.
## Google Ads
This one is not a single field, but two: the account's **conversion ID**, the one starting with `AW-`, and one **label** per conversion action.
| Label | Sent when |
| ------------------- | -------------------------------------------------------------- |
| `booking_lead` | A booking is created pending confirmation or on a waiting list |
| `booking_confirmed` | A confirmed booking is created |
| `contact` | The guest taps a contact button: phone, email, or WhatsApp |
Google Ads gives them to you separately, and that is how they go in: the conversion ID is the same for every action, while each label belongs to just one. Paste the label on its own, without the conversion ID in front of it: Restoo joins them when it sends the conversion.
Only the actions that have their label configured fire. To decide which ones to use as the primary conversion in your campaigns, see [Bidding & Optimization](/widget/bidding-optimization).
## After you save
It applies **from the next page load**, and there is nothing to deploy on your site.
With the widget embedded in your site, check as well that each platform's library is on your page and that the widget loads after it: that is in [what each destination needs](/widget/connect#before-you-start).
In either case, the quick way to confirm everything arrives is to [check that events fire](/widget/diagnostics#checking-that-events-fire) with each platform's tools.
## Next steps
Nothing goes out to any platform until the visitor's decision is known.
What each destination sends and what your page needs to receive it.