Skip to main content
kelly
kelly
Helper ⭐️⭐️⭐️
April 30, 2019
New Idea

Queries as Exclusion List

Related products:CS Journey Orchestrator
  • April 30, 2019
  • 18 replies
  • 343 views
If Journey Orchestrator is moving towards allowing for Bionic Queries to be created outside of a Program, I'd like to request that BQ can also be used as an exclusion list. Every program I run, I have to include a dataset task that looks for anyone that already entered that program in the last 180 days, then merge it, then transformation task the results. Every. Program. It's really not intuitive to build exclusion criteria into a query.

It's an extra step that would be much easier to solve for if I had a separate query 'Entered Progam in X days', and then select that list under exclusions (which is how any other email tool works).

      18 replies

      john_apple
      john_apple
      Expert ⭐️
      April 30, 2019
      I agree. I was just talking about this limitation yesterday with a colleague. We use a CSV exclusion list on a few Programs, but it doesn't automatically updated. We have had to manually generate a new CSV and load it into the Program. It would be easier and more reliable to have the Program run the necessary query to update the exclusion list.

        dan_ahrens
        dan_ahrens
        Expert ⭐️⭐️⭐️
        April 30, 2019
        Hi Kelly,

        It sounds like you need to only allow participants if they were not already part of that program in the past 180 days, is that right?

        If so, this capability exists today: https://support.gainsight.com/Journey_Orchestrator_and_Email/Programs/Adding_Participants_to_a_Program#Filter_Criteria_on_Participants

        Look to the Advanced criteria shown below in number 3:



        VP of Customer Success at Forcepoint
        kelly
        kellyAuthor
        Helper ⭐️⭐️⭐️
        April 30, 2019
        Hi Dan, uniqueness criteria only matters for that specific program. However, there are many use cases where you need to stop a program to make an adjustment and relaunch it, and you want to be sure not to bring in any contacts that entered the previous version.

          cmultanen
          cmultanen
          Helper ⭐️
          May 1, 2019
          +1, would love to be able to have a dynamic exclusion list.

            heather_hansen
            heather_hansen
            VIP ⭐️⭐️⭐️⭐️⭐️
            July 18, 2019
            Running into this now. What about having an option to say Don't Pull in Participants from, and then, have a multi-select dropdown with all the programs so that you could easily exclude them?

              techtouchtam
              techtouchtam
              Contributor ⭐️⭐️⭐️
              February 25, 2020

              Another solution could be an exclusion CSV uploading to the newly created program from the Participant Activity. The question I am trying to answer is if I can delete the exclusions after say 180 days in the program, allowing these participants to filter back in if they meet the existing criteria.

              techtouchtam
              techtouchtam
              Contributor ⭐️⭐️⭐️
              February 25, 2020

              Another solution could be an exclusion CSV uploading to the newly created program from the Participant Activity. The question I am trying to answer is if I can delete the exclusions after say 180 days in the program, allowing these participants to filter back in if they meet the existing criteria.

              So I did just test this. Although it is not ideal.

              You can build a CSV inclusive of all members you want to exlcude for a period of time, set a reminder in your calendar (ex. 365 days in the future) to delete the exclusion list. Now these previously excluded members can enter the program again. I find building the a report containing multiple program titles and the participants is easier than modifying than entire query.

              kelly
              kellyAuthor
              Helper ⭐️⭐️⭐️
              July 9, 2020

              This is becoming a growing need - as we are building out more programs, we have to build program suppression into the query.

              I’m hitting the 15 step limit due to this - due to having to include a dataset for the sole purpose of excluding via transform. I really wish I could just have a query as a suppression list.

                kelly
                kellyAuthor
                Helper ⭐️⭐️⭐️
                January 8, 2021

                Any update to this? We’ll be enabling CSMs with the option to unsubscribe accounts on a program by program basis by way of CTA. I’ll have to build this dataset and frequency dataset into every program in order to exclude them. It would be much more efficient to simply have datasets under Exclusions than to have to built into existing and future programs. This is a desperately needed function.

                  bradley
                  bradley
                  Expert ⭐️
                  January 8, 2021

                  Hi Dan, uniqueness criteria only matters for that specific program. However, there are many use cases where you need to stop a program to make an adjustment and relaunch it, and you want to be sure not to bring in any contacts that entered the previous version.
                   

                  @dan_ahrens this is an important but subtle distinction that we’ll likely be running up at some point in the not too distant future ourselves. A way to do this via the rule, or a mechanism where each program can “talk” to each other so if one participant is enrolled in a program they aren’t pinged by another immediately after.

                    Show more replies
                    Terms & ConditionsAccessibility statement