Progressive profiling breaking on number field | Community
Skip to main content
A
Anonymous
January 16, 2018
Question

Progressive profiling breaking on number field

  • January 16, 2018
  • 2 replies
  • 4723 views

We're testing progressive profiling on a new form. Everything's working great until the user gets to a field where the field type is number (and the field type it maps to is an integer). For some reason,  on submitting the form, instead of showing the thank you message as it should (it's embedded on a page and our CMS controls the thank you message), it refreshes the page and adds the fields and my submissions as parameters at the end of the URL.

We changed the field type to text and that fixed the issue. I'm sure we're not the first people to add a number field to a progressive profiling form -- has anyone encountered that issue before? Were you able to keep the field type as number, or did you need to change it to a dropdown or text field and add validation rules to only accept numerical characters?

For now, we're removing it altogether and will add it back in when we have more time to test.

Thanks for your help!

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

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
January 16, 2018

You must provide a URL if you want people to look at this.

keithnyberg
keithnyberg
Level 7
January 16, 2018

Agree with Sanford that a link would help. Have you tested the form submission to see if the values are captured in your MArketo instance regardless of the landing page behavior you mentioned?

Might be an issue with you form submit re-direct but hard to assume without playing with the form.

A
Anonymous
January 31, 2018

Hi Keith -- we've removed the problematic fields from our progressive profiling forms for now, and my team has submitted a case with Marketo, which has been escalated twice.

When someone filled out the form with the offending fields (one of which was number field, the other was a checkboxes field), the page would simply refresh, and either put the fields (and the person's responses) from the form as query parameters on the URL, or just add a weird query string to the end of it (something like "?aklid=123456"). The values they entered into the form were not captured in Marketo.

Once we get an answer back from Marketo support, I'll reply with whatever they discover to be the root cause of the issue.

SanfordWhiteman
SanfordWhiteman
Level 10
January 31, 2018

Why won't you provide a link? I can tell you what the bug is much faster than they can.

r just add a weird query string to the end of it (something like "?aklid=123456")

It's not weird, that's the form submission cache id (aliId). It's always attached to URLs after submission.

Terms & ConditionsAccessibility statement

Loading footer...