Skip to main content
Bokun → AmplitudeIntegration guide

Connecting Bokun to Amplitude

Bokun is owned by Tripadvisor and connects operators to Viator, so it is a distribution network with a booking engine attached rather than the other way round. Amplitude is built around behavioural cohorts, which makes the identity resolution and the event taxonomy load-bearing in a way they never are for an ad pixel. The join between them succeeds or fails on one thing: whether the user ID and device ID pair reaches the Bokun booking before the conversion happens, because Amplitude can only match a conversion it can tie back to a click it recognizes.

Free30 minutesNo obligation

Specific to this pair

Bokun bookings in Amplitude: net revenue per seat, tied to the device

Read the Amplitude device ID before the Bokun widget opens, pass it to your server with the booking reference, and send the booking with participants as quantity, net per-participant rate as price and the Bokun product ID. Send departure date as a property, reseller bookings as a separate event, and cancellations as negative revenue.

Amplitude is only worth wiring to Bokun if someone is analyzing the booking funnel on your own website: which tour pages lead to a widget open, where travelers abandon at date selection, how repeat guests behave. For that the booking event has to land on the same device ID the Amplitude browser SDK assigned on the tour page. Travelers rarely log in to an operator's site, so there is no user ID to merge on until the booking gives you an email. Read the device ID before the widget opens, pass it to your server with the booking reference, and send the booking with it; otherwise the purchase appears on a new anonymous user with no browsing history.

Map the booking to Amplitude's revenue fields deliberately: quantity as the number of participants, price as the net per-participant rate, and productId as the Bokun product ID so revenue splits by tour. Add a channel property set to direct. Reseller bookings never touched your site; if you load them at all, use a separate event type so they cannot inflate funnel conversion rates or cohort value.

The usual breakage is timing. A booking made in March for a July departure is March revenue, so send the departure date as a property for lead-time analysis. A cancellation in June needs its own negative-revenue event against the same booking reference, with a stable insert_id so a notification retry does not create a second refund.

Bokun → Amplitude · what breaks

Why this join usually fails — Bokun → Amplitude

  1. 01

    The user ID and device ID pair never reaches Bokun

    Reseller bookings originate on Viator, GetYourGuide or an agent's system. There is no session of yours anywhere in that chain.

  2. 02

    Distribution revenue attributed to advertising

    Bokun's purpose is to put your product in front of travellers on other people's platforms. That works, and none of it is something your search campaign caused.

  3. 03

    Revenue events that carry no revenue

    Amplitude will happily accept a purchase event with no price field. The event count looks correct, the funnel looks correct, and the revenue reporting stays at zero — which people usually discover a quarter later when someone asks what a cohort is worth.

  4. 04

    Nothing reconciles afterwards

    Amplitude shows the event in the user's activity stream with its properties expanded. Read the properties, because an event that arrives without its revenue fields still looks like a success.

Bokun → Amplitude · the fix

What working looks like — Bokun → Amplitude

  • The user ID and device ID pair on every booking

  • Conversions arriving in Amplitude

    The event lands on the user, joins their behavioural history, and becomes available for cohorts, funnels and retention.

  • Reconciled against the source

Bokun → Amplitude · architecture

How Bokun and Amplitude actually connect

  1. 1

    Bokun holds the truth

    Reseller bookings carry an OTA commission that can reach a quarter of the ticket price. Your net rate and the traveller's price are different numbers and only one of them is yours.

  2. 2

    Amplitude needs a click to match

    Amplitude needs a device or user identifier, an event type and its properties. Revenue events need the price and quantity fields specifically, or the revenue reporting stays empty while events flow normally.

  3. 3

    The identifier is the bridge

    The user ID and device ID pair, captured at the visit and carried into the Bokun booking.

  4. 4

    The event source decides reliability

    Send direct bookings at net value. Never send reseller bookings as conversions.

  5. 5

    Deduplication at the destination

    Amplitude deduplicates on insert_id. Omit it and a retried batch is counted twice, which shows up as a phantom spike that someone will eventually build a hypothesis on.

Bokun → Amplitude · normal or broken

Working vs. broken, side by side — Bokun → Amplitude

Normal, not a fault

  • The user ID and device ID pair present on the booking

  • Sent from the Bokun booking record

  • Deduplicated correctly

    Amplitude deduplicates on insert_id. Omit it and a retried batch is counted twice, which shows up as a phantom spike that someone will eventually build a hypothesis on.

  • Reconciles with the source

Actually broken

  • The user ID and device ID pair missing on most records

    Reseller bookings originate on Viator, GetYourGuide or an agent's system. There is no session of yours anywhere in that chain.

  • Sent from the browser

    Bokun's purpose is to put your product in front of travellers on other people's platforms. That works, and none of it is something your search campaign caused.

  • Counted twice, or not at all

    Amplitude will happily accept a purchase event with no price field. The event count looks correct, the funnel looks correct, and the revenue reporting stays at zero — which people usually discover a quarter later when someone asks what a cohort is worth.

  • Nobody has reconciled it

Bokun → Amplitude · diagnose

Diagnostic order — Bokun → Amplitude

  1. 01

    Count bookings carrying the user ID and device ID pair

  2. 02

    Follow one real conversion end to end

  3. 03

    Split by channel and check whether values are gross or net

    Two questions, both usually answered wrongly, and together they can overstate return by a factor of two.

  4. 04

    Check a purchase event for the price and quantity fields specifically

    Not whether the event arrived — whether the revenue fields are populated, in the exact names Amplitude expects.

  5. 05

    Read the match rate, not the success message

    Amplitude shows the event in the user's activity stream with its properties expanded. Read the properties, because an event that arrives without its revenue fields still looks like a success.

Bokun → Amplitude · prove

How it gets proven — Bokun → Amplitude

Source of truth

Bokun bookings by departure, split into your own website and reseller channels, valued at your net rate.

  • The user ID and device ID pair confirmed present on a live booking.
  • Revenue reconciled per transaction against your billing system, with identity merge behaviour verified across signup.
  • Direct bookings reconciled at net value against imported conversions.

Bokun → Amplitude · free audit

What we check in the free audit

  • Count bookings carrying the user ID and device ID pair
  • Follow one real conversion end to end
  • Split by channel and check whether values are gross or net
  • Check a purchase event for the price and quantity fields specifically
  • Read the match rate, not the success message

Checked against

Bokun bookings by departure, split into your own website and reseller channels, valued at your net rate.

Get my free conversion tracking audit

Free30 minutesNo obligation

Bokun → Amplitude · when not to buy

When you don't need this — Bokun → Amplitude

  • Measure identifier coverage yourself first — pull your last hundred bookings and count how many carry the user ID and device ID pair.
  • An operator selling mainly through Viator has a distribution question, not a tracking question.
  • If nobody is building cohorts or retention analysis, this is a large amount of instrumentation for reporting a dashboard already gives you.

Bokun → Amplitude · what we deliver

What gets built — Bokun → Amplitude

  • Identifier capture into Bokun

    Attribute direct-website bookings only, and report reseller volume as a separate channel at net rate.

  • Event source: the Bokun booking record

    Send direct bookings at net value. Never send reseller bookings as conversions.

  • Dispatch to Amplitude

    The Amplitude HTTP V2 API, posted server-side with the identity, event type and properties.

  • Reversals where they exist

    Cancellations reverse.

Written guarantee

95%+ tracking accuracy

Measured against Bokun bookings by departure, split into your own website and reseller channels, valued at your net rate.. Miss it and we keep working at no cost.

Get my free conversion tracking audit

From $400 · See packages

FAQ

Bokun → Amplitude questions, answered

The server-side booking event was sent without the device ID the browser SDK created on the tour page. Capture it before the Bokun widget opens and send it with the booking reference.

Free · 30 min

Get Bokun and Amplitude joined properly

Free30 minutesNo obligation