How Booking, Kayak & Hopper Monetize Connectivity in 2026 (Teardown of What Each One Ships)
Booking.com runs an Airalo-affiliate redirect from a corner of its trip planner. Kayak has no connectivity flow at all. Hopper embeds an eSIM SKU inside its Carrot Cash loyalty rail. Three different bets from the three biggest booking apps. This teardown maps what each ships today, the observable revenue on the table, and what a native attach would earn each one — with the specific integration decisions they'd have to make first.
Summary
Booking.com ships an Airalo-affiliate redirect — the customer becomes Airalo's on click. Kayak ships nothing. Hopper embeds an eSIM SKU in the Carrot Cash loyalty rail with opaque pricing. Three different bets from the top-3, none of them a native destination-scoped attach at booking confirmation. This teardown walks through what each ships today, what a native flow would earn each one, and the specific decisions each would have to make first.
Booking.com: affiliate redirect
Booking.com's connectivity presence is an Airalo-branded card in the 'Trip planner' section on some post-booking screens. Tapping it deep-links to Airalo's checkout inside the Airalo app (or Airalo.com in the browser). The customer completes purchase in Airalo's flow, receives Airalo's activation email, gets Airalo's support if the eSIM fails.
What Booking gets: an undisclosed referral commission per completed purchase (industry standard 8–12% of the eSIM retail price, so $1.44–$2.16 per $18 activation).
What Booking loses: the customer relationship, the activation UX (support tickets route to Airalo — but only after the customer contacts Booking first, wasting Booking's support team's time to redirect), and roughly 60–80% of the potential net revenue on the same surface.
Why they ship this instead of native: classic top-3 dynamics — Airalo already had a Partners deal template, legal signed it quickly, no engineering lift required. The opportunity cost is invisible on any dashboard, so nobody prioritized the native migration.
| Metric | Current (affiliate) | Native attach (est.) |
|---|---|---|
| Click-to-purchase conversion | 12–18% | 58–72% |
| Attach on eligible int'l bookings | 1–2% | 11% |
| Net rev per int'l booking | $0.02–$0.05 | $0.40 |
| Annualized net rev on 380M int'l room-nights | $8M–$19M | $90M |
Kayak: no flow
Kayak's Trips product surfaces destination guides, airport information, and boarding-pass storage — none of them ship a connectivity SKU. This is a structural gap driven by Kayak's meta-search positioning: the transaction lives on the underlying OTA (Booking, Expedia, Priceline), and Kayak doesn't receive the confirmation event that would trigger a native attach.
The workaround Kayak has available: a pre-departure email at T-minus-48-hours, cross-referencing the traveler's saved trip with a destination-scoped eSIM offer. Documented as an underperformer — email-placement attach is 50–70% below checkout-placement in benchmark data — but non-zero, and Kayak's brand + retention story could plausibly clear 3–5% attach at that surface.
What a native attach would require: Kayak would need to convert its Trips product into a first-party purchase surface for the eSIM add-on (independent of the underlying flight or hotel booking). Technically simple against a partner API like YonoSIM — the eSIM is its own SKU, doesn't require the flight or hotel confirmation flow. Politically requires internal buy-in that Trips can carry a real transaction.
Hopper: Carrot Cash embed
Hopper's play is the most creative of the three. eSIM SKUs are available inside the Carrot Cash rewards rail — travelers redeem loyalty currency (partially or fully) toward an in-app-purchased eSIM plan. Activation is native: QR + LPA delivered inside Hopper's confirmation screen, no fourth-party redirect.
What Hopper gets right: the activation surface is first-party, the SKU is in the same purchase context as the underlying booking, the Carrot Cash mechanic drives repeat engagement.
What Hopper gets wrong: the pricing is opaque — expressed in Carrot Cash rather than dollars — which suppresses attach at the top of funnel. Users see "500 Carrot Cash" and skip past because they can't quickly translate that into 'is this a deal'. The estimated attach rate at this surface is 0.7–1.1% of international bookings, roughly 10× below the native pre-selected-card benchmark of 8–14%.
The fix: add a dollar-priced non-Carrot-Cash default variant, keep the Carrot Cash redemption as a secondary toggle. Same integration, same provider, same activation surface — one pricing display change. Attach would likely 4–8×.
Side-by-side: what each ships vs the benchmark
| Capability | Booking.com | Kayak | Hopper | Native benchmark |
|---|---|---|---|---|
| Attach at checkout | No (post-booking only) | No | Rewards rail only | Yes (pre-selected card) |
| First-party activation | No (Airalo email) | N/A | Yes | Yes |
| Dollar-priced (transparent) | Yes (via Airalo) | N/A | No (Carrot Cash) | Yes |
| Destination pre-selected | Partial | N/A | Yes | Yes |
| Owns customer post-purchase | No | N/A | Yes | Yes |
| Estimated attach on int'l bookings | 1–2% | 0% | ~1% | 8–14% |
Where the mid-market wins
The interesting story isn't the top-3 — it's the mid-market. Three apps at 5M–50M annual users have shipped native attach that beats anything the top-3 offers:
- G Adventures. Group-tour operator; issues a shared regional eSIM to every guest on multi-country tours at booking confirmation. Attach rate on international group bookings reportedly clears 20% (single purchase covers 8–14 attachments).
- Wanderlog. Trip-planning app; post-save prompt surfaces a destination-scoped SKU when a user saves a trip with ≥5 days abroad. First-party activation, native confirmation.
- Skyscanner (pilot). 2025 test of a bundled trip-insurance + eSIM add-on on select international routes. Numbers unpublished; the fact that it moved from pilot to expanded rollout suggests it cleared the internal ROI hurdle.
The pattern is that a 2-week integration against a self-serve partner API is trivially approvable at mid-market scale; the same integration at Booking-scale requires a vendor-selection cycle, MSA negotiation, procurement diligence, and a quarter of internal alignment. The mid-market ships while the top-3 stall.
FAQ
QDoes Booking.com sell eSIM directly?
ANo. Booking.com surfaces an Airalo-branded card in the 'Trip planner' section on some post-booking screens that deep-links to Airalo's own checkout. This is an affiliate arrangement — the customer becomes Airalo's, Booking earns a referral commission on completed purchases (undisclosed rate, industry standard is 8–12% of eSIM retail). The eSIM sits inside Airalo's activation email, not Booking's confirmation. Estimated annual referral revenue based on Booking's ~950M yearly transactions is $18–$45M — a fraction of what a native attach would earn.
QDoes Kayak sell eSIM?
ANot as of 2026. Kayak's trips product surfaces travel guides and airport info but has no connectivity SKU, affiliate or native. Given Kayak's meta-search positioning (they hand off the transaction to the underlying OTA), a native attach requires re-architecting the confirmation surface — Kayak doesn't currently see the booking-completion event for third-party bookings. Their most probable path is a pre-departure email attach (48h before travel), which is a documented underperformer (50–70% below checkout placement in benchmark data).
QHow does Hopper's connectivity play work?
AHopper embeds an eSIM SKU inside the Carrot Cash rewards rail — travelers redeem loyalty currency toward an in-app-purchased eSIM plan. The activation is native (QR + LPA delivered inside Hopper's confirmation), but the pricing is opaque because it's expressed in Carrot Cash rather than dollars. The volume is unpublished but Hopper's post-booking Carrot Cash redemption rate is disclosed at ~14% across all SKUs; if connectivity is 5–8% of that, the attach on international bookings likely sits at 0.7–1.1% — well below native-attach benchmarks (8–14%).
QWhy don't more travel apps ship native eSIM attach?
AThree reasons in order of frequency. (1) Provider friction — Airalo Partners' 2–6 week sales cycle keeps prototyping teams from ever hitting an endpoint, and Holafly has no partner program. (2) Perceived operational risk — 'what if the eSIM doesn't work on the customer's phone' becomes a support ticket the travel app owns. (3) Roadmap prioritization — connectivity attach doesn't show up on any leadership dashboard until it's shipped, so it perpetually loses to visible P0s. YonoSIM API removes the first two: public sandbox + automatic refund handle them at the platform layer.
QWhat would a native attach earn Booking.com specifically?
ABooking's public numbers: ~950M room-nights annually, ~40% international (Booking Holdings 2024 Investor Day). That's 380M international room-nights. Applying benchmark 11% connectivity attach on the long-stay-eligible subset (~60%) at $18 avg revenue with 20% partner margin: 380M × 0.60 × 0.11 × $18 × 0.20 = $90M/year in net connectivity revenue. Current Airalo-affiliate estimated take: $18–$45M. Native attach lifts net revenue 2–5× at the same customer surface. The gap is entirely operational, not demand-side.
QWhich travel app has actually shipped a good native connectivity flow?
ASkyscanner (Trip Insurance + eSIM bundle on some routes, 2025 pilot), G Adventures (regional group eSIM issued at booking for multi-country tours), and Wanderlog (post-save prompt with destination-scoped SKU). None of the top-3 US booking apps have shipped native attach in 2026. This is the pattern we see repeatedly: mid-market travel apps (5M–50M annual users) move faster because leadership can approve a 2-week integration; top-3 apps stall in the 6–12 month vendor-selection cycle.
Bottom line
Booking, Kayak, and Hopper are collectively leaving an estimated $110M–$140M/year in net connectivity revenue on the table by not shipping native destination-scoped attach at booking confirmation. The reason is not demand — the benchmark 8–14% attach rate is well documented — it's operational. Provider friction (Airalo's sales cycle, Holafly's missing partner program), perceived operational risk ('what if it doesn't work'), and roadmap-invisibility keep the integration deferred quarter after quarter. YonoSIM API is the direct answer to the first two: public sandbox, automatic refund. The playground at api.yonosim.com/docs is the fastest way to see what the top-3 apparently haven't seen yet.
Back to the Travel apps hub. The integration walkthrough is in the checkout spoke; the attach-rate benchmark data lives in the attach-rate spoke.