The Escapia integration allows you to connect data fields from the unit record in Escapia to Touch Stay and have that data automatically update. This allows you to store data, such as the key code or guest guidance, in Escapia 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 Escapia unit data to your Touch Stay content.
Firstly, you can connect Escapia data to a Touch Stay custom field. This is perfect for short values such as the key code or a WiFi password stored in one of your Escapia custom fields, 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 value 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 Escapia 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 Escapia and especially if that data is not present on every unit, 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 Escapia 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 unit-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 unit in Escapia. 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 unit in Escapia 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 Escapia 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 Escapia.
Hide topic if content is blank - this option is best if the content for this data point is not always present in Escapia and you want the topic to be hidden on those guides with no content. During the sync process, if an Escapia unit 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 Escapia. 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 Escapia the topic will always show on that guide.
Syncing the guide data
The unit data will sync between Escapia 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 Escapia 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 Escapia 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 Escapia
Unit-level fields (guide custom field or topic customisation):
Unit Complex
Detail URL (link)
Web Description
Guest Guidance
Key Code
Notes
Custom 1 to Custom 10
Reservation-level fields (user/guest custom field):
Door Code — if the reservation has no door code, the Kaba lock code is used instead.
Reservation Number
Brivo door code — the last four characters of the guest's phone number.
🤝 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.