How to show subscribe checkbox only if previously unsubscribed

[Anonymous]

So what's your best suggestion in this instance? We have a pretty low download rate but as we seek to improve those rates I'm not trying to increase our risk DoS.

It sounds like we can accomplish what we want -- to only show the registration field if unsubcribe=false -- only if we use prefill. Not super experienced with custom coding so you'll have to explain what ProgPro is to this rookie.

[SanfordWhiteman]

So what's your best suggestion in this instance? We have a pretty low download rate but as we seek to improve those rates I'm not trying to increase our risk DoS.

DoS isn't about legitimate use, it's about legitimate plus malicious use of the form. Any form that uses one API call (or more) in response to end-user actions is a sitting duck for a junior hacker.

It sounds like we can accomplish what we want -- to only show the registration field if unsubcribe=false -- only if we use prefill. Not super experienced with custom coding so you'll have to explain what ProgPro is to this rookie.

ProgPro is Progressive Profiling -- see here: Configure Form Progressive Profiling - Marketo Docs - Product Docs

[Anonymous]

So if we have a form embedded on our WP site and it triggers a campaign that has multiple flow steps that change statuses and another campaign that delivers the content in an email we're at risk for malicious use negatively affecting us?

[Dan_Stevens_]

They do however support Progressive Profiling, and (actually contrary to Dan's point in this case) with a boolean field, you can use ProgPro to determine whether the checkbox is checked or not, since a non-empty boolean field in Marketo is true / empty field is false.

The point I was trying to make is to be careful with boolean fields in Marketo since Marketo considers the field having a value in both cases (true and false).  And that if you did show the field to an already opted-in user - and that user didn't check the field - he/she's opt-in value would revert back to false.  In otherwords an UPDATE to that field is taking place even when no value - or so it appears - exists.

[SanfordWhiteman]

... In other words an UPDATE to that field is taking place even when no value - or so it appears - exists.

That's true by default, but Forms 2.0 API + JS can be used to make sure the field is not sent with the form.

In a Progressive Profiling context, a false boolean field is considered to be not-filled-in.  Because of this, even when PreFill is not supported directly (i.e. embeds) you can still determine whether the field was orginally false.

[Anonymous]

So we tried hiding the newsletter reg field based on the unsub value and came across a couple of problems:

• If the field is a part of ProgPro, it will not show if a known visitor unsubscribes
• If the field is outside of the ProgPro, it looks awkward above the ProgPro fields

I set the visibility to:

Is there a workaround we can use with ProgPro so that we only show the resub field if the unsub field is set to false? I need it to show up even if a known visitor unsubscribes so maybe it's best to house it outside of the ProgPro fieldset like Sanford suggested. Any ideas?

[Carrie_Chandle1]

In a Progressive Profiling context, a false boolean field is considered to be not-filled-in. Because of this, even when PreFill is not supported directly (i.e. embeds) you can still determine whether the field was orginally false.

I'm trying to accomplish something similar to OP and this was the exact answer I needed, and way more simple than I thought this process would be. Setting the field as progressive takes care of it!

[SanfordWhiteman]

Glad it helped!

[SanfordWhiteman]

[Anonymous]

Sanford, Thanks for the visuals. Will this allow us to continue progressive profiling as well as embed the forms on our webpage (not hosted in Marketo)?