Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
You do not have to render a Forms 2.0 form to use the Forms 2.0 API. Therefore you do not necessarily need to make a REST API call to Marketo unless you have exhaustively thought through your design, which I am quite convinced you have not.If you insist on using the REST API regardless of how well ...
I'm saying you're assuming the REST API is necessary instead of considering that your requirements may be better and more scalably met by the Forms 2.0 API.
I would have to see the HTML (i.e. URL) of your page to know exactly what you're talking about.
What's the exact custom CSS you're using?
The form has class "mktoForm" (you can see this in your friendly Dev Tools).
@Alicia C I see you posted while I was composing!You seem to be committed to making server-to-server API calls, which may indicate an XY problem (narrowing in on a solution before properly expressing the problem and opening it to alternate/better solutions). If you have a registration API that can b...
@Alicia C In [2], if you mean the voucher #s are generated on a separate server, you'd probably chain XHRs together: post to voucher server --> onSuccess callback --> post to Marketo server.As @Josh says if you don't have a front-end developer who understands Marketo you should probably retain one. ...
From your description, it doesn't sound like you need to use the REST API nor even server-side form posts. You just need to use the client-side Munchkin and Forms 2.0 APIs, which are waaaay more scalable.I'm assuming that your "platform" is a web app and that you want to log events to Marketo synch...
@Ryan The SCRIPT tag inside the DIV with id=lpeCDiv_4937.
I see you posted again while I was composing!