That is a real export. The same single HTML file the editor builds for an ad network, animations and all — only the store redirect is held back.
Book The Ride – Fixed Fare
Two stops on a rail, a fare locked at ₹740 against ₹910 at surge, held for two minutes.
What this screen does
The card is built around a single comparison: ₹740 fixed against ₹910 at surge. Naming the surge price is what gives the fixed one meaning — a fare on its own is just a number, while a fare shown beside what it would otherwise cost is a saving the viewer can feel.
Surge is the right thing to attack because it is the category's most resented feature. Riders do not object to paying for a journey; they object to the price changing because it is raining. A product that removes that is selling relief, not transport.
The two-stop rail communicates the journey without a map. It is a small piece of design doing a lot of work — the viewer understands the trip instantly, and the card stays legible at the size an ad actually renders.
'This fare is held for 2 minutes' is short, and correctly so. Unlike a hotel or a flight, a ride is booked in the moment, and the hold has to match the real decision window. A two-minute clock on a ride reads as normal; the same clock on a holiday would read as manipulation.
'Cancel free for 5 minutes · Pay after the ride' means committing costs nothing. Both the money and the decision stay reversible, which is what makes a two-minute deadline acceptable rather than pressuring.
Best for
- Ride hailing, taxi and car service apps
- Airport transfer and intercity services
- Markets where surge pricing is common and unpopular
- Campaigns launching in a new city, where a fixed fare is the entry offer
- Peak-time and bad-weather dayparts, when surge is on people's minds
Making it yours
- Use routes your audience actually travels — airport runs and common commutes outperform invented pairs of places.
- Set both fares to real numbers. The comparison is the card, and an exaggerated surge figure is the fastest way to lose the argument.
- Match the hold and cancellation windows to your app's real behaviour.
- Adjust the payment line if you take payment upfront — do not promise pay-after if you do not offer it.
- Localise currency, place names and typical fares per city.
- The pattern carries to any fixed-versus-variable pricing story: delivery fees, currency exchange, energy tariffs.
Next steps
Templates are a starting point, not a constraint. The documentation walks through changing one into your own ad and exporting it.