TMS Hardbounce Processing

Former Member
Former Member $organization

Need a customized LP_UPDATE_HARDBOUNCES

 

Can someone share their version of LP_UPDATE_HARDBOUNCES where they addressed getting the correct email address because TR_EADDRESS_TYPE values are used across extractions.

  • I held off doing this as I believe Wordfly (TMS version 2) will start populating the eaddress field in t_promotion, which I assume would be with the email address that was used for the mailing.

    At the moment I just check for at least 3 hardbounces recorded against the customer, when the eaddress field is populated with Wordfly I will adjust the swl to check that the email address being used has 3 hardbounces agains it.

    I am hoping that Wordfly will be launched soon, I know they have a Webinar scheduled in December for it.

    Mark

  • Former Member
    Former Member $organization in reply to Mark Ridley

    Thanks!  So did you simply use the default LP_UPDATE_EMAIL_PROMOTION script and move the RETURN to the bottom of it?

  • We left LP_UPDATE_EMAIL_PROMOTION alone as TMS was automatically updating t_epromotion_response_history with the various events.

    I just added an extra segment to my extractions that excluded people with 2 or more rows in this table with a response of 2 (hard bounce) or with 4 or more rows with a response of either 2 (hard bounce) or 5 (unsubscribe).

    Once the new version of Wordfly launches will see if I can backfill the relevant table with the current primary email address and then change sql to check that the hard bounces are against the customer and their primary email address with at least 2 attempts recorded.

    Mark