API Integrations: Connecting Your Registration Platform to InGo

Overview

InGo API Integrations connect your registration platform directly to your InGo community. Once connected, InGo can automatically pull eligible events from your registration platform and create them in InGo. When an event is activated, registrant data syncs into the correct InGo event groups, helping your team keep participant data accurate without repeated CSV exports and uploads.

The API Integration is separate from installing InGo widgets on your registration pages. These two features work together, but they are not interchangeable.

Widgets allow attendees to advocate for your event in real time as they register. |
The API Integration automates backend event creation and registrant syncing so your InGo event has the right participant data available for reporting and VIP Notifications.

Use both to maximize your event growth.

How It Works

When the integration is enabled, InGo pulls eligible events from your connected registration platform and creates them in your InGo community as Potential Events.

A Potential Event is inactive. It exists in InGo, but it is not live and does not begin syncing user data until someone activates it.

When your team is ready to use a synced event, activate it from the Events Dashboard. After activation, InGo begins syncing registrant data from the connected platform. As users are confirmed in the registration platform, InGo creates or updates corresponding participant records in the connected InGo event groups.

Supported Platforms

InGo currently supports API Integrations with:

• Cvent
• Swoogo
• Bizzabo
• Sessionboard
• ASP
• Visit by GES
• RainFocus

Additional platforms coming soon.
If your registration platform is not listed, contact your InGo Account Manager.

Platform Differences

The general setup process is similar across registration platforms: choose the platform from the Integrations menu, enter the required API credentials, sync events into InGo, activate the events, and map participant or registration types to InGo groups when prompted.

Registration type mapping may also vary by platform:

• Cvent, Swoogo, and Bizzabo support custom registration or attendee types, so mapping those types to InGo groups is an important part of setup.
• ASP, Sessionboard, and RainFocus can also support type remapping, but participant data is often more standardized based on current customer use cases.
• Visit by GES is supported, but InGo does not yet have enough live customer usage to document detailed mapping behavior.

Because integrations may vary based on how your registration platform account is configured, contact InGo Support if you are unsure how your registration types should map to InGo groups.

General Setup Steps

1. Go to your InGo Events Dashboard.
2. Click Add Events.
3. Select Integrations.

1. Choose your registration platform.
2. Enter the required API credentials.
3. (if needed) Filter your events
4. Complete the setup flow to sync events.
5. Refresh the Events Dashboard.
6. Review the events that appear as Potential Events.
7. Activate the events you want to use.

Registrant data will not sync for an event until that event has been activated.

Filtering Events / Handling Events You Do Not Want to Use

Depending on the integration and account setup, InGo may pull in all eligible live and upcoming events from the connected registration platform.

Use filters to control which events sync.

These events arrive as Potential Events, so they are inactive by default. If you do not want to use a specific event in InGo, you can leave it inactive or delete it from the dashboard.

Best practice is to leave events as Potential Events as deleted synced events will not be recreated on the next sync.

For Swoogo, an optional folder-name filter may be available during setup. If your Swoogo events are segmented by folder and you only want to sync a specific set of events, enter the folder name when adding your Swoogo credentials.

Handling Duplicate Events

If an event was already created manually in InGo before the integration was set up, syncing may create a duplicate Potential Event.

InGo helps identify possible duplicates by comparing event details such as name and date. When a possible duplicate is found, you may see:

• A Review Potential Duplicate button on the existing InGo event.
• A warning icon next to the synced Potential Event.

When reviewing a duplicate, you can choose to:

• Mark it as not a duplicate and activate it as its own event.
• Merge the synced event into the existing InGo event.

Merging preserves the configuration already completed on the existing InGo event.

Mapping Registration Types to InGo Groups

For data to properly sync between your registration platform and InGo, you’ll need to match your registration, ticket, and/or user types from your platform to the Groups you’ve created within your InGo event. You can map these together during the event activation step, while merging one event into another, or when directly connecting an InGo event to your registration platform as a one-off event.

InGo will display a table that lists out all registration types from your selected platform. For each option, you can select which InGo Group should be associated with it. Multiple registration types can be associated with the same InGo Group, and assignments can be applied in bulk. If you do not see an InGo Group that fits for a registration type, a new one can be created directly from this screen.

To finalize your event sync, at least one registration type must be connected with at least one InGo group. You can always return to this screen later to edit your configuration by clicking on the Integration Settings button on your Event Summary page, above the Groups section.

Updating Registration Type Mappings

Registration type mappings are not permanent.

If you add new registration types, reorganize your InGo groups, or need to correct an earlier mapping, open the event and click Integration Settings in the group section. This reopens the mapping screen so you can make changes.

On the next sync, users will be placed according to the updated mappings.

Tracking How Participants were added to InGo

The Registrants/Participants report shows every user in the event and how they were added.
Find your Participant report within your Event Summary, under “Configure” in the top right hand corner. Note “Channel” within the report.

Common Channel source types include:

• Platform Sync — added through the API Integration.
• Uploaded — added by spreadsheet upload.
• Registered — added through an InGo widget.

This report is useful for auditing participant data, troubleshooting unexpected entries, and confirming that synced users are appearing as expected.

FAQ, Limitations and Known Considerations

Event filtering
For most integrations, InGo pulls eligible live and upcoming events from the connected registration platform. These events are created as Potential Events and remain inactive until activated.

For Swoogo, an optional folder-name filter may be available during setup.

Missing event dates
If an event does not appear after syncing, check that the event has both a start date and end date in the registration platform. Events with missing dates, past end dates, or incomplete date fields may not be pulled in.

Cancelled registrants
At this time, cancelled registrants may remain in InGo after they cancel in the registration platform. We recommend creating a dedicated group such as Cancelled or Unregistered, moving affected users there manually, and disabling email sends for that group.

Duplicate review
InGo does not automatically merge duplicate events. Each flagged duplicate must be reviewed and resolved manually.

Multiple registration accounts
If your organization uses multiple registration platform accounts, you may need to create and connect separate API credentials for each account or community.

Does the API replace my Registration install?
The API Integration does not replace InGo widget installation.

You should still install the appropriate InGo widgets on your registration confirmation pages and confirmation emails. Widgets support real-time attendee advocacy when someone registers, while the API Integration keeps backend event and participant data in sync.

Think of the API Integration as an additional automation layer, not a replacement for the standard widget strategy.

Does this cost money to enable?
No, this beneficial feature is available within your InGo subscription

Am I charged for the events created by the API?
No, InGo does not charge per event. Subscriptions are advocate based, those who actually post.

Need More Help?

Contact your InGo Account Manager or reach out to support@ingo.me for help setting up your integration.