Re: gotowebinar registration issue

Chris_Adams
Level 2

gotowebinar registration issue

Hey there, We do about 3-4 webinars a week through gotowebinar and marketo. Our scheduled webinars for next week aren't adding test registrants to the webinar itself. Filling out the registration form put leads in 'invited' but they aren't getting to a 'registered' or 'registration error' status. I've re-entered the partner info in the admin panel, and am noticing an intermitent api error - 403, webinar has ended and can't accept registrations, but the webinars in question take place on the 1st, 2nd, and 3rd of July. If I register directly on gotowebinar.com everything works fine, seems to be an API issue. Anyone else got this going on currently?

Thanks,
Chris
Tags (1)
6 REPLIES 6
Anonymous
Not applicable

Re: gotowebinar registration issue

Is there an error message in the activity log for the lead?  I know that earlier in the week there was some confusion between Marketo and GTW in regards to updates to the API, which in turn, broke forms with required fields from correctly registering leads, but that was fixed a couple days ago.
Chris_Adams
Level 2

Re: gotowebinar registration issue

It looks like something wonky is going on cloning the registration page and the form. In my program, for the registration page, it's saying the only form on the page is for the correct date, 7/1 in this case. Yet, when I visit that registration page and fill out the form, the activity log is showing that I'm filling out the form for 6/24 and it's throwing the error. Thanks for the help with the activity log suggestion, now to dig deeper.

Thanks again.
Anonymous
Not applicable

Re: gotowebinar registration issue

Try removing and then re-adding the form element on the registration pages. I heard there was an issue with cloning forms from one program to another in which the new program seemed to reference the correct but actually was referencing the original form.
Chris_Adams
Level 2

Re: gotowebinar registration issue

Yeah, that's the issue I'm running into. My quick fix was to recreate the landing page and add the correct form to it. Not the ideal solution, but it did work. This is a new bug to me though, we've been doing this cloning method for months now. Hopefully I can find a better solution or figure out how to keep it from happening.
Anonymous
Not applicable

Re: gotowebinar registration issue

I’m experiencing a similar problem, but we have just embarked on our second attempt to integrate Marketo and GTW. So unlike Chris, I never had a functioning event and LP that suddenly stopped working after cloning it. 

After reading through this discussion, I rebuilt my landing page and I also reduced the fields to first name, last name and email address to rule out any other variables causing the problem.

After registering a few test registrants on the new landing page, I’m still seeing the same issue. Members are showing up in an “Invited” status vs. a “Pending Approval” status. Also, the registrants are not pulling through at all in GotoWebinar.

I checked the activity log and I don’t see any error messages at all. I see change program status activity type with details referencing the name of the program “Not in Program => “Invited.” I tried manually switching the member status for one of the registrants from “Invited” to “Pending Approval” hoping it might push the registrant into GotoWebinar. No dice.

Everything appears to be working from the Admin tab. In Launch Point I can see the program names in the “used by events” for my test campaigns. Also, everything is flowing nicely into the SFDC campaign.

I’ve submitted a case to support, but curious if anybody has ideas what could be causing this?

Anonymous
Not applicable

Re: gotowebinar registration issue

Hey Folks, never mind. Marketo Support pointed out that I was missing a critical local asset. I didn't have a registration child campaign with a trigger and flow step to change the member status from invited to registered upon completing the form. I thought the GotoWebinar integration would automatically handle that on the backend.