For GCO, the following credentials are always required:
- LoginId (pre-set - do not edit)
- Password (pre-set - do not edit)
- eventName (ask the GCO project manager on your event - the event name must be entered in the credentials with the exact same spelling and spacing as in GCO's system)
- urlSentLinks (pre-set - do not edit)
2-way sync for Webapp links + event passwords (sent from SpotMe to GCO)
How to Configure
Go to the API Data module > API Credentials. Click on "GCO Credentials".
Edit only the field EventName (see above in 'Credentials' section).
Then go to Preview to check if the credentials are working (please refer to the generic API engine page). If you have trouble previewing participants data with the event name you have received, please confirm the spelling with the GCO project manager, and alternatively, get in touch with the Project and Implementation team.
Sync "GCO People" to pull participants data (GCO -> SpotMe). Then sync "GCO Sent webapp links & event passwords" to return login information for each participant (SpotMe -> GCO). By previewing again "GCO People", you can check that the webapp links and event passwords now appear in the API in "Raw data" (meaning they have been correctly saved into GCO's system).
Fp_ext_id, first name, last name, email address, country, group and registration type are mapped by default. Do not change the mapping for fp_ext_id!
⚠️ Country information is mapped by default to the 'company' field in Backstage to allow the country of the sender to appear in the moderation/chair iPad view of the Q&A. This can be changed manually.
Make sure to check with the GCO project manager as early as possible whether other fields need to be imported: GCO needs to give us specific access to any additional fields, which require a 4-week lead time on their end.
To add mappings, please refer to the Mapping section of the generic API engine page.