How data moves through Stampede
When a guest does something at your venue, it is recorded once and shared with every part of Stampede at the same moment. That is why the profile, your marketing and your reports all agree, without imports or connectors.
When you'd use it
To understand why a booking, a Wi-Fi sign-in or a paid bill shows up everywhere at once, and what that means for the way you run marketing.
How it behaves
Most venues run five or more systems that each keep their own copy of a guest. They are joined up by nightly exports, connectors or someone copying data by hand, so each copy is always slightly out of date and rarely agrees with the others.
Stampede works the other way round. Every guest action is published once, as it happens, and each part of the platform that cares about it picks it up straight away. Nothing is copied between systems later, because there is only one system to begin with.
Take one guest, Sarah, on one evening:
She books a table. The booking is confirmed and the moment is shared across the platform. Her profile gains the reservation, her confirmation email goes out, and the booking appears in reporting.
She connects to the Wi-Fi. The sign-in lands on the same profile, matched on her email, and counts as a visit. If this is her first sign-in, a welcome journey can start.
She pays at the till. The closed bill adds her spend and what she ordered. Loyalty points are earned on the spend, and the revenue is credited to the campaign that brought her in.
She leaves a review. The rating and its sentiment attach to her profile, and a follow-up can be sent based on it.
None of those steps waited for the one before it to be synced. Each one was shared as it happened, and every part of Stampede reacted to it in parallel.
Configuration and options
- Recorded once
- Each guest action is captured a single time, at the source, never re-keyed or re-imported.
- Shared as it happens
- Every part of the platform that needs the action receives it straight away, rather than on a schedule.
- One record
- Everything lands on the same guest profile, matched on email and phone.
- Reacts in parallel
- A single booking can update the profile, send an email, award points and feed reporting at once.
- Consent travels with it
- A guest's email and SMS permissions sit on the profile, so a change applies everywhere instantly.
- Grows with each module
- Turning on another part of Stampede adds its activity to the same stream, with nothing to map.
Good to know
Matching uses email and phone. A guest who signs in to the Wi-Fi with one email and books with another shows as two profiles until a shared detail links them.
A Wi-Fi sign-in without marketing consent is still counted as a visit, but the guest is not added to your marketable list.
Most workflows start the moment their trigger happens. Date-based ones, such as birthdays, run on a daily check instead.
Because data is never copied between separate systems, there is no sync to fall behind and no reconciliation at the end of the month.
The data is yours: held in the UK and exportable at any time.