Use the Badge Data CSV Uploader to upload access control data manually. This makes historical check-in and office attendance data more accurate.
Before you start
You need:
- Access to your badge swipe data. Export a CSV file of the data that includes the timestamp and the email address.
- Admin permissions with the ability to manage integrations.
Upload the CSV file
When your CSV file is correctly formatted, follow these steps to get the data into Robin:
- Go to Manage > Integrations.
- Under Add Connectors, search for Badge CSV import. You can also select By category and find it under Access Control.
- Select Set up next to Badge CSV import. The Badge Imports page opens.
- Select Upload CSV. The Import from CSV window opens.
- Select a Location and an Access control vendor.
- Choose a .csv file or drag the file into the CSV file upload section. To start from the correct format, select Download CSV template.
- Review the file for errors.
- Select Import.
Your file appears in the file list with the file name, building and file status. For a file with errors, you can review the errors and, if you choose, force a retry.
You cannot undo a forced retry. Robin processes the file with its errors, and the errors are either left out or can harm your data. To force a retry, type an acknowledgment first.
FAQ
Why should I upload historical badge swipe data?
Badge data from your access control vendor makes check-in and attendance data more accurate. This helps most if your organization uses permanently reserved desks, has low check-in rates or has users who come to the office without a desk reservation.
What errors should I look for?
The correct file format makes sure high-quality data goes into Robin. Use the correct column headers and timestamp format, and valid emails.
Also make sure the user emails belong to valid Robin users, and that each user's default building/location matches the location you upload the file to.
What timestamps are supported?
The upload tool supports the ISO format in UTC (2024-01-01 01:01:01) and the Epoch/UNIX timestamp format.
Why do I need to select a location?
The data is specific to a building, so you must select a location. A common error is a file with too many other locations in it.
How long does it take to process the file?
It can take from almost no time to an hour, depending on the file size. The file status shows as pending until Robin processes it. Then it shows as Completed or with an Error status. If a file shows as pending for more than 24 hours, contact support@robinpowered.com.
Can I upload multiple files?
Yes. You can upload multiple files for multiple locations. The badge imports page shows earlier file names, the building each was uploaded to and the file status.
How do I know when a file was last uploaded?
The Badge Imports page has columns for the time and the uploader.
How does Robin use the data after the upload?
Robin uses the data to create check-ins for the users who swiped their badge, over the date range of the timestamps:
- If a user had a reservation but did not check in to a desk on the date of the reservation, Robin shows the desk as checked in after the fact.
- If a user had no reservation and did not check in to a desk, Robin creates a checked-in visit. The user shows as in the office on that date.
Workplace managers then see this data in basic and advanced analytics, so they can evaluate office occupancy with more confidence.
For more help, or to report a problem this article does not cover, email the Robin support team at support@robinpowered.com.