Ideas

Extend the functionality of the Program Member Custom Field (PMCF) values to be used as Tokens within the content of an email/landing page.   Example 1: You capture a value for an ad-hoc field (like number of accompanying guests, preferred time to call) and want to put these details in a triggered confirmation email reconfirming form field values.   Example 2: A specific value per person needs to be added to an email (field/value is not part of normal CRM sync). Risky to add this to a 'burner'/temporary field at the person level, so imported into a PMCF field to limit risk of other programs referencing this field and value then added to email as a token. ... View more

The suggestion is to add to the list of trigger tokens a new set of trigger tokens for Marketo Program triggers: - Added to Engagement Program - Engagement Program Cadence Changes - Engagement Program Stream Changes - Program Member Data is Changed - Program Status is Changed   The primary use case would be the {{trigger.Name}} token, which could be used in the above triggered campaigns to populate the Program Name in a flow step to enable program-level changes at a global level.   For example, in our instance, we need to populate a Program Member Custom Field (PMCF) with a common value whenever a lead reaches success in a program. Currently, we have to add the flow step in each individual program to set the PMCF. If we had a trigger token, we could have a single global campaign that could populate the PMCF across campaigns. Here's an example of the campaign setup:   Smart List: Program Member Status is Changed --- Program: Is Any --- Success: True Flow: Change Program Member Data --- Program: {{token.Name}} --- Attribute: [PMCF] --- New Value: [value] ... View more