Looking for Form Help | Community
Skip to main content
A
Anonymous
February 28, 2017
Question

Looking for Form Help

  • February 28, 2017
  • 1 reply
  • 1381 views

  Hi Marketo Community,

I am trying to create a form that will allow me to schedule clients into interview slots. This could also be used for interviewees. Where can I go to find help on creating this type of form? It would be built looking like the following:

First Name:

Last Name:

Email:

Monday 3-6

  • 1:30 PM
  • 2:00 PM

etc. ^ The above can be radio buttons, or check boxes format doesn't matter to me as much as the functionality of it.

Then once one of those time slots has been chosen, I would like for them to no longer be available to the rest of the people viewing that page.

If this isn't possible, is there at a minimum a way for me to set up a similar system where people can select their top 3 time slot choices?

Thank you for the direction!

@Gregoire Michel​? Merci

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
February 28, 2017

Please move the thread to Products and someone will answer it there. "Community" is for website feedback, not product support -- and yes, this is confusing!

A
Anonymous
February 28, 2017

Thanks, I will move it to products!

SanfordWhiteman
SanfordWhiteman
Level 10
March 1, 2017

Hi Nicholas,

Limited-registration events with instant feedback (yours is an extreme example of the same thing, with a single registrant) is a frequently sought feature.

Unfortunately, there isn't any native support for this. Marketo's lead-centric approach doesn't allow you to set program-level properties (in this case, an incrementing program-level token would do the trick) programmatically without using the REST API. And your few daily API calls are so precious that even though you can update a token in response to a form post, you'd be opening up a Denial of Service vulnerability.  It's an absolute no-no, even if tempting.

So even though a {{my.token}} could be used -- once it's set -- to change the options displayed on a form, or whether the form is displayed at all, it's setting the token that's out of reach in the real world.

This means we've had to look in other directions to sort-of accomplish the goal.

  • One is by using what I call a Resource Lead. This is a special dummy/placeholder lead that represents the program itself. You can increment a score field on this lead for every registration, and you can trigger... well, something... when the score goes over your registration limit. The question is not setting the value in this case but getting the value in order to action it (the opposite of the program token situation above).  The development work to do this gets pretty wacky, but everything is kept within Marketo.
  • Another is by logging registration events to a remote database (via webhook on form submission, not directly from the client). Then have the browser peek at the remote database (read-only!) before rendering the form. The development effort here is actually easier than the previous bullet, but it takes more moving parts. Pretty cool when it's done. And yet with the lingering feeling that you should have used a different event registration service to do the whole thing (although in truth, 3rd-party event reg services threaten your API limits as well when they flush data back to Marketo).
Terms & ConditionsAccessibility statement

Loading footer...