header

How to use Calculated Fields in Journey Orchestrator Programs

  • 29 October 2019
  • 6 replies
  • 294 views

Userlevel 7
Badge

One of the most common questions I get during Admin Office Hours is “How can I account for updates to participant data mid-stream during a Program?”

 

When I explain to Admins that we have a feature for this called Calculated Fields within the Program setup, they often seem pleasantly surprised but then a little intimidated by the steps that are involved in making sure everything runs right. I’ve put together a tutorial video below that will hopefully help simplify this process. 
 

 

The main things to remember: 

  1. When setting up your calculated field, make sure to set up the filters to associated the Account ID with the Account ID you’ve mapped in your participant sources. Same goes for email address at the contact level. 
  2. You’ll want to use this field in a conditional wait in your program. In the video below, I start my query with contacts that have a score below 50. My conditional wait then checks in to see if any contact still has a score below 60 after 7 days. If yes, I create a CTA. If no (meaning the contact’s score has improved above 60), they get a thank you email.

What I get then is the following screenshot. After publishing the program, I changed one of the three contacts’ score to 70, meaning that contact got an email while the other two got a CTA. You can see that the program correctly picked up that new score and therefore sent the contact with a 70 score down the path of getting an email.

 

Calculated Field Program Worked!
 

6 replies

Userlevel 7
Badge +1

Hi @spencer_engel  - to your first reminder point, essentially you need to filter an ID field from the data source (SFDC) to a matching ID field from the query. So, it could be Account ID = (field) Account ID or it could be something else as long as you make a custom mapping - for example Opportunity ID if you want to check for changes to an open Opportunity (e.g. Renewal)

Userlevel 6
Badge

I’ve not used Calculated fields yet - would this be use case for it?
Pulling in Accounts with a specific CTA that’s status is open. Make CTA Status a calculated field. 7 days after an email, check that the status of the CTA is still open?

Userlevel 7
Badge

I’ve not used Calculated fields yet - would this be use case for it?
Pulling in Accounts with a specific CTA that’s status is open. Make CTA Status a calculated field. 7 days after an email, check that the status of the CTA is still open?

Yes, absolutely! That’s a great use case.

 

If I use this in a long program where I want to evaluate the same field at multiple times (let’s say 3 times) during a program. Will I need a calculated field for each conditional wait or can I use the same calculated field at each conditional wait?

 

Scenario1:

“CSM Name Calculated1” used at 3 separate conditional waits to check for a change in CSM

Scenario2:

“CSM Name Calculated1” used at Conditional wait 1

“CSM Name Calculated2” used at Conditional wait 2

“CSM Name Calculated3” used at conditional wait 3

 

Thanks

Userlevel 7
Badge

If I use this in a long program where I want to evaluate the same field at multiple times (let’s say 3 times) during a program. Will I need a calculated field for each conditional wait or can I use the same calculated field at each conditional wait?

 

Scenario1:

“CSM Name Calculated1” used at 3 separate conditional waits to check for a change in CSM

Scenario2:

“CSM Name Calculated1” used at Conditional wait 1

“CSM Name Calculated2” used at Conditional wait 2

“CSM Name Calculated3” used at conditional wait 3

 

Thanks

Scenario 1 should do it. Tagging JO product manager @nitisha_rathi to confirm though.

 
Userlevel 7

If I use this in a long program where I want to evaluate the same field at multiple times (let’s say 3 times) during a program. Will I need a calculated field for each conditional wait or can I use the same calculated field at each conditional wait?

 

Scenario1:

“CSM Name Calculated1” used at 3 separate conditional waits to check for a change in CSM

Scenario2:

“CSM Name Calculated1” used at Conditional wait 1

“CSM Name Calculated2” used at Conditional wait 2

“CSM Name Calculated3” used at conditional wait 3

 

Thanks

Scenario 1 should do it. Tagging JO product manager @nitisha_rathi to confirm though.

One calculated field can be used in multiple conditional waits. No need to create separate fields for multiple conditional waits.

Reply