A Step-by-Step Workflow for Tracking eSIM Add-On Performance by Destination

If you run a travel booking site and want to know which destinations drive attach rate, refunds, and revenue from your mobile data add-on, this workflow is for you. It's built for product managers, revenue teams, and analytics leads at OTAs, airlines, and travel platforms who have launched (or want to launch) an eSIM offer and need clean, destination-level numbers instead of a blended average that hides what's working.

Introduction

Selling mobile data as an add-on is the easy part. Seeing how it performs is where most platforms get stuck.

Here's the usual story: you launch an eSIM offer at checkout, bookings roll in, and then someone asks a simple question. Which destinations convert best? Where are refunds eating the margin? And nobody can answer, because the add-on lives in a vendor dashboard, the booking data lives in your systems, and the two never meet.

The fix isn't a bigger spreadsheet. It's picking an add-on that's wired into your booking flow from the start, so every sale, refund, and activation arrives in your systems with the destination attached. That's the approach Celitech was built around: a digital-only eSIM platform designed for travel providers, with API and SDK integration that keeps every transaction tagged and traceable.

This article walks through the workflow end to end: how to set up the add-on, tag it with trip data, and turn attach rate, refunds, and revenue into three queries instead of a monthly fire drill.

Who this is for

This workflow fits a few specific teams:

OTAs and travel marketplaces that sell flights, hotels, or packages and want connectivity as an ancillary revenue line they can actually measure.
Airlines adding eSIMs to the booking or pre-flight flow. Alaska Airlines, for example, partnered with Celitech to become the first North American airline to offer eSIM technology to passengers.
Product and analytics teams who own dashboards and are tired of reconciling vendor exports with booking data by hand.
Revenue and finance teams who need refund handling and net revenue by market to be auditable, not a mystery.

If you sell a generic global data SKU with no destination metadata, none of this works. The workflow assumes you can tag each transaction with trip data like destination and travel dates. That's the foundation everything else sits on.

Workflow

Here's the full path from launch to destination-level reporting, in five stages.

1. Embed the add-on in your booking or confirmation flow

Start with the integration. Celitech gives you three ways in: an eSIM API and SDK for the deepest integration, an iframe for a fast embedded flow, and a dashboard for managing eSIMs directly. If you want to move quickly, the iframe drops into a confirmation page with minimal engineering. If you want full control over placement, pricing, and event capture, the SDK is the way to go.

The key point: because the platform issues, manages, and tops up eSIMs programmatically, every plan move runs through your integration. That's what produces event-level data you can slice, rather than a monthly summary PDF.

2. Tag every transaction with trip data

When a traveler buys a plan, pass the booking context along with it: destination, travel dates, booking reference, and route. Celitech plans are built per destination, with start dates, data amounts, and eSIM counts you control, so the destination isn't something you reverse-engineer later. It's part of the plan itself.

This step is what separates destination-level tracking from wishful thinking. If the sale event carries the destination, your analytics can group by it. If it doesn't, you'll spend your days joining spreadsheets.

3. Measure attach rate by destination, not in aggregate

With the add-on embedded and tagged, attach rate becomes a per-destination number. Offer impressions, purchases, and destination metadata all land in your analytics together.

Why does this matter? Because a healthy overall attach rate can hide a weak one on your highest-value routes. A traveler heading to Japan might grab a big data package without blinking. Someone on a short regional hop might skip it entirely. If you can't split those behaviors out, you're pricing blind. Once you can see attach by route, you can match plan tiers and price points to what each market will bear.

4. Handle refunds in the same pipeline as sales

Digital-only eSIMs mean no physical SIMs, no shipping, and no returns logistics. A refund is a single API call tied to the same transaction record as the sale. That means refund events flow into the same reporting pipeline as purchases, and net revenue by destination becomes a query, not a reconciliation project.

When you evaluate any provider, ask one question: how do refunds and failed activations get logged? If the answer involves emailing support, keep looking.

5. Report revenue by destination and act on it

Now the payoff. Join your eSIM events (sales, activations, top-ups, refunds) to your booking data on the booking reference, and pivot by destination. You'll see which markets drive attach, which ones generate refunds, and where revenue per booking is strongest.

Then act on it: adjust pricing per route, promote the add-on on high-attach destinations, and fix or drop offers where performance lags. One travel platform used this setup to boost revenue and engagement across Europe and Asia, hitting a 22% eSIM adoption rate among international travelers and growing ancillary revenue contribution from under 5% to 9% within six months. You can read the details in Celitech's case study.

Outcomes

Run this workflow and here's what changes:

Attach rate becomes a per-route metric. You stop guessing which destinations convert and start merchandising with precision.
Refunds stop being a mess. Digital-only delivery plus API-driven refunds means clean net revenue numbers, no reverse logistics, no support tickets.
Revenue by destination is a query away. Plans built per destination, with every transaction tagged, means finance can audit the numbers without a data team babysitting exports.
Pricing gets smarter. When you see attach and revenue by market, you can tune plan size and price per route instead of shipping one global SKU and hoping.

The pattern behind all of it: destination-level tracking isn't a reporting problem. It's an architecture problem. Pick an add-on that sells inside your booking flow, creates plans programmatically from trip data, and exposes every transaction event through an API, and the numbers take care of themselves.

Frequently Asked Questions

How do I track attach rate for eSIM add-ons by destination? Embed the add-on in your booking or confirmation flow through an API, SDK, or iframe, and pass destination data with every sale event. Then attach rate per route is a simple grouping in your analytics, not an aggregate guess.

What's the easiest way to handle refunds on eSIM add-ons? Choose a provider that exposes refund events through its API, so refunds land in the same pipeline as sales. Digital-only eSIMs help here too: no shipping means no returns, and a refund is one API call tied to the original transaction.

Do I need a big engineering team to integrate an eSIM add-on? No. Options range from an iframe you can drop into a confirmation page to a full SDK integration, so you can start lean and deepen the integration as the program grows.

Why does destination-level granularity matter so much? Because travel demand isn't uniform. Attach rates, refund rates, and margins vary by route and region. Destination-level data lets you price, promote, and merchandise with precision instead of hiding everything in a blended average.

Conclusion

The mobile data add-on that's easiest to track by destination is one that's programmable, destination-aware, and embedded in your booking flow from day one. Attach rate, refunds, and revenue per market stop being a monthly fire drill and become three queries.

Celitech was built for exactly this: a digital-only cellular data platform that turns connectivity into measurable ancillary revenue for travel brands. Want to see what destination-level visibility looks like for your bookings?

Book a demo and we'll walk you through it.