Compusystems (CSI) Installation

Are you using CSI as the registration platform for your event? The standard InGo installation and Best Practice setup is as follows.

Requirements, please read:

Do not cut and paste InGo code from a previous event.
InGo Widgets currently operate with four (4) distinct widget IDs (assuming you are installing all four) per event.
IDs change from event to event.
IDs need to be integrated with the code sent by your InGo Account Manager.
InGo's new widget configuration does not need jQuery. Do not include this. Use only the snippets below with the new IDs provided to you via your InGo Account Manager.

Activator (Formerly Login Widget)

1. The Activator Widget is installed on the initial registration page (next to Manual Registration button) in the middle of the page

Code example:

Screenshot:

Note: Activator Widget script should be inside <div> where you want to display it (AttendeeRegWelcome.jsp)

Autofiller (Formerly Registration)

2. The Autofiller Widget goes on any page where you wish autofill to be used (for first name, last name, email, company, and title.)

Code example:

Screenshot:

Note: Code should be inside <HEAD> (AttendeeRegAdd.)

Amplifier (Formerly Social Widget)

3. The Amplifier Widget needs to be installed on the confirmation page above the fold

Code example:

Authorizer (Formerly Confirmation)

A. Single Attendee Type Events (No Additional People Can Be Added to the Registration Record In the Same Workflow)

4.A The Authorizer Widget is also installed on the confirmation page and the code needs to be updated with the CSI params for email, first, last, company, and title. (please confirm the below params in the code are correct)

Method One:

data-ingo-attendee.email="<%=reg.getValue("internet_address")%>"

data-ingo-attendee.first-name="<%=reg.getValue("name_first")%>"

data-ingo-attendee.last-name="<%=reg.getValue("name_last")%>"

data-ingo-attendee.company="<%=reg.getValue("comp_1")%>"

data-ingo-attendee.title="<%=reg.getValue("title")%>">

</script>

B. Multiple Attendee Type Events (Additional People Can Be Added to the Registration Record In the Same Workflow e.g. "Register Others")

4.B The Authorizer Widget is also installed on the confirmation page and the code needs to be updated with the CSI params for email, first, last, company, and title.

ADDITIONAL ATTENDEES: If the attendee registered additional attendees, you must add one extra call for each additional attendee with the parameter additional = true. It works only with method 2 and 3:

Method Two:

<script
src="https://cdn.ingo.me/widgets-loader/1.4.5/js/ingo.loader.widget.js"></script>
<script>
 window.InGo.ingoWidget({
   widgetId: "[INGO-AUTHORIZER-WIDGET-ID]",
   attendee: {
     additional: true,
     email: "##User’s email here##",
     firstName: "##User’s first name here##",
     lastName: "##User’s last name here##",
     company: "##User’s company here##",
     title: "##User’s job title here##"
     external-registration-id:"##User’s badge/reg/unique ID here##"
 }});
</script>

Method Three:

   <script
     src="https://cdn.ingo.me/widgets-loader/1.4.5/js/ingo.loader.widget.js"
     data-ingo-id="[INGO-AUTHORIZER-WIDGET-ID]" data-ingo-additional="true"
     data-ingo-attendee.email="<%=reg.getValue("internet_address")%>"
     data-ingo-attendee.first-name="<%=reg.getValue("name_first")%>"
     data-ingo-attendee.last-name="<%=reg.getValue("name_last")%>"
     data-ingo-attendee.company="<%=reg.getValue("company_name")%>"
     data-ingo-attendee.title="<%=reg.getValue("title")%>"
     data-ingo-attendee.external-registration-id="<%=reg.getValue("registration_ID_needs_confirmation_from_CSI")%>">
   </script>

Thank you for taking the time to read this article.