Why us Easy integration
Developers
Talk to sales
Industries · Travel

Keep travellers engaged between trips

A traveller books once, travels once, then goes quiet until next year. So the mechanics have to survive a gap: collections that never expire, and a tier earned on nights in the last twelve months rather than a calendar year, which means status falls away on its own with no annual reset to run.

The travel cycle

A traveller books once a year and is silent in between

Daily products count sessions. Travel counts trips, and there are only a few a year: weeks of research, one booking, a few nights away, maybe a review, then a long silence. Anything that expires daily is the wrong tool.

one traveller  ·  fourteen months  ·  every event they generated
Fourteen months of one traveller. Fourteen bars, one per month. A few small bars early on are searches and wishlist adds. One tall bar in month four is the booking and the stay. Then seven months in a row with no bar at all, before research starts again. A band over the first twelve months marks the rolling window a tier is counted on. trips, bookings and searches a tier counts the last twelve months Apr Aug Jan Seven of these fourteen months carried no activity at all.

Reading the chart: each bar is one month. The small early bars are searches. The tall bar in April is the booking and the stay. Then seven months carry nothing at all. The band is the last twelve months, the window a tier counts, so status drops on its own as months fall out of it.

Research is loud, commitment is rare

Most of your events are searches and wishlists. One rule can count both and still reward only the booking.

A stay is a shape

Send destination_region and ancillary_type as properties. Each becomes a filter you can use in a rule today.

The day is the wrong unit

Daily missions would expire 340 times a year here. What survives a gap is cumulative progress.

The rule you would build

A tier counts the last twelve months, so status falls away on its own

Most programmes keep an annual total and run a job every January to wipe it, which is both a job to maintain and a cliff your customers resent. Ask for nights in the last twelve months instead and the total falls away by itself, a night at a time.

how this is set up
Match all of the 2 rules below
Match any of the 2 rules below
Sum of nights 25 rolling 365 days
Sum of booking value 6,000 rolling 365 days
Attribute account status = active
Then: the traveller qualifies for the Gold segment · gates Gold-only missions and shelf items
KeyKindWhat it carries
booking value Metric · Currency Money committed at booking, in your base currency.
nights Metric · Number Nights stayed. Send at check-out, so a cancelled trip never counts.
reviews Metric · Number A review submitted. A count, never a rating.
destination region Property · String The geography behind a stay. Filters a passport stamp.
tier Attribute · String Read directly by eligibility rules.

Send us one completed-stay event

Send us the event your platform sends at check-out. We will build a destination collection and a Gold tier in a test account while you watch.