Duplicate MQL Alerts to my BDRs

[Anonymous]

It's really odd. I been struggling to find the issue. I do appreciate you taking a look. Probably will open support case.

[ChristinaZuniga]

I've been experiencing this too, randomly. I haven't had time to track down the cause - if you open that ticket and get it resolved please update the thread !

[Anonymous]

The one thing that stands out here to me to troubleshoot is that the smart campaign trigger is set to "greater than". Wouldn't that trigger this campaign if their score changes multiple times when it is above 49? Per Calon's ask, can you go to the marketo lead record of a lead this is happening to and share that activity? If there are multiple score changes that looks like it may be a culprit.

Looking at an individual's activity history will also highlight other potential issues causing this. (FYI to view this activity, click on their name, which was hyperlinked in the last screen shot shared, and then at the top click over to the activity tab).

[Dan_Stevens_]

That's what I was hoping to glean by looking at the activity logs and campaign results.  But nothing jumped out a me as something that would cause this to trigger consecutively, at the same time.

[Anonymous]

Hi Jason,

Thanks for your thoughts. Here is a lead's history that this duplicate alert is going too. This isn't entire history, but a chunk of it.

[SanfordWhiteman]

Where's the Lead Score log line(s)?

[Anonymous]

Here is logging of lead score. Sorry for different sizes, but trying to copy as much as I could.

[SanfordWhiteman]

Looks to me like you have a race condition. As Jason highlights above, you're allowing someone to reenter the Trigger campaign when Lead Score changes and exceeds 49. (The Filter you have on the Trigger doesn't prevent reentry under accelerated circumstances.)

[Anonymous]

Thanks Sanford. Can you provide details to this. Sounds like you are on too something and would love to see if I can look into fixing this.

[SanfordWhiteman]

You should think of the steps of Trigger campaigns as running independently, interleaved with the steps of other campaigns.

So it's not just explicit Wait steps that can change the order of operations across different (or the same) leads. A burst of (nearly) simultaneous triggers can also create unexpected order. However, the Lead Score will only have one value at a time, so if you use Data Value Changes (not Score Changes) and constrain New Value/Old Value you should be out of the woods.