How Aakam’s technology could serve travel
Scroll to explore
Travel buyers compare, book once, and are re-acquired at full price the following year. The channel that won them takes its fee whether or not the traveller would have come back anyway.
Where the same problems appear
Aakam does not serve travel today. No operator is a customer and no booking system integration exists. What follows is an argument about which of the three mechanisms would transfer and which would not.
WHERE THE MECHANISMS MEET
The same problems, in a business that is not a store.
Nothing held between tripsShaaaA year passes between bookings and nothing in that year belongs to the traveller. The next trip is a fresh comparison against everyone.What it would do. A balance in the traveller’s own name is the mechanism, and it transfers cleanly. The long gap between purchases is what makes it worth more here than in commerce. Attribution across a long windowRaasidThe research happens weeks before the booking and across devices, so the channel credited is usually the last one rather than the one that worked.What it would do. Capturing the event at source rather than in the browser is the same mechanism; the longer window makes the missing part larger, not different. 
The mechanisms transfer. The booking systems they would have to live inside are the work, and none of that work has been done.
Aakam does not build custom software to order. These are products with their own roadmaps and their own customers; an industry page is an argument about where those products fit, not an offer to build something new.