Once Admin users have created successful connections to Yardi Voyager and/or Google Analytics, they can backfill most historical data points in Remarkably. ‘Backfilling’ is a term that describes two things: pulling in historical data where it doesn’t yet exist, and overwriting existing data. It’s a great tool to fill in missing data and refresh stale data. However, there are some important things to know about backfilling: tips and limitations.

Usage Tips:

  1. You can backfill missing data, or refresh incorrect data. Examples of each application are below.
    1. Imagine you added a property and made successful Yardi Voyager and Google Analytics data connections on November 1, 2023. You may want to backfill October 2023 as well, so you have a full picture of Q4 2023.
    2. Imagine your leasing team made 3 changes to 2 existing Yardi guest cards on a Tuesday, 4 days after the guest cards were initially captured. It’s now Friday, 3 days after the changes were made. You may want to backfill the past week (7 days) to capture the changes in Remarkably.
  2. Backfilling will overwrite existing data in Remarkably and can’t be undone.
  3. It can take 24-48 hours for Yardi and/or Google Analytics data to match after the first successful connection test. You may want to want 1-2 days between a successful test and your first backfill.

Limitations:

  1. Admin users can backfill up to 31 days at a time. This limit is set to ensure successful incremental data pulls and to avoid PMS timeout errors.
  2. Currently, backfilling is permitted back to January 2022. If you wish to backfill farther back for any given property, please contact support@remarkably.io.
  3. Occupied %, Leased % and Exposed % values can’t be backfilled from Yardi Voyager.
  4. At this time, automated pay for performance actual expense entries can’t be backfilled.
  5. Backfilling success is subject to data availability and data source constraints. In other words, we can’t backfill data that doesn’t exist, and we may not be able to backfill data that’s too complex and requires too much time or server bandwidth, given PMS-side integration constraints.

Troubleshooting Tips:

If Backfilling failed, it could be due to a few things. Here are some possible causes and suggested fixes.

  • Your Yardi Voyager property configuration prevents backfilling with current settings. To adjust your settings, follow these steps:
    • In Yardi Voyager, Navigate to Interfaces > Configuration > Review Interface Vendors 
    • or Review Property > Interface Configuration in your Yardi Voyager account.
    • Select ILS/Guest Card from the Entity Type dropdown list and click Submit.
    • Once the list of available vendors appears in the side menu, select ‘Remarkably Prospects’.
    • On the ILS & Guest Card Configuration page, check the box next to “Export all guest cards, ignore interface association” and click Save.
  • The data source was unavailable at time of backfill request (e.g. the backfill request occurred during a maintenance window, or during issue-related downtime), and should be tried again later.
  • The data requested was too complex / too large to pull in for the time period.
    • You can try backfilling a smaller date range (e.g 1 week instead of 31 days).
  • There was no data available from the data source during that date range.
    • You can try backfilling from a different instance and/or property code.