StayStrategy

Conversions API for hotels: setup, events and testing

For a hotel, the Conversions API (CAPI) is a way for your booking system’s server to report confirmed direct bookings straight to Meta, so your Facebook and Instagram ads are optimized toward real reservations instead of clicks. It is not a hotel booking API, which is the connection OTAs use to pull room inventory. This guide covers the Meta kind: what to send, how to set it up, how to test it and what to watch on privacy.

TL;DR

  • Conversions API sends events from your server to Meta. The Meta Pixel sends them from the guest’s browser. Most hotels should run both and let Meta deduplicate.
  • The one event that matters most is Purchase, sent only after a confirmed booking, with the revenue value, the currency and a booking reference.
  • Deduplication depends on two things matching exactly: the event name and the event ID on the browser and server copies.
  • Test with a Meta test event code and a real test booking before you trust the numbers.
  • Server-side does not bypass consent. If a guest declined marketing tracking, that choice has to govern what you send.

Table of Contents

Two things people mean by hotel APIs

Search for this topic and most results are about hotel supplier or booking APIs. Those connect a travel agency or booking site to room inventory from bedbanks and distribution systems. They help someone sell rooms. They do not tell an ad platform that a guest booked.

The Conversions API is different. According to Meta’s server-side API specification, each event needs four fields: an event name, an event time, user data and an action source. It is a measurement tool. You use it when you run paid ads on Meta and want the ad system to know which clicks turned into stays.

If you run a boutique hotel, a short-term rental brand or a tour business with its own booking page, this is the version that applies to you.

Why a hotel sends booking events from the server

The Meta Pixel is a snippet of code that runs in the guest’s browser. It works until the guest uses a browser that blocks it, closes the tab before the confirmation page loads or starts the search on a phone and finishes on a laptop. Each of those leaves a hole in your data.

The cost of those holes is practical. A booking engine vendor’s documentation puts it plainly: without a reliable purchase signal, Meta keeps showing ads but optimizes toward clicks or visits, which are not the same as a paid booking. The server-side route lets your system report the purchase directly, without relying on the guest’s browser.

Hospitality has a particular problem here. Hospitality Technology notes that guest journeys span devices, platforms and channels, and that a Conversions API connection can pass a booking back to Meta in real time even if the guest clicked an ad on one device and finished elsewhere. The same piece reports that advertisers using the Conversions API often see double-digit ROAS improvements compared with pixel-only setups, because better data helps the platform find valuable audiences and bid more efficiently. Treat that as a reported industry pattern, not a promise for your property.

If you want the browser side first, our Meta Pixel guide for hotels walks through the pixel setup, events and testing.

What to send: the events that matter

Resist the urge to send everything. A small property needs a short, clean list.

Event When it fires Where it is sent from
ViewContent A guest views a room or property page Browser (Pixel)
InitiateCheckout A guest starts the booking process Browser (Pixel)
Purchase A booking is confirmed Browser and server

This mirrors how one booking engine’s documentation describes its own setup: the Pixel fires PageView, ViewContent, InitiateCheckout and AddPaymentInfo in the browser, while Purchase goes through both the browser and the server, and the Conversions API sends only Purchase. Your booking engine may differ, but the shape is common, and a Purchase-only server feed is a perfectly good start.

Some platforms keep it just as lean. FareHarbor’s help center says that when its Conversions API option is on, it sends a Purchase event each time a customer reaches the booking confirmation page, with value, currency and booking ID, and no other events. For a tour operator, that is often enough.

Rules for the Purchase event

  • Send it only for confirmed bookings. Not for a started checkout, not for an inquiry.
  • Use the real revenue figure. Decide once whether value means room revenue or total with taxes and fees, and keep it the same every time.
  • Include the currency. A missing currency makes the value hard to use.
  • Use the booking reference as the event ID. This is what makes deduplication possible. Heroes PMS documentation describes using the booking reference as the event ID so Meta counts the booking only once.
  • Send it once. One confirmed reservation, one Purchase.

Timing matters too. Meta’s specification says an event time can be up to seven days before the event is sent, and if any event time is older than that, Meta returns an error for the entire request and processes no events. If you batch bookings from a property management system, send them promptly.

How to set up Conversions API

The exact clicks depend on how your site and booking engine are built. The sequence is the same almost everywhere.

Step 1: Check what your booking engine already supports

Many booking engines and property management systems have a built-in Meta connection. If yours does, use it. The setup is a form, not a development project. Look in the engine’s marketing or integrations settings for a Meta Pixel or Conversions API option.

Step 2: Create or open your dataset in Events Manager

In Meta Events Manager, connect web data and create a dataset. FareHarbor’s instructions have you select both the Conversions API and the Meta Pixel, configure the Purchase event with its parameters, then generate an access token and save it somewhere secure.

Step 3: Enter the three values in your booking engine

You will usually need the Pixel ID, the access token and the URL of the website that is the event source. Paste them into the booking engine’s Meta settings. Treat the token like a password. Anyone who has it can send events to your dataset.

Step 4: Confirm the browser Pixel fires the matching event

The Pixel and the server must both send Purchase, with the same event name and the same event ID. If your booking engine handles both, it should do this for you. If you have a separate marketing website and a third-party booking page, make sure the Pixel is on the confirmation step and not only on your homepage.

Step 5: Add customer matching data

Meta needs something to tie an event to a person. For every server event, Meta shows an Event Match Quality score from 0 to 10. FareHarbor says it sends three customer parameters, client IP address, user agent and email, and cautions against adding more for privacy reasons. More matching data tends to improve the score, but only send what you have a lawful reason to send, as covered below.

Step 6: Test before you spend

Run a test booking before you put budget behind any campaign. The next section shows how.

How to test and deduplicate

When the Pixel and the server both report the same booking, you want Meta to count one. The deduplication rule in Meta’s specification is specific: the browser event name must match the server event name, and the browser’s event ID must match the server’s event_id. When a match is found between events sent within 48 hours, only the first one is considered, and if both arrive within five minutes of each other, the browser event is favored.

A test routine for one afternoon

  1. In Events Manager, open the Test Events tab and copy the test event code.
  2. Enter the code in your booking engine’s Meta settings. Heroes PMS recommends putting it on the Meta Pixel card.
  3. Install the Meta Pixel Helper browser extension and load your booking pages. It should show ViewContent and InitiateCheckout firing as you move through.
  4. Complete a test booking.
  5. In Test Events, look for one Purchase that shows as coming from both the browser and the server, with the same event ID and marked as deduplicated.
  6. Remove the test code once you are done, and cancel or label the test booking so it does not sit in your real revenue reporting.

When the numbers look wrong

The Chord diagnostic guide gives a clean checklist for duplicates and overcounting. Confirm that the Pixel and the server are both firing the same event, check that the event ID is present in both and identical, open the Diagnostics tab in Events Manager for deduplication warnings, and use Test Events to look for a single deduplicated instance.

In hotels, the common causes are predictable:

  • The confirmation page generates a new ID every time it reloads, so a guest refreshing the page creates a second Purchase.
  • A reservation with several rooms is counted inconsistently, as one event in the browser and several on the server.
  • A cancellation is sent under an event name that looks like another purchase.
  • Test bookings stay in live reporting.

The fix is a monthly reconciliation. Compare the number of Purchase events in Events Manager with the number of confirmed direct bookings in your booking engine for the same period. They should be close. If Meta shows many more, look for duplicates. If it shows fewer, look for missing events or failed matching.

Why Meta still shows more than your booking engine

Even with a clean setup, Meta will often report more conversions than your own records. One reason is attribution. Meta’s default window counts a booking within seven days of a click or one day of a view, and view-through conversions are included. Compare Meta’s figure to your booking engine’s, not to the other way around, and read our hotel marketing attribution guide for how to reconcile the two. If part of your revenue comes by phone, the offline conversions guide shows how to bring those bookings back into your ad data.

Hashing is part of the mechanism. Meta’s Business Tools Terms, filed as a court exhibit, say that when using the Meta Pixel or other business tools, the advertiser or service provider must hash contact information such as names, email addresses and phone numbers in the manner Meta specifies before sending it. Booking engines that support the Conversions API typically do this for you. Heroes PMS states that customer data is hashed with SHA-256 as Meta requires.

Hashing is not the same as consent. Heroes PMS makes the point that hashing limits what Meta receives, but sending conversion data to an advertising platform is still a processing choice that your privacy policy should mention.

The legal risk in the US is real and has been tested against hotel websites. A March 2025 lawsuit alleges that a major hotel group let social media platforms intercept guest communications, including confidential guest records, without prior consent. The law firm’s advice to hotel website owners was to update the website terms, cookie policy and privacy disclosures, document consent, usually through a cookie banner, and keep trackers off until the user consents.

For server-side events, there is one more step. A HotPilot guide is not cited here, so apply this principle directly: if a guest declined marketing tracking in your banner, that decision has to reach the server that sends the booking event. A banner choice stored only in the browser cannot control what your booking system sends later. Ask whoever runs your booking engine how the consent choice travels into the booking flow.

This is general information, not legal advice. Because rules differ by state and by your guests’ locations, have your attorney review your privacy policy and consent banner before you turn on server-side event sharing.

What to do with the data once it flows

Clean Purchase data changes what Meta can do for you. It can learn which audiences book direct, and it lets you judge campaigns by bookings and revenue instead of clicks. Value-based bidding, which prioritizes people likely to generate more revenue, also depends on accurate values, as the Hospitality Technology article notes.

For a small property with limited traffic, there may not be enough Purchase events early on for Meta to learn quickly. In that case, run your first campaigns with a clean Purchase feed, keep budgets steady and judge results over weeks, not days. Our guide to Meta ads for hotel campaigns covers campaign structure, and how direct bookings drive margin growth explains why the reservation you capture directly is worth tracking so closely.

Where this fits in AI visibility

Tracking tells you which paid clicks became bookings. It does not decide whether a traveler asking ChatGPT or Google’s AI where to stay hears your name. That is a separate job, and the free AI visibility course teaches it step by step for independent hotels, rentals and tour operators.

A short checklist

  • Your booking engine’s Meta connection is turned on, with the Pixel ID, token and site URL entered.
  • Purchase fires from the browser and the server only for confirmed bookings.
  • Both copies use the same event name and the booking reference as the event ID.
  • Value and currency are included and defined the same way every time.
  • A test booking showed one deduplicated Purchase in Test Events.
  • The test code is removed and test bookings are kept out of reporting.
  • Your cookie banner, privacy policy and consent flow have been reviewed by your attorney.
  • Once a month, you compare Meta’s Purchase count with your booking engine.

FAQ

Is the Conversions API the same as a hotel booking API?

No. A hotel booking or supplier API connects a booking site to room inventory. The Meta Conversions API sends your own marketing events, such as confirmed bookings, from your server to Meta so ad delivery and measurement improve.

Do I still need the Meta Pixel if I use the Conversions API?

In most hotel setups, yes. The Pixel captures browser activity such as room page views and the start of checkout, while the server reports the confirmed booking. When both send Purchase with the same event name and event ID, Meta deduplicates them.

Which events should a small hotel send?

Start with Purchase from both the browser and the server, plus ViewContent and InitiateCheckout from the Pixel. Send Purchase only for confirmed bookings, with value, currency and the booking reference. Add more only when you have a reason.

What is Event Match Quality?

It is a score from 0 to 10 that Meta shows for server events. It reflects how well the data you send can be matched to a Meta account. Sending hashed customer details your booking engine already has, such as email, generally helps, within your privacy commitments.

No. Server-side sending is still a form of sharing guest data with an advertising platform. Your privacy policy should describe it, and a guest’s decision to decline marketing tracking should control whether their booking event is sent. Ask your attorney how this applies in your state.

Sources

StayStrategy Editorial articles are general information for hospitality operators and are produced with the help of AI. Platform policies, prices and local rules change, so confirm the details before you act on them.

Get your property ready to be named by AI

The AI Visibility Workbook is eleven printable sheets. When every box is full you have written what a machine needs to be able to name you.

Or check your visibility first. Seven questions, about two minutes.

How to get recommended by AI, the course