Follow

Lanyon Integration

Please note that Lanyon is owned by Cvent and both clients and provider refer to it as Cvent. However, it is a different provider with a different integration.

Credentials

For Lanyon, the following credentials are always required:

- apiToken

- endPoint

Data types

Supported data types are:

- Person

- Presenter

- Presenter Photos

- Session

- Tags

- Locations

- Schedule (for session registrations - aka 2-way registration), it requires both session and person data to be already synced

- Bookmarks (for saved session on Lanyon), it requires both session and person data to be already synced

- Sponsor

- Sponsor Logos

2-way registration

2-way registration means that when the user tries to register in the app to a session by clicking on the 'Register' button, our system confirms with the provider if we can register the specific user to the specific session.

Based on the response we get from the provider the user is registered or not to the session.

The best way to test is to confirm with the client which user can be used for testing and then register to a session.

Session targets

There are 4 fields that trigger session visibility, for both sessions and users.

1. PublicViewPublicSchedule

= sessions without any logic value for publicviewprivateschedule, overall_privateviewprivateschedule,privateviewprivateschedule, cannotvieworschedule

The session has no restrictions on Viewing (Public Information) and session has not restrictions on Scheduling (Public information). There is nothing required on user or session record. Every use can see and enroll. We do not receive a filed for Publichviewpublicschedule

2. PublicViewPrivateSchedule

Session has no restrictions on Viewing (Public Information), but session has scheduling restrictions. Privately it can be scheduled. For scheduling to happen both user and session have to have same matching flag. We are not checking flags on user or session record whether to display the sessions, we are just checking flags on user and session record to schedule.

Every user can see and we have the option to register - if the user tries to enroll, we call Cvent and you will pass the information whether the registration is confirmed or not.

This means no targets, the sessions are visible to all users with open registration

3. PrivateViewPrivateSchedule or Overall_PrivateViewPrivateSchedule

Sessions is not visible for Viewing (Public Information), but rather only visible for viewing Privately. If user and session have a matching flag, that session becomes Visible and session attendance can be Scheduled. Most restrictive.

The session is only visible, with the option to register, for users with a matching value

No session currently as simply PrivateViewPrivateSchedule, we should use {[overall_PrivateViewPrivateSchedule}}

4. CannotViewerSchedule

Session is not to be shown or available for scheduling. We need a matching flag on both user and session record, but you can think of this mode as hiding session for that specific user. If there is matching value, the session is not visible. If there is no matching value, the user sees the session and can (un)register.

How to configure

Credentials

Go to the API Data module > API Credentials. Click on "Lanyon Credentials [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 API engine page)

Concurrent Sessions

By default, master sessions are created for concurrent sessions that have the same start time. The wording `Concurrent Sessions` can be changed in credentials

If this functionality is not desired, you need to:

1. Unmap the `in_slot` field coming from Hubb to our own in_slot field:

Inslotmapping.png

2. In the API Credentials, remove `ConcurrentSessionsTitle`:

Concurrentsessions.png

Remove outdated data

  • For participants:

`Remove outdated data` is selected by default. This means that the items deleted on the client's side will be removed from Backstage.

Remove outdated data2.png

  • For sessions:

`Remove outdated data` is selected by default. This means that the items deleted on the client's side will be removed from Backstage.

  • For sessions registrations:

`Remove outdated data` is selected by default. This means that the items deleted on the client's side will be removed from Backstage.

Mapping

Do not change the mapping for fp_ext_id and fp_status!

 

What is required

Whitelist the IPs of the SpotMe servers

Lanyon requires SpotMe server IPs to be whitelisted.

 

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.