"Not email was sent" error constraints or filters & triggers | Community
Skip to main content
Grégoire_Miche2
Level 10
November 5, 2015
New

"Not email was sent" error constraints or filters & triggers

  • November 5, 2015
  • 4 replies
  • 3124 views

When analyzing what's not happening, it's impossible to count the leads who were targeted but were not sent an email. And yet, it is very important that we can easily measure how many leads were hit by a communication limit, how many were in fact suspended, unsubscribed, blacklisted or with an invalid email. Of course, you can do it smart campaign by smart campaign, but it's impossible to get a global view.

We would need that either the "not email was sent" provides constraints to select reasons such as :

  • communication limits,
  • suspended,
  • unsubscribed,
  • email invalid,
  • previously hard bounced
  • Duplicate email address in the target
  • etc...

or have a specific filter

A dedicated trigger "Email could not be sent" with all these previous constraints would be fabulous, as, based on the reason, we could immediately trigger alerts or set tasks for corrective actions.

-Greg

4 replies

Justin_Cooperm2
Level 10
December 11, 2015

I love this idea, but don't you think it would be constraints on "not was delivered email"

Grégoire_Miche2
Level 10
December 12, 2015

Hi @Justin Cooperman,

Marketo run the filters BEFORE sending in case of communication limit, opt-out, email invalid emails (incl. previously hard bounced) and do not even send the email. So we really need the constraints on the "not was sent email" filter, since as the email is not event sent, the "not was delivered" email would not return any of these leads.

And also need the trigger, if possible

-Greg

Justin_Cooperm2
Level 10
December 14, 2015

Ok, I get it. I actually think it might warrant an entirely new filter. We probably wouldn't want to add it to "not was sent email" because that should really mean the lead was never included in any campaign that attempted to send the email.

Maybe something along the lines of "was prevented from being sent email" with constraints.

I still also think we should add constraints to "not was delivered email" to identify some of the deliverability failures.

Grégoire_Miche2
Level 10
February 24, 2016

Just to show how painful it can be without that filter, read this post:

My email was not sent: a troubleshooting guide

The filters in this idea would make understanding what did not work as expected so simple...

-Greg

April 27, 2016

Any updates on this? We were just directed by our support engineer to add this as an idea.

February 6, 2020
No text available