Option to update mapped field values during journey in Programs
None
We use this functionality for drip campaigns and need more flexibility as these campgains can continue for long periods of time. From example, we need the ability to update certain fields during the course of the journey, e.g., CSM name if the client is transitioned to a new CSM.
Sign up
If you ever had a profile with us, there's no need to create another one.
Don't worry if your email address has since changed, or you can't remember your login, just let us know at community@gainsight.com and we'll help you get started from where you left.
Else, please continue with the registration below.
Welcome to the Gainsight Community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
This is current functionality: "When the outreach is sent, the token values are fetched dynamically. In order to tokenize fields, they must first be added under "Select list fields" in the Power List setup step."
More info here: https://support.gainsight.com/Journey_Orchestrator_and_Email/Standard_Outreaches/04_Create_and_Execute_CoPilot_Outreaches_(aka%2C_schedule_emails)
If you have additional email steps, the token will continue to use the value that was captured in the initial query sync for that participant.
If the CSM name changes on the account record, the value in the Program will not update to the current value - so additional emails will continue to be sent from and signed by the old CSM (for example).
I have encountered this countless times. To have a value updated on an active participant record would be enhancement and would be of interest to our org.
Most recently, we had a scenario where renewal owners were being changed on renewals that were part of an active Program. To reduce confusion, we need to add a Conditional Wait step to check to see if the renewal owner changed, and if true the would be placed on an alternative email path that did not use the tokenized fields.
What would have been better, would have been able use current data for token fields rather than data that was pulled at the initial participant query sync. Or use a Calculated Field value in a Token.
https://community.gainsight.com/conversations/programs-designate-participant-fields-to-be-updated-if-changed-eg-csm-5cd06e42e4b0e18d6eded18f