Identify skipped email send in Bulk Activities API

Identify skipped email send in Bulk Activities API

Hello All,

Is there a way to identify that the Email Send activity(activity id 6 ) captured in Bulk activities rest API is "Skipped person already used up Daily/Weekly communication limit"?

How can it be accomplished?

Thanks in advance,

Sumedha Parab

3 REPLIES 3
Highlighted

Re: Identify skipped email send in Bulk Activities API

You can't. It's a non-logged activity from an API standpoint.

You could maintain your own, separate counter of emails sent in a given day (using a Score field). Then you could predict prior to the Send Email step that it was about to be skipped and could set an Interesting Moment. However, this would be very difficult to manage across email assets.

Conversely, you could set an IM before attempting to send every asset. Then when there's neither a Sent nor Bounced log for a given email you can infer that it was skipped. Pretty heavy on resources though.

What is the importance of this data on your back end?

Highlighted

Re: Identify skipped email send in Bulk Activities API

Hi Sanford,

Thanks for the quick reply. 

We are developing a dashboard for top management to monitor the performance of multiple Marketing campaigns.

Email Send is one of the important parameters for calculating various business KPIs. 

Bulk Activities API is used to capture this as well as the other Lead activities. The reason for using Bulk Activities and not the individual APIs is the daily threshold API limit set by Marketo.

Please suggest whether this approach is correct or is there any better solution for the above requirement?

Warm Regards,

Sumedha.

Highlighted

Re: Identify skipped email send in Bulk Activities API

Email Send is one of the important parameters for calculating various business KPIs.

I would say Delivered is far more significant from a "top management" perspective. 

Reducing the number of people both Sent and Bounced is vital from a marketing ops perspective. But managing deliverability isn't a "put it in the CEO's dashboard" thing IMO. It's implicit, but not explicit.

Re: skipped sends, do you really want to bother top management by showing people who not only didn't get an email, but you didn't even expect to get an email (because you set communications limits)? That metric is again worth looking into ops-wise, but not publishing in a dashboard (unless you mean a CMO dashboard specifically).

The reason for using Bulk Activities and not the individual APIs is the daily threshold API limit set by Marketo.

Doesn't matter whether you use the paginated API or the bulk API, skipped sends aren't things that "happened." (Incidentally, you may not realize that an EP cast also isn't something that "happened"!)

Please suggest whether this approach is correct or is there any better solution for the above requirement?

The only close-to-practical approach would be what I mentioned with IMs.