Connect GoToTraining and GoToWebinar - Article
Summary
GoToTraining and GoToWebinar can support scheduled online learning through connected provider accounts. The setup has separate Activity and Event contexts, so the correct account, client credentials and callback URL matter. Configure the required route and verify a representative session before relying on it for a live cohort.
Use this article to:
- Choose the correct GoTo service and connection scope
- Configure provider credentials and the displayed redirect URL
- Understand co-organizer and participant dependencies
- Verify session creation, joining and synchronization
Choose the service and connection context
Use the GoTo service appropriate to the delivery you have purchased and intend to run. GoToTraining and GoToWebinar are separate integration areas; configuring one does not establish the other.
In Settings → Third party integrations, open GoToTraining or GoToWebinar. Both provide Activity and Event subpages. Configure the context needed by the intended scheduling workflow, and review both when your delivery uses both routes.
The redirect URL is displayed for the selected context. Copy that exact value into the provider application rather than replacing its final path with an assumed callback. A credential pair can be correct while its redirect configuration is wrong.
Prepare the provider application
Coordinate with the administrator of the relevant GoTo account. Create or select an appropriate OAuth client in the provider’s client-management portal. Register the redirect URL displayed by Eurekos and the scopes needed for the agreed service.
Keep provider account, subscription and authorization prerequisites distinct. A client registration alone does not establish that the account is entitled to host the intended training or webinar. Do not copy a trial account’s details into a production connection.
Configure Eurekos
| Area | Credential labels | Additional point to check |
|---|---|---|
| GoToTraining | Consumer key and Consumer secret | Use the redirect URL for the selected Activity or Event subpage |
| GoToWebinar | Client ID and Client secret | Review Synchronize co-organizers for the intended delivery model |
Enter the approved credentials, use Save, then complete Connect where offered by the configured connection. Follow the provider authorization through the intended account. Saving a key is not the same as completing authorization.
For GoToWebinar, Synchronize co-organizers adds Activity administrators as co-organizers where the connection supports that relationship. Select it only when those responsible people should have that provider role and meet the provider’s account requirements.
Create and verify the learning Event
Use the relevant Event or Training Activity scheduling workflow and select the configured conferencing service. Keep the date, time, timezone and responsible delivery relationship coherent. Verify the created session in both Eurekos and the GoTo account.
Use Eurekos enrollment and registration for the intended cohort rather than maintaining unrelated attendee lists independently. The GoToWebinar synchronization follows the Eurekos participant relationship; adding people directly on the provider side should not be assumed to create corresponding Eurekos registrations.
Give learners a clear joining route and preparation instructions. A provider meeting link, Activity enrollment and recorded attendance are separate evidence. Confirm the intended host and participant journeys before announcing the session widely.
Operate changes with the provider owner
When a host account, credential, authorization or scheduled session changes, verify the connection again. Coordinate cancellation and rescheduling with the responsible facilitator and inspect the provider-side result as well as the saved Eurekos Event.
Do not promise that every provider-side change returns to the learning platform. Use the supported scheduling and participation routes, and inspect the actual attendance evidence for the configured provider. The connection’s settings do not by themselves establish that a participant completed the entire Training Activity.
Verify the configuration
| Scenario or check | Expected result or evidence |
|---|---|
| Provider and scope selection | The intended GoTo service and Activity/Event context are configured |
| OAuth authorization | Credentials, redirect URL and connected provider account match |
| A representative scheduled Event | Correct provider session, date, time and responsible host |
| Co-organizers are enabled | Intended Activity administrators have the expected provider relationship |
| A learner joins | The person reaches the intended session from the relevant platform route |
| Participation changes | Supported synchronization and the actual Eurekos record agree |
Troubleshooting
| Problem | What to check |
|---|---|
| Authorization returns a redirect error | Exact callback for the selected provider and Activity/Event subpage |
| Credentials are saved but no connection is established | Complete Connect/authorization where available through the intended provider account |
| A host or co-organizer is absent | Provider account prerequisites and Synchronize co-organizers configuration |
| Provider attendees do not appear as Eurekos participants | Use the supported Eurekos enrollment/registration route; do not assume reverse synchronization |
| The wrong GoTo service is offered | Check which separate provider integration was configured |
| A session change is not reflected as expected | Inspect both records and the supported direction before manually recreating the session |
FAQ
-
Are Activity and Event the same GoTo connection?
They are separate configuration contexts in the integration interface. Use the redirect URL and setup for the route your scheduling workflow needs.
-
Do people added directly in GoToWebinar automatically become Eurekos participants?
Manage the intended cohort’s enrollment and registration in Eurekos. Participant synchronization follows that relationship; do not assume that adding a person directly in GoToWebinar creates a corresponding Eurekos registration.