Do you need to see if InGo will work in your registration system, website, etc? Here are some initial questions that if you answer "yes" to, you can install InGo.
1) Does your platform accept custom HTML (including <script> tags) to registration pages?
1a) If yes, can the platform designate on which pages in the registration process and/or what part of those pages the code is injected?
2) If not, does the platform have a public API which InGo could run registration through and then POST a registrant via the API to the system as if they registered directly on your platform?
Demo Code
If the answer is "yes" to question 1, here are instructions and demo code to send to your installer if they want to install InGo on a test reg workflow:
Login: (visible widget at start of registration)
<script src="https://cdn.ingo.me/widgets/E21CCEEB63D34EFE9C4F88A7E79612BA.js"
data-ingo-manual="http://www.insert_your_next_page_where_users_should_land.com"></script>
Data-ingo-manual should be set to the next page URL in the registration flow. Most likely your personal details form page
Autofiller: (invisible widget on personal details page)
<script src="https://cdn.ingo.me/widgets/E3BA400B47154CCDB49FAC95A6D30644.js"
data-ingo-fields.user.first-name="#FirstName_Input_CSS_Selector"
data-ingo-fields.user.last-name="#LastName_Input_CSS_Selector"
data-ingo-fields.user.email="#Email_Input_CSS_Selector"
data-ingo-fields.user.company="#Company_Input_CSS_Selector"
data-ingo-fields.user.company_position="#Title_Input_CSS_Selector"
></script>
Data-ingo-fields.user._____ should be set to the CSS or query selector of your form fields you wish to pre-fill. You can remove any of these that you do not wish to pre-fill, and any valid CSS/query selector should work.
Social: (visible widget on confirmation page)
<script src="https://cdn.ingo.me/widgets/F623C732ABB14D219C425CB0F050BBD9.js"></script>
Confirmation: (invisible widget on confirmation page)
<script src="https://cdn.ingo.me/widgets/31A8622C9C79487191856D46FEB5A6D5.js"
data-ingo-attendee.email="Your_system_email_param"
data-ingo-attendee.first-name="Your_system_firstname_param"
data-ingo-attendee.last-name="Your_system_lastname_param"
data-ingo-attendee.company="Your_system_company_param"
data-ingo-attendee.title="Your_system_title_or_position_param"
data-ingo-attendee.external-registration-id="Your_system_generated_external_id"
></script>
If you have mapped all 5 of the main fields in the autofiller widget, you can omit the “attendee” object in this widget. If not, data-ingo-attendee.____ should be set to a personalization tag (example: {{first_name}} would replace with Tim)
Comments
0 comments
Please sign in to leave a comment.