Centralize a double-opt-in workflow | Community
Skip to main content
Dan_Stevens_
Dan_Stevens_
Level 10
October 13, 2015
Question

Centralize a double-opt-in workflow

  • October 13, 2015
  • 3 replies
  • 3240 views

For any program that has a form within it, we include the necessary flow steps to populate the appropriate opt-in fields (opt-in, opt-in date, opt-in program, etc.) with the appropriate values.  One of these values is a local "Program Name" token.  Ideally this would be built once and any smart campaign that needs to use it, would simply request this single campaign.  But if we do this, we lose the local program token.  My thought was to use this local token with a hidden field of the form (a Marketo form that's embedded on our website).  But when I populate this custom/hidden form field, the value remains as {{my.program name}}.  Are local tokens not supported in Forms 2.0?

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

3 replies

Grégoire_Miche2
Grégoire_Miche2
Level 10
October 13, 2015

Hi Dan,

I do not see how this could work.

I think you may post an Idea around "populate a hidden field with a token value", meaning that when the form JS is executed, it pulls the value from Marketo. I'll vote for it :-)

-Greg

J
Adobe Employee
JohnCl9Adobe Employee
Adobe Employee
October 13, 2015

Hi Dan,

Is the form you're using this token with sitting on a landing page that is a child asset of the Program where the token lives?

My.Tokens are only available to child assets of the Program or Campaign folder where those tokens have been created.

John

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 13, 2015

No, the form is a central form in Design Studio.  Forgot about that (I was thinking since the Program that's used to track behavior of this form - in this case, a contact-us page on our website - is local, that the tokens would work).  For those forms that reside locally within a program, this should work then, correct?  Are local my.tokens supported in Forms 2.0?

J
Adobe Employee
JohnCl9Adobe Employee
Adobe Employee
October 13, 2015

Yes, they should work.  Remember that My Tokens can live in Campaign Folders as well.

SanfordWhiteman
SanfordWhiteman
Level 10
October 13, 2015

The principal problem with your plan is the "embedded form" part.  If it were a Marketo LP, it's easy: render a token into the page (i.e. in an HTML block), then use the Forms 2.0 API to populate the value.

For embedded forms, though, you may be able to smuggle the token into the Thank You URL, which IIRC was recently fixed to restore the ability to include my.tokens.  If you can do that, then you can grab the token out of the URL, add the hidden field, then repost the form with the program name appended (silent post, so don't worry about the lead seeing anything).  This won't affect operation of your Thank You URL since you can strip out the data before the redirect (or just leave it in place if you consider it harmless for the person to see ?program=myname).

Dan_Stevens_
Dan_Stevens_Author
Level 10
October 13, 2015

Thanks Sanford, but even this approach won't work since there is no TY URL.  A user then receives a confirmation email and are asked to click to double-opt-in.  I think I'll need to stick with local campaign flows like we're doing today.

SanfordWhiteman
SanfordWhiteman
Level 10
October 13, 2015

You don't need to be using a TYURL, in fact it's easier if you're not. It's just leveraging the functionality awarded to TYURLs.

Terms & ConditionsAccessibility statement

Loading footer...