Skip to Content
Author's profile photo Matthias Reiner

Hybris Marketing Cloud Email Campaigns – Feedback handling Amazon SES

As you might know there is two out-of-the-box Email Service Provider (ESP) interfaces you can use to send marketing mails triggered from Hybris Marketing Campaign Execution.

– SAP Mobile Services and
– Amazon Simple Email Services.

Since we got many questions around how Hybris Marketing handles the feedback and responses from the ESP, we’d like to provide some detailed insights based on the Amazon example.

The table below the lists the potential negative response codescoming from Amazon SES while trying to deliver the the marketing mails to the target group members assigned to the Email Campaign.

Based on the codesin the right column, in Hybris Marketing Interaction Types (left column) with respective reasons (second from left) are created in the system.

Only the hard bounce would result in an invalidated email address (facet) in the interaction contacts’ golden record.

Soft bounces would not trigger actions out-of-the-box. However there is a BAdI which could be used (CUAN_IMPORT_IA_4_IC) to implement custom logic based on the respective interaction type.

Sample coding is available for “EMAIL_BOUNCE_HARD”, so it is very little effort to implement something similar for “EMAIL_COMPLAINT” – just a few lines of code.

 

Interaction Type Interaction Reason Description Amazon SES response code
EMAIL_BOUNCE_HARD EMAIL_INVALID Email Address Not Valid N/A
NO_EMAIL Target email address does not exist

IF lv_bounce_type = ‘Permanent’.

‘General’ OR ‘NoEmail’

SUPPRESSED Email was invalid before

IF lv_bounce_type = ‘Permanent’.

‘Suppressed’

EMAIL_BOUNCE_SOFT ATTACHEMENT_REJECTED Rejected due to suspicious attachment ‘AttachmentRejected’
CONTENT_REJECTED Rejected due to suspicious content ‘ContentRejected’
MAILBOX_FULL Mailbox is full ‘MailboxFull’
MESSAGE_TOO_LARGE Message is too large for the inbox ‘MessageTooLarge’
EMAIL_COMPLAINT ABUSE Unsolicited email ‘abuse’
AUTH_FAILURE Email authentication failed ‘auth-failure’
FRAUD Potientially fraud ‘fraud’
NOT_SPAM Mail was classified as spam before ‘not-spam’
VIRUS Mail might contain a virus ‘virus’

 

Implementation Class: CL_CUAN_MKT_EXEC_EMAIL_AMZN

Implementation Method: PROCESS_RESPONSE_BOUNCE

 

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Joyca Vervinckt
      Joyca Vervinckt

      Hello Matthias,

      Thanks for this interesting blog.

      This blog describes Amazon SES in detail, but do you also have some insights on the SAP Mobile Services handling?

      Because for example the interaction type "EMAIL_COMPLAINT" doesn't seem to be available with SAP MS, and neither all of the Interaction Reasons...

      Kr,

      Joyca

      Author's profile photo Catherine Durieux
      Catherine Durieux

      Hey Joyca,

      I heard from SAP mobile services that this should be available now.

      Maybe good to know 😉

      Regards

      Catherine

      Author's profile photo Tobias Schneider
      Tobias Schneider

      Hi Matthias Reiner,

      I know that blog is a little bit old, but is it possible to prevent SAP Marketing Cloud from deleting the email-addresses from Contacts that had a HARD_BOUNCE interaction using that BAdI?

      Would really appreciate your help since we cannot work with that standard hard bounce handling of SAP Marketing Cloud...

      Kind Regards

      Tobias