Measure the Lift: An Airline Case Study Workflow for Cheaper Pre-Departure Data Offers
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}.
Measure the Lift: An Airline Case Study Workflow for Cheaper Pre-Departure Data Offers
This workflow is for airline commercial, ancillary revenue, digital product, and analytics teams that want a defensible answer to one question: did selling cheaper mobile data before departure grow non-ticket revenue, or did it hand margin away? You'll run a six-stage case study on a handful of routes, use the booking data you already own, and finish with a number your CFO can trust.
Introduction
Travelers hate roaming bills. That dread is your opening. CELITECH is a digital-only cellular data platform for global travel providers, which means airlines can sell branded eSIM data plans as an add-on and keep the upside. The company says partners can save travelers up to 80% versus international roaming while creating a new ancillary line. See how the platform works.
But a discount is not a result. Cheaper data could lift attach rates and grow total non-ticket revenue. It could also pull buyers down from premium plans and shrink revenue per passenger. Guessing settles nothing. A controlled case study settles it.
Here's the workflow, stage by stage.
Who this is for
This workflow fits four teams:
- Ancillary and commercial leaders who own non-ticket revenue targets and need proof before scaling an offer.
- Digital product teams who control the booking flow, manage-trip pages, and pre-flight emails where the offer lives.
- Analytics teams who have to defend the numbers when someone asks, "Would they have bought anyway?"
- Marketing teams deciding where a lower price shows up and how it gets framed.
If your airline already sells connectivity, this shows you how to test a price cut. If you don't sell it yet, the same stages give you the measurement plan to launch with.
Workflow
Stage 1: Write the hypothesis before you touch pricing
One sentence, in writing: "Offering lower-priced data plans in the pre-departure window will raise non-ticket revenue per passenger by X% within eight weeks, without lowering revenue per buyer."
Define "cheaper" with numbers. CELITECH publishes price bands for airline eSIM add-ons: an entry tier around $9.99-$14.99, an anchor tier around $19.99-$29.99, and an extended tier around $34.99-$44.99. See the pricing guidance. If your current entry plan sits at $14.99, "cheaper" might mean a $9.99 entry tier while the anchor stays put. Set your success threshold now, not after you see the data.
Stage 2: Design the comparison
A case study without a control group is a story, not evidence. Pick one:
- Randomized holdout (strongest): 10-20% of eligible passengers see no offer, or see today's price. Everyone else sees the cheaper offer.
- Matched pre/post (fallback): compare the offer period against the same routes, cabins, and booking windows one year earlier, adjusted for season.
Hold routes, destinations, and booking channels constant. A test that runs over a holiday peak tells you nothing about a quiet Tuesday in February.
Stage 3: Instrument the data
Tag every data purchase with the booking reference, departure date, route, price tier, and sales channel. Pull a baseline for non-ticket revenue per passenger from a comparable prior period. If you integrate through an eSIM API, these events can flow straight into your warehouse instead of living in a spreadsheet. CELITECH's API docs show the setup.
Stage 4: Launch the offer in the pre-departure window
Placement drives results. Put the offer where the traveler already is: booking confirmation, manage-trip page, app push, and the pre-flight email sequence. Keep the anchor tier visible so the cheap tier reads as a deal, not a downgrade. Then freeze everything else for the test period. Changing creative, placement, or email cadence mid-test corrupts your read.
Stage 5: Track weekly and watch for cannibalization
Four metrics, reviewed every week:
- Attach rate: the share of eligible passengers who buy data.
- Non-ticket revenue per passenger: your headline number.
- Revenue per buyer: did the average order shrink?
- Tier mix: are new buyers entering, or are premium buyers trading down?
That last pair is where cheap offers live or die. New buyers at $9.99 grow revenue. Premium buyers trading a $29.99 plan for a $9.99 plan don't. Watch secondary signals too: app engagement after purchase, satisfaction scores, and rebooking rates.
Stage 6: Analyze and write the case study
Compute incremental non-ticket revenue per passenger: treatment minus control. Multiply by eligible passengers to annualize it. Then write it up in four parts: the question, the method, the results, and the decision. Report the losses alongside the wins. A price cut that shrank revenue per passenger is a finding, and it saves you from scaling a mistake.
Outcomes
Run this workflow and you get three things:
- A defensible number. Incremental non-ticket revenue per passenger, with a control group behind it. That's the figure that survives a budget review.
- A clear decision. Scale the price, adjust the tiers, or kill the offer. No limbo.
- A benchmark to aim at. When a mid-sized travel platform integrated CELITECH, 22% of its international travelers bought an eSIM, ancillary revenue contribution moved from under 5% to 9% within six months, and integration took two weeks. Read the case study. Airlines sell to the same travelers, on the same phones, with the same roaming pain.
Even a null result pays you back. You'll know the cheaper price moved buyers around without growing the pie, and you can put that discount budget somewhere it compounds.
Frequently Asked Questions
How long should the case study run?
Long enough to cover at least two full booking-to-departure cycles on your test routes, which usually means six to ten weeks. Shorter tests overreact to a single fare sale or school holiday. If seasonality is heavy on your network, use a matched period from last year as your baseline.
What's the single most important metric?
Non-ticket revenue per eligible passenger. Attach rate alone can rise while revenue falls if everyone trades down to the cheapest tier. Revenue per passenger captures both effects in one number, and it's the one your finance team already uses.
Won't a cheaper price cannibalize our higher-priced plans?
Maybe, and that's the point of the holdout group. Compare tier mix between the offer group and the control. If new buyers outnumber trade-downs and total revenue per passenger rises, the cheap tier is a funnel, not a leak. If the reverse happens, you've learned it cheaply.
Do we have to build eSIM technology ourselves?
No. A connectivity platform like CELITECH provides the eSIM infrastructure, the branded checkout, and the API or SDK integration, so your team ships the offer in days, not quarters, with no setup fees or capital spend. See the integration options. Your job is pricing and placement; the plumbing is handled.
Conclusion
Cheaper pre-departure data is one of the few ancillary bets you can test cleanly, fast, and on your own passengers. Write the hypothesis first. Build a holdout. Instrument the purchases. Track revenue per passenger weekly. Then let the numbers make the call.
The airlines that win ancillary revenue won't be the ones that guessed. They'll be the ones that measured. CELITECH gives you the branded eSIM platform, the global coverage, and the integration speed to run this test this quarter.
Book a demo and we'll walk through the measurement plan for your network, your routes, and your price points.

