Skip to main content
New Idea

Allow Calculated Fields to be used in Variant Filtering

Related products:None
  • September 19, 2019
  • 5 replies
  • 79 views
john_apple
jean.nairon
angela_domenichelli
heather_hansen
kelly
+25
  • john_apple
    john_apple
  • jean.nairon
    jean.nairon
  • angela_domenichelli
    angela_domenichelli
  • heather_hansen
    heather_hansen
  • kelly
    kelly
  • darkknight
    darkknight
  • spencer_engel
    spencer_engel
  • dan_ahrens
    dan_ahrens
  • denim
    denim
  • travis_floyd
    travis_floyd
  • lori_dinardo
    lori_dinardo
  • ana_g
  • schagri
  • ml2019
    ml2019
  • andreammelde
    andreammelde
  • tippetts
    tippetts
  • bradley
    bradley
  • kstim
    kstim
  • sarahmiracle
    sarahmiracle
  • romihache
    romihache
  • alizee
    alizee
  • Molly.McQ
    Molly.McQ
  • ayyoung
  • camber
  • jenlpro
    jenlpro
  • dayn.johnson
    dayn.johnson
  • Stuart
    Stuart
  • Hawleynr
  • L.L
    L.L
  • andor_fuhrer
    andor_fuhrer

john_apple
We would like the ability to filter email variants within an Email step based on Calculated Fields.

We have a need to send variations based on certain actions taken by the customer which updates data from SFDC. In order to account for these variations, we need to create an email chain with multiple Conditional Waits/branches (using the same Calculated Fields) and send accordingly (multiple email steps). We'd like to just have one Email step and have the filtering based off of Calculated Fields take place all within one step.

5 replies

kelly
Forum|alt.badge.img+3
  • Helper ⭐️⭐️⭐️
  • 312 replies
  • February 5, 2021

This is a major need. Knowing I can’t use survey responses as variant filters, I just created a program with calculated fields to capture those responses only to realize those can’t be used as variant filters, either. 


travis_floyd
Forum|alt.badge.img+6
  • Contributor ⭐️⭐️⭐️⭐️
  • 39 replies
  • November 30, 2021

OK, adding to this one to establish a USE CASE since this still hasn’t gotten any traction…

I create an email chain JO, and send different versions of the email template based on the HEALTH of the customer.  After the first email goes out, we wait 1 week, and then send another email, but we want it to be based on the CURRENT HEALTH of the customer, not on the health when they entered the program!  Since calculated fields are not available for filters at the email template, I have to build 3 templates… one for RED, one for Yellow, and one for Green (or more if using a 5 scale, or 100 scale) and then use separate conditional waits that can look at the Calculated field to determine if the template should be used or skipped!  Highly inefficient… and my CS team wants me to build a 10 week version of this too!  The chain is going to be so long I won’t be able to see it to manage it!

 

PLEASE give this another look!


anirbandutta
Forum|alt.badge.img+2
  • Expert ⭐️
  • 1804 replies
  • December 1, 2021

@PavanCh pl check this thread


dan_ahrens
Forum|alt.badge.img+2
  • Expert ⭐️⭐️⭐️
  • 1984 replies
  • December 1, 2021

This is a strong use case @travis_floyd - you’ve got my upvote!


revathimenon
Forum|alt.badge.img+6
  • Gainsight Community Manager
  • 594 replies
  • April 3, 2025
The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings