Signals
Talk to an engineerStart freeSnowplow
Solutions/Industry

Turn more searches into bookings, and sell more per trip.

Signals tells your search, booking flow and CRM what each traveler is doing right now, so they respond while the traveler is still comparing.

Start freeTalk to us
How Signals helps

What travel brands can do with it.

BookingHigher search-to-book rateTravelers run search after search, and the results lag behind what they just tried. Signals tells your search which dates and airports this traveler has tried, so the next results rank for someone flexible on both.How search inputs work →BookingMore completed bookingsA traveler leaves at the payment step, and the follow-up reaches them once they have booked elsewhere. Signals passes it to your site or CRM at once, so the reminder lands while they are still deciding.How booking recovery works →BookingMore bookings from fare alertsA traveler who priced the same route three times this week is waiting on that fare. Signals tells your CRM which route they are watching, so it can send the alert when that fare moves.How fare alerts work →Revenue per bookingHigher ancillary revenueSeat, bag and hotel offers are set before the booking flow knows what trip this is. Signals tells your booking flow this is a family of four, three nights, landing late, so the offer fits.How ancillary offers work →Loyalty and serviceMore loyalty sign-upsA join prompt on the first visit comes before the traveler has reason to say yes. Signals tells your site when someone is booking a second trip this year, so the prompt shows then, not before.How loyalty timing works →Loyalty and serviceShorter handle timesA traveler whose booking failed opens a chat and explains it from the start. Signals hands your assistant or support agent the route, dates and fare from the session, so the first reply is the fix.How support context works →
For your engineers

One SDK, one read call.

We host it, or it runs in your own AWS or GCP account. Signals collects events with its own SDKs, updates what it knows within a second of each event, and answers a read in 6ms at the median and 10ms at p95, in-region.

Read the docs →
const traveler = await signals.getServiceAttributes({
  name: "booking",
  attribute_key: "domain_sessionid",
  identifier: sessionId,
});
// { searches: 9, dates_changed: 2, airports_tried: ["JFK", "EWR"], fare_dropped: true }
Your booking platformasks what this traveler is doing when it renders a page
Search and pricingget this session's searches with each request
Braze, or any tool that takes a webhookgets a message the moment a rule fires
Snowflake, BigQuery or Databricksruns the same definitions over past sessions
Questions

Asked before anyone opens the docs.

Does it replace the booking engine or CDP we run?

No. Your booking engine keeps pricing and selling the trip, and your CDP keeps its audiences. Signals tells them what this traveler is doing right now, such as how many searches they have run and whether a fare dropped out of the booking flow, and they decide what to do with it.

Travelers compare for weeks and rarely log in. What can Signals know about them?

A lot of what matters, because it keys on the session as well as the user. The searches, date changes and airports tried in this session reach your search and booking flow without a login, and a returning visitor on the same browser carries that history into the next visit. When they log in or join the loyalty program, the same definitions run on the user id.

Is this a data platform project?

No. Add the SDK to your site and app and collection starts, so there is no event pipeline to stand up first. Your product team defines what it wants to know about a traveler in the console, and an engineer reads it with one call and deploys it through the CI/CD you have. A coding agent can do most of the wiring, and the docs, MCP server and agent skill are written so it can.

Where does the data live?

In a deployment we host, or in your own AWS or GCP account, with the same architecture either way. Events are validated against your schemas on the way in and remain yours. Snowplow is ISO 27001 certified, and deployments run under GDPR and CCPA, which matters when travelers book from several jurisdictions.

What if next-day data is fine for us?

Then buy a warehouse tool and save the money. If the fare alert can wait until tomorrow and the loyalty prompt can show on the next visit, the batch route is cheaper and we would tell you so. Signals is for the search, booking flow and CRM that have to respond while the traveler is still comparing.

Try it on your own site.

Add the SDK, define one thing you want to know about a visitor, and watch it update while you click around. The free tier runs on the real engine: no card, no sales call.

Start freeTalk to an engineer