Triggered Smart Campaign called multiple times | Community
Skip to main content
Jo_Pitts1
Community Advisor
Jo_Pitts1Community Advisor
Community Advisor
June 17, 2020
Solved

Triggered Smart Campaign called multiple times

  • June 17, 2020
  • 2 replies
  • 5140 views

Hi there.

I have a Smart Campaign that is triggered by multiple data value changed entries in the Smart List section.

It works just fine, however if multiple fields get changed at the same time for a Lead Record, the campaign gets called multiple times.  Technically, things still seem to work fine - but it is REALLY ugly.

Nothing in the Run each person through the campaign flow: settings is granular enough, and even if it were, I wouldn't want to use it as there is the potential a record may be updated twice in close succession, and I'd want the smart campaign triggered twice.

Is there a way around this?

Cheers

Jo

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Append all the fields into a unified history field at once with a suitable delimiter:

 

  {{lead.field one}}|{{lead.field two}}|{{lead.field three}}

 

Trigger on Data Value Changes  to that field. 

2 replies

BenjaminJacquet
BenjaminJacquet
Level 2
June 17, 2020

Have you tried setting an additional filter looking at an action in the Flow (e.g. Not was sent email, Not Program Status was changed etc.) in the past 1-2 seconds? Could be worth some testing 🙂

Jo_Pitts1
Community Advisor
Jo_Pitts1Community AdvisorAuthor
Community Advisor
June 17, 2020

@benjaminjacquet ,

that could work but any arbitrary time scale will at some point be wrong in this kind of situation. 

I was really hoping I could use a calculated field in the Data Value Changes, but no such luck.

    P
    PhillipWi1
    Level 9
    June 17, 2020

    You could maybe try date stamping when the campaign was last run using the {{system.datetime}} token into a custom field. Then add in as a filter to your program "(custom field) is not within the last x minutes", or something similar.

     

    Would that work?

    SanfordWhiteman
    SanfordWhitemanAccepted solution
    Level 10
    June 17, 2020

    Append all the fields into a unified history field at once with a suitable delimiter:

     

      {{lead.field one}}|{{lead.field two}}|{{lead.field three}}

     

    Trigger on Data Value Changes  to that field. 

      Jo_Pitts1
      Community Advisor
      Jo_Pitts1Community AdvisorAuthor
      Community Advisor
      June 18, 2020

      Hmmm.. so have to have the append stuff everywhere any of those fields might change (i.e. form submits and API calls).

      Not as elegant as a calculated field, but cest la vie 🙂

      Terms & ConditionsAccessibility statement

      Loading footer...