Stova integration

Credentials

For Stova, the following credentials are always required:

• endPoint
• accountid
• key
• eventid
• Active statuses - it is possible to set which participant statuses are imported as active. By default, they are Confirmed and Attended. Statuses need to be comma-separated.
• only_data_modified_up_to_a_day_since_last_sync. Please leave as it is.
• presenterPhotoEndpoint
• personPhotoEndpoint

Endpoint

Stova's endpoint can be found here: https://developer.aventri.com/#api-endpoints

When providing the endpoint in the Stova credentials page in Backstage, please provide it using this format: https://XXX/api/v2, where XXX is the Stova endpoint, for example:
https://api-na.eventscloud.com/api/v2
https://api-apac.eventscloud.com/api/v2
https://api-emea.eventscloud.com/api/v2

Concurrent sessions

It is possible to automatically add master sessions for concurrent sessions that have the same start time. For creating concurrent sessions on the next sync, you need to:

1. Map the `in_slot` field coming from Stova to our own in_slot field:

2. In the API Credentials, enter a new setting called `ConcurrentSessionsTitle` and set the desired title for the master sessions:

Data types

Participants, Session, Presenter, Presenter photos, Person photos, Sponsor, Sponsor levels and Schedule.

Note: Users in Stova with a category.name of “Sponsor” are explicitly excluded from the user sync. Instead of being imported as users into SpotMe, they are imported as sponsors.

How to add credentials

Go to the API Data module > API Credentials. Click on "Stova [UPDATE ME]".

The credentials fields to update are pre-configured: just add the credentials you have received from the provider.

Then go to Preview to check if the credentials are working (please refer to the generic Integration engine page).

Mapping

Users

Do not change the mapping for fp_ext_id and fp_status.

If your Stova attendees uploaded their profile picture in a Stova field of type "Upload file" or "Upload image", you will need to run the Users "preview" in SpotMe, open the report, and note the column name corresponding to this field.

Then, in Backstage, click on the Users data type to open the configuration, and change the mapping of the SpotMe field named "photo" so that it reads data from the Stova field noted previously.

User photos

Once the Users have the “photo" field mapped, you can configure the data type “User photos".

Go to Integrations > Stova > User photos > Type specific configurations, then edit the field “Person photo endpoint". You need to enter one of the following urls depending on the region where your files are stored:

https://na.eventscloud.com/ereg/uploadfiles/

https://eu.eventscloud.com/ereg/uploadfiles/

https://au.eventscloud.com/ereg/uploadfiles/

In order to retrieve User photos, the Users sync should be run before the “User photos” sync.

Utilizing Stova user IDs for QR codes that will be scanned using the SpotMe platform

If you are utilizing user IDs from Stova for your user QR codes or attendee badges, and you intend to scan these QR codes using the SpotMe platform (event check-in, session check-in, lead capturing), you will need to make sure that the Stova user ID is added to the external_qr_value field in the user profile in Backstage.

Read our Using third party QR codes and platforms article to find out how exactly this can be achieved.

Troubleshooting

My sessions are not imported

SpotMe requires sessions in Stova to have a start and end time in order to be imported into SpotMe. Make sure that your sessions have a start and end time, and try importing again.

I get an error message when I try to synchronize users

If when trying to synchronize users you get the following error message “Failure. Internal server error", and you have less then 6'000 attendees in your user list, go to Integrations > Stova > Credentials, and set the Page size option to 300.

If the sync continues to fail, or if you have more than 6'000 attendees, please contact SpotMe support.