General Requirements for Installing InGo

Installing InGo is generally as simple as cutting and pasting code snippets into your registration platform.  However not all registration platforms are InGo-compatible.  This article will describe what is generally required for integrating InGo.

Requirements for Embedding InGo on Your Registration Platform

• Does your registration journey include 1) a start/landing page, 2) a separate data collection form page, and 3) a confirmation / "thank you" page?  The majority of registration flows adhere to this pattern. InGo requires this specific journey in order to function correctly.

• Can you embed javascript to the content area of all of the above pages? 
  • Yes! Great, InGo should easily install to your site in just a few minutes.   
  • Maybe or unsure?  Maybe your platform allows custom JavaScript in the header and footer, or on a subset of the required pages?  A custom install should be possible.  Contact [e-mail] for assessment.
  • No. Your site doesn't allow for custom JavaScript, or embeds to an iFrame that cannot interact with the entire page.  InGo might still be installed with workarounds or with limited features.
• Can you redirect registrants from  a different URL outside of your registration platform to your registration site, and redirect back out again?  This workaround can be used where registration platforms don't allow for custom JavaScript, but allow for confirmed registrants to be redirected to an external confirmation page.
  
  See our example Eventbrite integration here. This same process applies for any style of integration where InGo cannot be embedded on your registration platform but you can redirect people to a third party website.
  

If you have any questions or doubts, please contact [e-mail] for assessment.