SOLVED

Trigger Firing Question

Go to solution
Highlighted
Anonymous
Not applicable

Trigger Firing Question

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?

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Trigger Firing Question

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

View solution in original post

8 REPLIES 8
Highlighted

Re: Trigger Firing Question

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

Highlighted
Anonymous
Not applicable

Re: Trigger Firing Question

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

Highlighted

Re: Trigger Firing Question

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

View solution in original post

Highlighted
Anonymous
Not applicable

Re: Trigger Firing Question

Oh so something like this

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

Highlighted

Re: Trigger Firing Question

Yes. Just at a 4 or 5 seconds wait step before the first step, so that you leave Marketo enough time to post the form data to the database so that the smart list render accurately. 5 seconds in not 100% certains but will cover almost all the form fillouts. If you want more security, augment the delay to a couple of minutes.

Also, keep in mind that you might not even be allowed to keep the data from EU people.

-Greg

Highlighted
Anonymous
Not applicable

Re: Trigger Firing Question

Hi,

Does something like this work? Does the "subscription date" as null equal blank value? Because I want to timestamp everyone, but if they are indeed from the GDPR countries, I don't want to timestamp a subscription date, unless the check our checkbox on the form (which this is a separate smart campaign)

Screen Shot 2018-05-15 at 4.41.41 PM.png

Highlighted
Level 10 - Community Moderator

Re: Trigger Firing Question

You don't need multiple wait steps in there, Calon.  You want to wait after the Filled Out Form comes in, no need to wait after the Change Data Value is executed.

Highlighted

Re: Trigger Firing Question

Hi Calon,

+1 on Sanford for the unnecessary wait steps beyond the first one.

And yes, NULL keyword in a CDV flow step sets the field to blank. BUt you could also just empty the default choice, which would mean "do nothing".

-Greg