Skip to main content

Guide level data mapping with Streamline

The Streamline integration allows you to connect data fields from the property record in Streamline to Touch Stay and have that data automatically update. This allows you to store data, such as the WiFi password, lock box code or property description, in Streamline and have that sync to Touch Stay for the relevant guides. Depending on the type of information that you wish to sync, there are 2 different ways to connect your Streamline property data to your Touch Stay content.

Firstly, you can connect Streamline data to a Touch Stay custom field. This is perfect for things such as the WiFi password, where you will want this on all of your guides and as part of a larger topic. You then add the custom field into your topic content and the WiFi password will show in the relevant guide correctly. You can learn more about using field codes in Field Codes Explained.

The second option is to connect Streamline data to a Touch Stay topic and automatically create a customisation for that topic for the relevant guide. This can be combined with setting a visibility rule to only have that topic show on guides where there is data present. This option is more suitable for longer form content in Streamline and especially if that data is not present on every property, such as specific appliance or amenity instructions.

Table of contents:


Setting up new data mappings

You create new data mappings from the Map data tab of the Integrations page by clicking Add new mapping. From here, choose the data in the Streamline data field picker that you would like to map to Touch Stay.

  • If you pick a reservation-level field, you go straight to choosing a user/guest custom field (linked to your invitations).

  • If you pick a property-level field, you'll see Choose mapping type, with the options Guide custom field or Topic customisation.

If you select Guide custom field, you can choose an existing custom field code or create a new one by using the "+ New custom field" button, giving it a name and any substitute value. Substitute values are used in the case of data missing when the field code is used; see Field Codes Explained for more detail about field codes.

If you select Topic customisation, you can then select the topic to map this data to (the dropdown allows searching too, just type the topic name). This will then create a customisation for that topic on each guide with the relevant content from each property in Streamline. The final option is to set any visibility override rule required for this data. This rule is applied to each guide every time the data syncs. There are 3 options, and the choice depends on whether this content is present on every property in Streamline and your preferred tag setup:

  • None - each time the data syncs, the topic's visibility on that guide is set back to normal, so it shows based on its active tags. Any Always Show or Always Hide you set by hand for that topic on that guide is replaced. Use this option if the data will always be present in Streamline or you have a generic version of the content for that topic added to Content Hub which you would like to show in the absence of specific content in Streamline.

  • Hide topic if content is blank - this option is best if the content for this data point is not always present in Streamline and you want the topic to be hidden on those guides with no content. During the sync process, if a Streamline property has no data for the mapped topic then the visibility override rule will be set to Always Hide and the topic will not show on that guide. Otherwise, the topic's visibility is set back to normal.

  • Show topic if content is not blank - very similar to the above option but it works the opposite way and sets Always Show on topics for a guide if they have some content in Streamline. Otherwise, the topic's visibility is set back to normal. Use this option if you set your optional topics to have no tag in Content Hub, then when data syncs from Streamline the topic will always show on that guide.


Syncing the guide data

The property data will sync between Streamline and Touch Stay automatically once every 24 hours, but you can also manually trigger the sync to run at any time.

There is a Resync guide data button on the Map data tab (just under the Streamline logo) which will sync data for all guides and all data. This may take some time if you have many guides and many data points mapped.

Resync a single guide (legacy Hub only): go to Guides, open the guide, open the Guide Details tab, click Edit on the Streamline Integration card and click Resync guide data. The new Hub doesn't have a single-guide resync, so use the Resync guide data button on the Map data tab instead.


Data sources in Streamline

Built-in property-level fields (guide custom field or topic customisation):

  • WIFI Name

  • WIFI Security Key

  • Description

  • Short Description

  • Comment

  • Lock Box Code

  • Lock Box Directions

  • Virtual Tour URL (link)

  • Floor Plan URL (link)

  • Flyer URL (link)

Streamline custom fields

Property custom fields you've set up in Streamline (for example Trash pick-up, Pool code or Parking pass) are also listed as property-level fields. The list is read from your first imported property, so a custom field that only exists on other properties may not appear.

Reservation-level fields (user/guest custom field):

  • Number of Guests (Number)

  • Pets (Yes/No)

  • Confirmation ID (Number)

  • Location Name (Text)

  • Lock Code (Text)

Lock Code is filled in with the first value Streamline has for the reservation from these fields: Reservation: Dack ID, Reservation: RemoteLock ID, Reservation: Lynx Code, PointCentral, RemoteLock or KABA.


🤝 Need help?

Our Fin AI assistant is available 24/7 and typically responds in under 10 seconds. If Fin isn't able to solve your issue, our support team will take ownership of your case from there.

You can also reach out to our team at [email protected], and we'll be happy to help.

Did this answer your question?