Maqetin emails new riders who have not taken a ride.
A rider signs up and the first trip does not follow. Maqetin reads the sign-up and the first ride in your app’s events, and emails the riders who have not taken one.
Sample scene: a taxi app in Singapore.
The journey starts when your app sends user.signed_up. It waits 3 days, then checks whether ride.completed arrived since the person entered. If it did, they leave and no email goes. If not, the email goes.
Every trip is a receipt.
It names the one step left before a first ride: a payment method.
- Stop at the first ride. The journey looks for ride.completed since the person entered, so a rider who has taken a ride gets no email.
- Receipts take the send API. A ride receipt sent through the send API reaches riders who opted out of marketing; a journey email skips them.
- One app, many cities. Set a city trait with identify(), and a saved segment on it lets a journey enter only riders in one market.
Hi John,
Your account is ready. Add a payment method once, and your first ride is one tap from the home screen.
Book a rideEvents to send.
Your app sends each one when it happens. The journey above uses the first two.
- user.signed_up
- A person creates an account.
- ride.completed
- A ride ends and is paid.
- ride.requested
- A rider asks for a ride or a rental.
- ride.cancelled
- A ride is cancelled before pickup.
Templates.
No template is written for mobility yet. The gallery lists the templates for other kinds of app.
Browse the templatesStart with the riders who signed up and stopped.
Book a demo and we'll show you Maqetin on rider journeys like yours.