9 Replies Latest reply on Oct 13, 2015 10:18 AM by Dan Stevens

    Centralize a double-opt-in workflow

    Dan Stevens

      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?