Skip to main content

Guide level data mapping with OwnerRez

The OwnerRez integration allows you to connect OwnerRez booking and property data, including any custom OwnerRez data fields (called 'custom field definitions'), to Touch Stay and have that data automatically populated in your guides and invitations.

There are 2 different ways to connect your OwnerRez property data to your Touch Stay content.

1. Connect OwnerRez data fields to Touch Stay custom fields. This is perfect for things such as the WiFi password, that you will want on all of your guides as part of the WiFi topic. Once the data field is mapped in Touch Stay, you simply add the custom field into your topic content and the WiFi password will change dynamically for each guest based on the property they are staying at. You can learn more about using field codes in Field Codes Explained.

2. Connect OwnerRez data to Touch Stay topics 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 OwnerRez 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

Go to Integrations > Map data and click Add new mapping. From here, choose the data in the OwnerRez data field picker that you would like to map to Touch Stay.

  • If you pick a booking-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 OwnerRez. 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 OwnerRez 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 OwnerRez 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 property specific content in OwnerRez.

  • Hide topic if content is blank - this option is best if the content for this data point is not always present in OwnerRez and you want the topic to be hidden on those guides with no content. During the sync process, if an OwnerRez 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 OwnerRez. 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 OwnerRez the topic will always show on that guide.


Syncing the guide data

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

To force a sync, go to Integrations > Map data and click the Resync guide data button. This syncs all guides, and the time it takes will vary based on how many guides and fields you have mapped.

Resync a single guide (legacy Hub only): go to Guides, open the guide, open the Guide Details tab, click Edit on the OwnerRez 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 OwnerRez

Built-in booking-level fields (mapped to a user/guest custom field):

  • ID, Adults, Children, Infants, Pets, Total Guests (Number)

  • Lock Code, Form Key, Listing Site, Notes, Guest Full Name, Booking Date, Lease Link (Text)

  • Total Rent, Total Surcharge, Total Tax (Text)

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

  • Number of Bedrooms, Number of Bathrooms (Number)

  • Property URL (Text)

Custom field definitions

Any 'custom field definitions' that you have created in OwnerRez are also listed in the picker (up to 100 definitions), as text fields. There are two types:

  • Booking information links to invitations created when you have synced bookings with your Touch Stay account. This data dynamically adjusts for each guest.

  • Property information can be mapped to your guides, to save recreating information about your properties that you have already added in OwnerRez.


🤝 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?