Gaaaaah... I went according to the documentation, but apparently I know just enough to hurt myself, I guess. I did actually have the fields populated at one point (ex: "FirstName":"John" etc). I stripped it out when posting the sample code. Logic being that, I was afraid that those example values would get passed, instead of what was actually getting filled out in the form. I can put that back in though easily enough if they need to be there. I do have custom fields for the 'ecode' (among others); my concern was more for standard fields that differed (ex: Marketo's FirstName to Cvent's first_name). I guess my question there is, the field names on the visible form need to match the field names that are the hidden fields, yes? Otherwise, how are the values going to get passed from the visible form to the hidden form's fields? I suppose the example I posted should have included the field names of the visible form, instead of "FirstName" "LastName" "Email". On lines 9 thru 18, I more or less copied the regular documentation, except I updated "myForm" to "htmlForm," because I figured that part had to direct to the form ID; what else would 'myForm' be? Nothing else in my code is called 'myForm,' so my impression is that it correlated to the form ID. From there, it followed to me that line 17 was the 'listener.' When i looked at your documentation here: MktoForms2 :: HTML form to Mkto form - I don't see a listener attached to the raw HTML form there that looks any different from what I did on my form, except I included the entire embed code instead of just the last two lines like on yours, and put the 'display:none;' inline. As to your second point, the payload looks to be formatted correctly on my end; here's the example payload: ecode={{lead.CventEcode}}&first_name={{lead.First Name}}&last_name={{lead.Last Name}}&email_address={{lead.Email Address}}&source_id=null&target=null& it submit_form=Submit (You'll notice there's two fields at the end; sourceID & target. According to the documentation: "The Source ID and Target Landing Page fields can be null, but must be included in the form.") It's coming back as response code 200, so it's connecting, but I'm getting a response that's a bunch of HTML effectively saying there's been an error and I need to contact my Cvent support team. Which I did...and they can't seem to help me. I'd paste the response code dump, but it's a giant block of jibberish. If the payload I'm passing looks correct though, then at least I know the issue is on their side and not mine.
... View more
Customize up to 8 badges at the top of your trophy case for all other Community members to see!
Ignite 1
Earned on 2.08.21
Earned by 3230 people
Select to learn more
Give Back 1
Earned on 2.08.21
Earned by 3211 people
Select to learn more
Affirm 1
Earned on 2.08.21
Earned by 549 people
Select to learn more
Give Back 10
Earned on 2.08.21
Earned by 559 people
Select to learn more
Ignite 3
Earned on 2.08.21
Earned by 933 people
Select to learn more
Give Back 3
Earned on 2.08.21
Earned by 1456 people
Select to learn more
Ignite 5
Earned on 2.08.21
Earned by 526 people
Select to learn more
Give Back 5
Earned on 2.08.21
Earned by 944 people
Select to learn more
.png)