OrcLink
← Help Center

Guides

Booking engines: SynXis, Roller, BookNow, AXS

On-site capture on the confirmation page, and back-office reconcile by booking id through the revenue API or CSV.

OrcLink has no native integration with SynXis, Roller, BookNow or AXS. A booking reaches OrcLink in two ways, and you can use both:

  1. On the confirmation page (on-site capture), when the booking engine lets you run your own tags there.
  2. From the back office (reconcile), by sending each booking from the engine's export or your own system.

OrcLink has not checked any of the four engines. Whether its booking pages accept your Google Tag Manager container or a custom script is up to the engine and your plan with it: ask the vendor.

1. On-site capture on the confirmation page

You need the OrcLink script (/t.js) on the confirmation page. Then either:

  • A thank-you page rule (Capture > Rules > Thank-you pages): a page pattern for the confirmation page and, if the address carries the booking number, a parameter such as booking=order_id. See Thank-you pages.
  • A data-layer event through Google Tag Manager: the OrcLink conversion template with order_id (the booking number), and email or phone if the page has them. See Google Tag Manager.

A value on the page is recorded as a claim only; the real amount comes from the back office (step 2).

Engine on its own domain. Many booking engines run on the vendor's domain. OrcLink's cookies from your site are not there. Cross-domain tracking needs the OrcLink snippet on that site and its tracking subdomain under Domains, which a vendor domain usually does not allow. Then use step 2 with the guest's email or phone.

2. Back-office reconcile by booking id

Send each booking (and later changes: cancellations, final amounts) from the engine's export or your own system:

  • Revenue API: PUT /api/v1/revenue/{booking id} with the date, value, currency, and the guest's email or phone (hashed on receipt). See the API reference.
  • CSV upload (Data in > CSV upload, type Revenue): the booking id as the record id, the date, the value, and email or phone. An upload is history: it is never sent to ad platforms, and every upload can be undone.

How a booking finds its click:

  • by the OrcLink click id (olid), if your system kept it;
  • else by the hashed email or phone, when an earlier capture on your site (a form, orc.identify, the confirmation page) tied that email or phone to a click: matched, with click credit;
  • else by lead_id, the booking number your page sent with orc.identify({ externalId }): shown as matched by "order / lead id", with no click credit, and never sent to ad platforms. Send the email or phone too whenever you can.

The record id in the URL is never used to match.

Per engine

EngineWhat to ask the vendorOrcLink path
SynXisCan the booking confirmation page load your GTM container or a custom script? Can you export reservations with a guest email?Step 1 if yes; step 2 with the reservation number and guest email
RollerSame questions for the checkout confirmation page and the bookings exportStep 1 if yes; step 2 with the booking reference and email
BookNowSame questionsStep 1 if yes; step 2
AXSSame questions for the order confirmation page and the orders exportStep 1 if yes; step 2 with the order number and email

None of the vendor features in this table is confirmed by OrcLink.