Haven connects to Track natively with a server API key from your Track account. Units, photos, rates, availability, reservations, door codes, reviews, and guest messages sync into Haven, and direct bookings taken on your Haven site are created in Track. Track remains the system of record for your units and your operations; Haven is the branded direct-booking site, checkout, guest guide, CRM, and protection on top.
Early access. The native Track connection is being enabled account by account. If you do not see a Track card with Connect Track under Integrations, it is not on for your account yet: contact Haven support to request it. Until then you can still list your Track units on Haven by connecting through Airbnb.
Haven needs a server key. A channel key (the kind created under Distribution Channels) will not work: it cannot see unit blocks, daily pricing, contacts, or guest messages, and Haven refuses it at connect with a message telling you to create a server key instead.
- In Track, open Configuration → Company Setup → API Keys.
- Click + Server Key.
- Copy the key and its secret. Keep the secret somewhere safe until you have pasted it into Haven.
- Sign in to Haven and open Integrations.
- Find Track and choose Connect Track.
- Enter three things:
- Track domain — the
yourcompany part of yourcompany.trackhs.com. Pasting the full address works too.
- Server key — the server key you created.
- Secret — the secret that came with it.
- Haven checks the key against your Track account. If the domain cannot be reached, or Track rejects the key or secret, the dialog says which, and nothing is saved.
- Every active Track unit starts importing automatically, and auto-import stays on for units you add later. To bring in only some units, turn auto-import off on the Track card and pick the ones you want.
Each Track unit becomes one Haven listing. A complex or building with many units imports as separate listings; group them in Haven if you want a shared site.
One Track account connects to one Haven account. Agencies that run several owners from a single Track account connect it once and assign listings to clients — see Agency Mode.
- Unit content — name, descriptions, address and map location, guest capacity, bedrooms and bathrooms, amenities, photos (in your Track order), house rules (pets, smoking, events, children), check-in and check-out times, check-in details, and directions. Fields Track supplies are locked in the Haven editor so the two never drift.
- Rooms and beds — the rooms and bed types on the unit populate Where you'll sleep on your listing.
- Booking window, cancellation policy, and security deposit — read from the unit and its policies in Track.
- Fees — required fees such as cleaning, linen, resort, community, and pet fees, along with other required charges. Optional fees import as add-ons guests can choose at checkout. A fee Haven cannot price exactly (one scoped to certain dates, stay lengths, or occupancy) is flagged on the listing instead of being charged wrongly.
- Taxes — the taxes configured for the unit mirror into Haven as tax rules. See Taxes.
- Calendar — nightly rates, minimum and maximum stay, arrival and departure restrictions, availability, and unit blocks.
- Reservations — bookings from every channel Track manages, with the guest, guest counts, and the price breakdown (rent, fees, taxes, total). Holds appear as pending reservations and drop off when Track expires them.
- Door codes — the access code Track assigns to a reservation shows in Haven for that stay. Track keeps issuing the codes.
- Reviews — guest reviews with public text import as testimonials you can feature on your site.
- Guest messages — messages guests send in Track arrive in Haven Messages.
- Guests — the guest on each Track reservation is added to the Haven Guests tab.
- Unit custom fields — the custom fields you define on units in Track are available as shortcodes in Haven messages, filled in with that unit's value when a message is sent.
- Direct bookings taken on your Haven site are created in Track as confirmed reservations, marked as coming from Haven and carrying your Haven reservation code. Haven sends its own price breakdown — the nightly rates, the fees, and the total the guest paid — so Track records what was actually charged.
- Pending requests — a booking request you have not answered is sent to Track as a hold only when Hold dates for pending requests is on; otherwise the hold is created the moment you approve the request. The guest's payment confirms the hold in Track; declining the request releases the dates. Track expires a hold on its own schedule (set by your guarantee policy): if that happens before the guest pays, Haven creates the booking in Track afresh at payment time.
- Returning guests — before creating the booking, Haven looks the guest up in your Track contacts by email, then by phone, and books against the existing contact when there is one, so a repeat guest does not become a duplicate contact. When the same phone number belongs to a different contact, the note on the reservation says so.
- Cancellations made in Haven cancel the reservation in Track.
- Guest messages you send from Haven, including automatic guidebook sends, go out through Track on the channel the guest booked through.
- Reviews collected by Haven for a Track stay are posted to Track.
- Rates, stay rules, and blocks — only when you make Haven the calendar source of truth for a listing with Manage pricing in Haven. Haven then writes nightly rates, minimum stays, and arrival and departure restrictions to Track, and blocks you create in Haven become Track unit blocks. Releasing a block removes only the blocks Haven created.
Track does not send webhooks, so nothing arrives instantly. Haven checks Track on a schedule instead:
| What | How often Haven checks |
|---|
| Calendars, availability, reservations, and guest messages | About every 10 minutes |
| New units (when auto-import is on) | Approximately hourly |
| Unit content, photos, fees, and taxes | Approximately every 6 hours |
| Reviews | Approximately every 12 hours |
A change made in Track can therefore take up to that long to appear in Haven. When you need it sooner, click Sync now on the Track card under Host Dashboard → Integrations; it pulls units, photos, calendars, and reservations for that account right away.
Bookings going the other direction do not wait for a schedule. A Haven direct booking is sent to Track as soon as it is confirmed.
See How Syncing Works for the full picture across providers.
- Edits to unit content made in Haven. Track owns unit content, so descriptions, photos, amenities, and fees flow one way: from Track into Haven.
- Card and payment data. Guests pay through Haven's Stripe checkout. No card details are sent to Track, and the payment will not show as collected inside Track.
- Guest-count changes made in Haven. Changing the dates of a booking in Haven moves the reservation in Track, and early check-in or late checkout purchases set the reservation's times there; a change to the number of guests does not travel, so update that in Track as well.
- A standalone contact sync. The guest travels to Track with their booking. Haven does not push its wider guest list into Track's CRM, and it does not import Track contacts that have no reservation.
- Lock commands. Haven reads the door code on a reservation. It does not lock, unlock, or program locks; Track and its lock integrations keep doing that.
- Owner statements, accounting, housekeeping, and maintenance. Those stay in Track.
Your Haven AI assistant can answer guests who booked a Track unit on Airbnb, Vrbo, or another channel. Choose Draft for approval or Send automatically under Communication → Message automations. Replies go out through Track on the channel the guest booked through. Because Track sends no webhooks, Haven sees a new guest message on its next scheduled check — about every 10 minutes — and the reply follows then, not within seconds. See AI replies to OTA guests.
Disconnect on the Track card stops syncing and removes the stored key from Haven. Imported listings stay in Haven. The server key itself remains valid in Track until you delete it there, under Configuration → Company Setup → API Keys.
- Rotating the key. Create a new server key in Track, then reconnect with it in Haven. Your listings and reservations stay linked because the connection is tied to your Track domain, not to the key.
- If Track rejects the key later. Haven marks the connection as needing attention and asks you to reconnect; syncing resumes once a working server key is entered.
- Several rate types. Haven reads the rate type Track selects by default for the unit, and writes to that same rate type when you manage pricing in Haven.