Best Practices for InGo Widget Installations
Events achieving 10x more referrals and growth are following these best practices to ensure widgets are installed correctly within their registration workflow.
1. Use the Full Funnel Installation (Unless Otherwise Advised)
InGo widgets work best when installed at the beginning AND end of registration, meaning all four widgets are deployed across the registration flow:
|
Registration Page |
Goal |
Widget Type |
|
Start |
Double advocacy during registration and speed both. |
Login Widget |
|
Personal Information Page |
Speed registration with auto-complete |
Registration Widget |
|
Confirmation/thank-you page |
Drive advocacy for registrants who we can confirm completed registration. |
Confirmation Widget & Social Widget |
⚠️ Critical: A missing Login Widget reduces adoption by approximately 40%. If your provider is compatible, ensure it is present at the start of the registration process.
2. Place the Social Widget "Above the Fold"
✅ Do: Place the Social Widget near the top of the confirmation page, above the fold.
❌ Don't: Place it at the bottom of the page where registrants are unlikely to see it.
Poor placement is equal to not installing at all. This is one of the most impactful and easiest fixes to make.
3. Retrieve Your Widget Scripts from the InGo Admin
To get the correct widget scripts for your event:
- Log into the InGo Admin
- Navigate to your event → Registration Path → Scripts
- Select your registration provider (e.g., Cvent, Visit by GES, Swoogo, etc.)
- Follow the on-screen instructions for each widget
📄 Need help finding your scripts? See: Locating Your Widget Scripts
4. Upload Your Event Graphics Before Going Live
The Social Widget requires a posting graphic to display correctly. If no image is uploaded, the widget will show a spinning wheel or blank preview.
To upload your graphic:
- Go to your event in the InGo Admin
- Navigate to Registration Path → Edit
- Click Upload, select your image, and Save
5. Add InGo HTML to Confirmation Emails
Beyond the registration flow, InGo can be embedded in:
- Registrant Confirmation Emails
- Know Before You Go (KBYG) Emails
- Speaker / Exhibitor Confirmation Emails
Adding InGo's HTML block to these emails extends reach beyond the confirmation page and encourages sharing at multiple touchpoints. Contact your InGo Customer Success Manager for your event's HTML snippet.
6. Request a QA Before and After Going Live
InGo's Support Team offers proactive Quality Assurance (QA) reviews of your widget installation. We strongly recommend requesting a QA:
- ✅ Before launch — to catch issues before registrants start flowing through
- ✅ After going live — especially if you notice low participant counts or adoption rates
- ✅ After any changes to your registration platform — widget scripts can break if registration pages are updated
To request a QA, email support@ingo.me with:
- Your event name and link in the InGo Admin
- A coupon code or test credentials to bypass any paywall
- The registration URL you'd like us to test
7. Provide a Coupon Code / Test Credentials for QA
If your event registration has a paywall or requires payment, the InGo Support Team will need a complimentary or test promo code to complete a full end-to-end QA. Without this, we cannot test the confirmation page where key widgets live.
Please include this when opening a support ticket or requesting a QA.
8. Check Your Installation If Adoption Rates Are Low
If you notice a lower-than-expected adoption rate or participant count, a broken or misconfigured widget installation is often the cause. Common issues include:
- Login Widget missing or removed from the start of the flow
- Confirmation or Social Widget absent from the confirmation page
- Social Widget placed below the fold
- VIP Share link used in place of the widget
- Registration page was updated, breaking the widget embed
If you suspect an issue, contact support immediately — especially if your event is within 90 days. Getting issues resolved early maximizes the number of registrants captured and advocates generated.
Need Help?
- 📧 Support: support@ingo.me
- 📚 Knowledge Base: support.ingo.me