Conversion tracking with Google and Meta
Conversion tracking tells your Google and Meta accounts what guests do in your booking engine: when they search, when they start checkout and when they book, with the booking's value. You then see in Google Analytics, Google Ads and Meta Ads Manager which ads and campaigns bring bookings, and the ad platforms can show your ads to people more likely to book.
This is separate from Google Hotel Ads and free booking links, where your prices show up in Google search and Maps. Those are set up through the channel manager.
What Areca sends
You only enter the IDs of your accounts. Areca loads Google's and Meta's own scripts in the booking engine and sends these events:
| What the guest does | Google Analytics | Google Ads | Meta pixel |
|---|---|---|---|
| Opens the booking engine | page view | PageView | |
| Searches for dates | search | Search | |
| Goes on to enter their details | begin_checkout | InitiateCheckout | |
| Completes a booking | purchase | conversion | Purchase |
A booking is reported with its total, its currency and the booked rooms. Each booking counts once: going back in the browser or reloading the confirmation does not report it again. Bookings paid by card are reported when the guest returns from the payment page, and only when the payment went through.
Before you start
You need:
- A Google Analytics 4 property, a Google Ads account or a Meta pixel. Set up any of them, or all three.
- Access to Settings > Integrations in Areca.
- Your website with the website widget or links to your booking engine.
Step 1: Google Analytics 4
Find your Measurement ID
- Sign in to Google Analytics. If you have no property yet, click Admin > Create > Property and follow the steps.
- Open Admin > Data collection and modification > Data streams and click your web stream. If there is none, add a Web stream with your website address.
- Copy the Measurement ID. It looks like
G-XXXXXXXXXX.
Use the same property as on your own website, so a visit to your website and the booking that follows are in one place.
Set up your domains
Your booking engine runs on app.arecabooking.com, so Google Analytics has to know it belongs to your website.
- In the same web stream, click Configure tag settings > Configure your domains.
- Add your website's domain (for example
yourhotel.com) andapp.arecabooking.com. Save. - Go back, open Show more > List unwanted referrals and add a condition: Referral domain contains
checkout.stripe.com. Save.
The last step keeps card payments from being counted as visits from Stripe. Areca already tells Google Analytics to ignore Stripe, this setting is a second safeguard.
Check that bookings count as key events
Google Analytics marks purchase as a key event on its own. To check, open Admin > Data display > Events after
the first test booking and see that Mark as key event is on for purchase.
Booking value then shows up in reports such as Reports > Monetization > Ecommerce purchases and Reports > Acquisition > Traffic acquisition.
Step 2: Google Ads
There are two ways to count bookings in Google Ads. Choose one. Using both counts every booking twice.
- Option A, import from Google Analytics. Simplest when Google Analytics is set up as in step 1. In Google Ads,
link your Google Analytics property under Tools > Data manager, then open Goals > Conversions > Summary >
Create conversion action > Import > Google Analytics 4 properties > Web and pick
purchase. You enter nothing in Areca for Google Ads. - Option B, a Google Ads conversion tag. Counts conversions even without Google Analytics, and Google Ads sees them sooner. Follow the steps below.
Option B: create a conversion action
- In Google Ads, open Goals > Conversions > Summary and click Create conversion action.
- Choose Conversions on a website, enter your website address and click Scan, then choose Add a conversion action manually.
- Set:
- Goal and action optimization: Purchase.
- Conversion name: for example "Booking engine booking".
- Value: Use different values for each conversion. Areca sends each booking's total and currency, so a default value only matters if one is ever missing.
- Count: One. A booking is one conversion.
- Click Done, then Save and continue.
- On the setup screen choose Use Google tag > Install the tag yourself. In the event snippet find the line
'send_to': 'AW-123456789/AbCdEfGhIjKlMnOp'.- The part before the slash is the Conversion ID:
AW-123456789. - The part after the slash is the Conversion label:
AbCdEfGhIjKlMnOp.
- The part before the slash is the Conversion ID:
You do not paste the snippet anywhere. Areca adds the tag to the booking engine for you.
The conversion action shows Unverified or No recent conversions until the first real booking from an ad click. This can take up to a day after that booking.
Step 3: Meta pixel
- Open Meta Events Manager with the business account that runs your Facebook and Instagram ads.
- If you have a pixel for your website, use that one. Otherwise click Connect data sources > Web, name the dataset and click Create. When Meta asks how to connect, close the setup: Areca installs the pixel.
- Click the dataset under Data sources and copy its ID from the Settings tab. It is a number of 15 or 16 digits.
In Ads Manager, choose Purchase as the conversion event for campaigns that should bring bookings.
Step 4: Add the IDs in Areca
- Open Settings > Integrations and choose Google Analytics & Meta Pixel.
- Enter what you set up:
- Google Analytics > Measurement ID:
G-XXXXXXXXXX. - Google Ads > Conversion ID and Conversion label: both or neither. Leave them empty if you chose option A.
- Meta > Pixel ID.
- Google Analytics > Measurement ID:
- Click Save changes.
Tracking starts right away for guests who open the booking engine after you save. To stop it, clear the fields and save.
The cookie banner
As soon as any ID is set, the booking engine asks guests about cookies before it measures them. The banner uses your booking engine's colours and names your property, since you are the one collecting the data.
- Accept: Google Analytics and Google Ads measure normally, and the Meta pixel is loaded.
- Reject: Google gets only anonymous pings without cookies (Google's consent mode), and nothing is loaded from Meta.
Both buttons look the same and booking works either way. The choice is remembered on the guest's device. Guests can change it any time with Cookie settings at the bottom of the booking engine.
Mention in your privacy policy that your booking engine uses Google Analytics, Google Ads and the Meta pixel, whichever you set up.
Ads that lead to your website
Guests often click an ad, land on your website and book from there. Google Ads and Meta mark the ad click in the page
address (gclid, fbclid and utm_ tags). The website widget carries these
tags on to the booking engine, also when the guest first looks at a few other pages of your website. You do not need
to set anything up for this.
If you link to the booking engine from your own buttons instead of the widget, or point ads straight at the booking engine, the tags in the ad link reach the booking engine on their own.
Test it
Use a private browser window, and turn off ad blockers while testing, since they block these scripts.
- Google Analytics: open Tag Assistant, click Add domain and enter your
booking engine address. Search, choose a room and book. In Google Analytics, open Admin > DebugView: you should
see
search,begin_checkoutandpurchasewith its value. - Meta: in Events Manager, open your dataset, then Test events. Enter your booking engine address and click
Open website. Accept cookies in the banner, then search and book.
PageView,Search,InitiateCheckoutandPurchaseappear within a few seconds. - Google Ads: Tag Assistant shows the conversion being sent with your ID and label. Google Ads itself only counts bookings that came from a real ad click.
- From your website: open your website with
?utm_source=test&utm_campaign=checkat the end of the address, search in the widget and book. In Google Analytics, Reports > Realtime should show the visit astestand not ascheckout.stripe.comor direct.
Cancel the test bookings in Areca afterwards. Bookings already reported to Google and Meta stay there; they are test data and do not affect your ads.
Why the numbers differ
Google Analytics, Google Ads, Meta and Areca rarely show the same number of bookings:
- Guests who reject cookies are counted only partly by Google and not at all by Meta.
- Ad blockers and some browsers block these scripts completely.
- Each platform credits a booking differently. Meta may count a booking from someone who only saw an ad, Google Ads only one after a click.
- Bookings from channels such as Booking.com, and bookings made at the front desk, are never reported. Only bookings made in your booking engine are.
Your bookings list in Areca is always the complete count.