Summary

Rushmore is a system that can be used to manage registrations and onsite activities.

SpotMe can retrieve data from this system via Rushmore API.

Installing the Rushmore integration

To install the Rushmore API in your workspace, go to:
Settings > Features, and select data-api-rushmoredigital.

What you will need for the integration

• The Rushmore event ID.
• You need to create at least one participant in the Rushmore system.
• Add “1” in the ”Event app” field for that participant.
  

Rushmore integration credentials

Once you've installed the data-api-rushmoredigital package, go to Integrations > API credentials, and select the Rushmore Digital Credentials.

In the below fields, enter the following information:

• API Endpoint: https://takeda.rd-r.com
• Username: spotme
• Password: fR4@dd5!2dtnD
• Event id: Enter the event ID received by client. This must be all in lower case without any spaces.

Retrieving data

• Data is only synced one way: from Rushmore to Backstage. If you make any changes directly in Backstage, they will be overridden when syncing with the Rushmore API.
• The value “1” must be added  to each participant’s ”Event App” field, in the Rushmore system, to trigger the creation of a new participant in Backstage.
• If a participant does not have the value “1” in ”Event App” field, they will not appear in Backstage.
• If a participant was initially set as "1" in ”Event App” field in Rushmore, created in Backstage, and then set as 0 in the Rushmore system, it will automatically cancel the participant in Backstage.

Displaying an existing metadata

All standard metadata (personal details, flights, transfers, etc.) are created when installing the Rushmore package. They will be in your Excel exports but not displayed in the users module in Backstage.

To display them in the Backstage participant page, do as follow::

1. Go to Data configs > Rushmore digital person.
   
2. Click on the metadata you need and copy the “SpotMe field” value.
   
   
3. Create a new metadata in Backstage using this exact field.
   
   
4. Refresh your page and sync the API.

Note that you can use these metadata without displaying them on Backstage.

Creating a new metadata

You can create new metadata that are specific to your event (e.g. workshop allocation, teams, etc.). These are not standard and you will therefore need to create them manually in the API and in Backstage (metadata manager):

1. Export your report from Rushmore.
   
   
2. In Backstage, go to Rushmore API > Data Configs > Rushmore Digital person.
   
   
3. At the end of the metadata list, click on “+”, to add a new metadata to the API.
   
   
4. Set it up as follow:
   API Field: Use the Title column  from the Rushmore report, copied exactly as it is (respecting spaces and case-sensitive).
   SpotMe field: Name that you will add to the Backstage metadata section.
   
   
5. Create the new metadata in Backstage (metadata manager) using the exact same information as above.
   
   
6. Refresh your page and sync the API.

If you make any changes (either manually or with an XLS import) to data that is imported via API, syncing the data via API would overwrite your changes, even if they are applied to fields that are not mapped. 

To avoid this from happening, do as follows:

1. In Backstage, go to Rushmore API > Data Configs > Rushmore Digital person.
2. Add the metadata that you want to control manually, to the Omit default metadata fields.

This will prevent the fields from being overwritten - i.e. whatever was input manually or via XLS will prevail over the imported data (if any) coming from the API.

Best practices

• Install and test the API early on to ensure everything is working smoothly.
• Set your API as “autosync” if you are planning frequent updates.
• If changes are required, always make them in Rushmore to avoid overriding existing data.
• Double check that all participants have information in their profile before displaying a metadata in a session, page, or message.
• If needed, you can create metadata in Backstage without linking them to the API.