Skip to main content
added 13 characters in body
Source Link
Gortonington
  • 30.9k
  • 3
  • 27
  • 64

I have marketing cloud automation set up that puts our end users into one of 6 groups based on last character of their ID. Every month we send out an NPS Survey on the first Tuesday of every month and the second Tuesday of every month. We have used SQL to make sure when we send the reminder to the same Group - they don't get the reminder if they filled it out on the first send.

This is the SQL statement we used to prevent folks from getting it twice - unfortunately it did now work and many people got two surveys a week apart and are NOT happy.

The is the statement (it validates ok) - what is the error?

WHERE a."Group"='Group3' AND (b.PL_NPS_SubmissionDate > DATEADD(day, -30, getdate()) OR b.PL_NPS_SubmissionDate is Null)

WHERE a."Group"='Group3'
AND
(b.PL_NPS_SubmissionDate > DATEADD(day, -30, getdate())
OR
b.PL_NPS_SubmissionDate is Null)

I have marketing cloud automation set up that puts our end users into one of 6 groups based on last character of their ID. Every month we send out an NPS Survey on the first Tuesday of every month and the second Tuesday of every month. We have used SQL to make sure when we send the reminder to the same Group - they don't get the reminder if they filled it out on the first send.

This is the SQL statement we used to prevent folks from getting it twice - unfortunately it did now work and many people got two surveys a week apart and are NOT happy.

The is the statement (it validates ok) - what is the error?

WHERE a."Group"='Group3' AND (b.PL_NPS_SubmissionDate > DATEADD(day, -30, getdate()) OR b.PL_NPS_SubmissionDate is Null)

I have marketing cloud automation set up that puts our end users into one of 6 groups based on last character of their ID. Every month we send out an NPS Survey on the first Tuesday of every month and the second Tuesday of every month. We have used SQL to make sure when we send the reminder to the same Group - they don't get the reminder if they filled it out on the first send.

This is the SQL statement we used to prevent folks from getting it twice - unfortunately it did now work and many people got two surveys a week apart and are NOT happy.

The is the statement (it validates ok) - what is the error?

WHERE a."Group"='Group3'
AND
(b.PL_NPS_SubmissionDate > DATEADD(day, -30, getdate())
OR
b.PL_NPS_SubmissionDate is Null)
Source Link

Automation to prevent duplicate emails from sending a week apart

I have marketing cloud automation set up that puts our end users into one of 6 groups based on last character of their ID. Every month we send out an NPS Survey on the first Tuesday of every month and the second Tuesday of every month. We have used SQL to make sure when we send the reminder to the same Group - they don't get the reminder if they filled it out on the first send.

This is the SQL statement we used to prevent folks from getting it twice - unfortunately it did now work and many people got two surveys a week apart and are NOT happy.

The is the statement (it validates ok) - what is the error?

WHERE a."Group"='Group3' AND (b.PL_NPS_SubmissionDate > DATEADD(day, -30, getdate()) OR b.PL_NPS_SubmissionDate is Null)