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

      Show previous replies
      dan_ahrens
      dan_ahrens
      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.

      In that situation then you might want to consider adding a custom field on the Company Person record to allow different programs to “communicate” with each other. Rules could set the status of that field, which could be a boolean, or more complex variations with alphanumerical codes. 

      VP of Customer Success at Forcepoint
        bradley
        bradley
        Expert ⭐️
        January 8, 2021

        @dan_ahrens I was actually just thinking about that earlier today and you’re right, that’s how it needs to be done today. Would be nice if the solution was a bit more direct though :)

          HollySimmons
          HollySimmons
          Helper ⭐️
          January 13, 2021

           having to include a dataset for the sole purpose of excluding via transform

          @kelly can you just explain very quickly how you do that?

          I’m looking to exclude people from Y program who received X program (its just a single email) in the last Z days. Thank you!

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

            @HollySimmons You’ll need a participant data set and filter the frequency within that dataset (anyone that entered program in the last 30 days). With the merge, retain all records from the primary dataset and when you have your final output you’ll do a transformation task.

            In the transformation task add the participant email address to the filter section so participant email = null, that way the final output will only contain contacts that were not participants in the last 30 days.

            Be careful in your participant data set that you are pulling in the participant created date and not the program created date.

              HollySimmons
              HollySimmons
              Helper ⭐️
              January 13, 2021

              Ahhh amazing thanks so much @kelly - all makes sense. 

              For background (for the original request) we would also love to be able to exclude via rules, we want to run 4 separate programs that have large overlapping audiences but we only want someone to be in one of the programs at any one time. They can re-enter the same program every 90 days, but can enter a different one 30 days after completing another. 

                kvanderwyk
                kvanderwyk
                Contributor ⭐️⭐️
                January 26, 2022

                This would be supremely useful as right now we can’t edit an existing program to make small changes like to the Conditional Waits, and instead need to clone and rebuild. This leads to duplicate programs and gets confusing quickly.

                  linny75
                  Contributor ⭐️⭐️
                  June 1, 2022

                  What updates are there on movement to simplifying  excluding customers that have already been sent an email from a program? 
                  It’s not a straight forward process and impacts customer experience. 

                  kelly
                  kellyAuthor
                  Helper ⭐️⭐️⭐️
                  March 14, 2024

                  Are there any updates to this? And with the migration to the new platform this is somehow marked as a New idea that is > 4 years old?

                    Terms & ConditionsAccessibility statement