Platform Integrations

Here we will go through the available plugins in our CMS allowing for easy integration with 3rd party solutions you may be using.

Eventsforce Integration Setup Guide

Before you can connect your event to CrowdComms, you will need to generate an API user within your Eventsforce account, and generate an API key. Instructions on how to do this can be found here:

If you find you have any trouble with the setup, then you will need to get assistance from Eventsforce direct before we can start the setup with our platform. To do this, you can start a chat with an Eventsforce support agent from within your admin area.

From our side, please note that our system only allows group names up to 50 characters long. So you will need to bear this in mind with your fields that you wish to pull through into cc groups

Please note: You need to make sure that within Eventsforce all your custom fields are set up to apply to 'this event only'. If you set them up as 'available to all events' then they will count as event-spanning, aka profile level questions. They are then carried within your Eventsforce profile as Custom Data. This will NOT pull through via the API, which only pulls through your event specific registration data, so please make sure your questions and answers are correctly configured before setting up your API. 

We don't filter the registration or payment status when requesting the attendees from Eventsforce. However, the Eventsforce API states that if no registration status is specified, by default it will only return complete registrations. Therefore, we will only get complete registrations pull through to the CrowdComms cms. If you need further information on this, please refer to their documentation here.

Connecting EF to CrowdComms

  1. Log into the CrowdComms dashboard with your Credentials
  2. Click to edit the app that requires integration
  3. Click on “Plugins” at the very bottom of the left hand menu

    Picture1.png
  4. Click on the “eventsforce” Tile

    Picture2.png

  5. Enter the following.
    - Client I.D
    - Event I.D
    - API Key
  1. Click “Save”

Automatic Field Mapping

The above steps may be all you need to do depending on the fields set up on your reg form. The following information will pull across as standard:

Attendee Information:

Sessions set up in eventsforce will pull into a new agenda module in CrowdComms, so you won’t need to create one. The session details which pull across are:

Abstracts are also added to the sessions as documents

Custom Field Mapping

Now that the EF connection details have been inputted & saved, you can now click on the “Custom Fields” TAB to input any custom fields required.

  1. Click on the “Custom Field” TAB

    Picture3.png

  2. Click on “Create New”

    Picture4.png

  3. Enter the Name of the EF Field required to be pulled through

    Picture5.png

  4. Select the type (Custom Field or People Group)

    Picture6.png

  5. Select the exact group/field to be mapped. Which drop down is available as to select here will depend on which ‘type’ you selected in step 4.

    Picture7.png

  6. Click “Create” (You will now receive a message to say if the field mapping has been saved or not)

    Picture8.png

  7. Repeat the process as necessary

Notes

Picture9.png

 

IDLoom Integration Setup Guide

Please note: This is a self-service guide for when setting up your own idloom account with our platform. These instructions will not apply if we have set up registration for you in our CrowdComms account. In that case please speak to your support agent who can set it up for you.

There are two main elements to setting up your integration with idloom. Part one is within the IDLoom CMS itself, where you will create the integration. This will generate your API key. The second part, is within the CrowdComms CMS, where you will link the integration and relevant event to the platform.

IDLoom Setup

You will want to do this one you have your event all set and ready to go.

Step 1 – Navigate to the Integrations tab (3 up from the bottom, the one that looks like </>)

  1. Click to create a new integration
  2. Fill in the name
    N.B. this will usually be the name of the event but it doesn’t matter what you call it
  3. In the box for ‘Available for profiles’ select the profile that your event is set to
  4. Check the boxes for ‘Allow API access’ and ‘Activate webhooks’

    Capture8.PNG

  5. Click save – this will then generate your API key

N.B. It would be good to make a note of this at this point, or do the next steps in a new tab so you can easily access all the bits you need.

Step 2 – Navigate to your event

  1. Go to geeks – integrations
    N.B. If you don’t see an integrations tab in the geeks section here, then something is wrong with the previous steps, most likely you missed the ‘available for profiles’ section so go back and check.
  2. Select the newly created integration

    Capture9.PNG

  3. Press save
  4. Stay in the geeks section and go to ‘Analytics & tracking’ to get the ‘Event UID’

    Capture10.PNG

    N.B. Make a note of this, as well as your event name as written in the idloom CMS, or again leave this tab open.

CrowdComms CMS

Now go to the corresponding platform in the CC dashboard and follow these steps:

  1. Go to plugins – idloom
    N.B The ‘idloom account’ and ‘idloom server’ information will be pre-filled with our CrowdComms account data. You will need to override this with your own. Please fill in your account name and server info (the server will always be idloom.events)
  2. Enter your API key

    Capture11.PNG

  3. Press save

The following fields will map across by default:

Title –> Title
First Name –> First Name
Last Name –> Last name
Email –> Email
Job Title –> Job title
Company name –> Company
Phone/Mobile number –> Phone number

N.B All other default CrowdComms fields can be mapped into, e.g ‘About’, ‘Address’ and all social media fields if required (perhaps as a way of getting speakers to self-populate their profiles), it just means you have to manually map them using the CMS. Any other form fields/questions will also need to be set up as custom fields in the CrowdComms CMS before you can map them

Key Considerations
The mapping between the default fields is hardcoded and therefore no other idloom fields can be mapped into them. You will need to consider this if you want these fields displayed under a different name in CrowdComms. An example would be if you want the company name to display under ‘organisation’ rather than ‘company’. You have 2 options here, either create a custom field in idloom with a corresponding custom field in CrowdComms, and link them. Or you would use the default field in idloom (as you can re-name them) but bearing in mind this would pull into the company field in CrowdComms. To change this, this would be part of a custom design request that you would need to check with your support manager. We could then get this changed on our end via custom design. We would only advise using this second option, if it is key to have this field visible under a person’s profile from within the main people list, rather than having to click in to see all custom fields. So please weigh up the best setup for your specific event.

  1. Click on the ‘Events’ tab at the top which should now have become selectable from completing step 3.

    Capture.PNG

  2. Fill out your event ID (UID) and event name as found on the ‘analytics & tracking’ section within your event – geeks.
  3. Click save
    N.B. This will then add the integration to the platform.

    Capture2.PNG

  4. Click the pencil icon to map custom fields
  5. Select the ‘Default People Group’ top right that you would like registrants to pull into if required. (If blank they will default to the ‘everyone’ group).

    Capture3.PNG

    N.B. If no custom fields are required, then setup is now complete. Otherwise, please continue as below.

  6. Under ‘Field Integrations’ click ‘create new’ to begin mapping custom fields
    N.B At the top of this section it says ‘idloom field’ or ‘idloom field’. For the moment please ignore the second box of the same name, as this needs to be updated by the devs. The first box will have a drop down of all fields, categories and options on your registration form.

    Capture4.PNG

  7. Select your field/category/option from the list
    N.B. With the country field, because of a change on idloom’s end this will now only pull through the country code by default. If you need the whole name to pull across you will have to speak to your support manager as this will require a bespoke setup we will need to do for you.

  8. On the line below, choose where you want to map it to by finding the corresponding box for the field/category/option you chose. i.e if you chose to map a field, then you can now only select options from the profile field or custom field boxes.
    N.B. idloom fields can only map to cc fields (profile and custom depending on what’s relevant) and categories and options can only map to sessions or groups.

    Capture5.PNG

  9. If your field is a tickbox, then also remember to tick this box. This is required as idloom will send the information through as binary i.e. a 1 or a 0 and ticking this box will turn it into a yes/no.

    Capture12.PNG

Useful Information
  1. Registration status: Canceled, Rejected, Not coming, To contact
  2. Payment status: Waiting for payment, Canceled
Troubleshooting

Errors in the cms

Data not pulling

 

Zoom Integration Setup Guide

To integrate Zoom into our platform, you will need access to the following; 

Please note: If you are looking to use zoom to run concurrent meetings, there are some limitations on zoom's side, so please see these best practices before deciding if this setup will work for you.

Here is a video guide on integrating your account with the platform:



All steps are also listed below for you to refer back to:

Step 1. Zoom Developer Platform

Once you are logged into zoom, you will need to navigate to the developer platform. You can find this under solutions in the top left hand menu

Switching-to-Zoom-Developer-Section.PNG

Then you need to click on 'build app' in the top right next to your initials as per the shot below: