8 Replies Latest reply on May 15, 2018 11:32 PM by Grégoire Michel

    Trigger Firing Question

    Calon Alpar

      Hi all,

       

      Question about triggers. And it is related to our favorite friend GDPR. We have triggers fire when someone fills out a form to add them into our permission to email. Now with GDPR we need to exclude this for GDPR countries. Can I just add a Smart List filter to exclude these countries and going forward it will do this. Or will it now pull in past data and update the flow based on adding this new filter to the initial triggers?

       

      So basically clarifying if the triggers will be firing differently going forward?

        • Re: Trigger Firing Question
          Grégoire Michel

          Hi Calon,

           

          The trigger behaviour will not be change when GDPR becomes applicable on may 25th.

           

          It's your responsibility to exclude some people from your lists if you want to. You can do this based on a explicit country entry (a country field in the forms) or implicit (using inferred country or some IP based deduction).

           

          Pay a lot of attention to smart lists filters coming together with triggers: for performance reasons, they may bring inaccurate information if the field you are filtering from has just been entered in the form. Better use a smart list in a choice in the flow after a 4/5 seconds wait.

           

          -Greg

            • Re: Trigger Firing Question
              Calon Alpar

              Hi Grégoire,

               

              Thanks for this. My current setup is below:

               

              Basically anyone who is inbound or downloads content becomes permissioned. Big no no for GDPR incoming. So to exclude EMEA, I was going to add a filter here to exclude the below Smart List. Does this sound applicable?

               

              Also, confirming this would start triggering going forward? It wouldn't affect data retroactively?

               

              Screen Shot 2018-05-10 at 12.59.41 PM.png

               

               

               

               

              Screen Shot 2018-05-10 at 12.59.56 PM.png

                • Re: Trigger Firing Question
                  Grégoire Michel

                  Hi Calon,

                   

                  Triggers never fire retroactively. If you want to re-process your existing database (and you probably should), you will have to use the filters to detect persons that you should now exclude.

                   

                  Your triggers will fire OK, but rather that adding a member of smart is not GDPR countries as a filter below the triggers, do the following in the flow step

                  • Add a "wait 4 seconds" any the top of the flow
                  • add choices in the flow that say "is Not member of GDPR country, add to permission list with default do nothing"

                   

                  -Greg