Constituent Email Status

Options

The EMAIL_STATUS field on the Convio Consitutent record influences the deliverable state of the Constituent. The EMAIL_STATUS field may hold one of four distinct states.

  • Unknown: The email address has recently been added to the Constituent360 database. This address has not been associated with any action on the site or response to email that might validate it.
  • Good: The email address has been associated with an action on the site or has responded to an email that has targeted it such as opening or clicking through.
  • Bad (Soft Bounce): The recipient domain has responded with a 4xx error (temporary) when attempts have been made to deliver to this address.
  • Bad (Hard Bounce): The recipient domain has responded with a 5xx error (permanent) when attempts have been made to deliver to this address.

In each case where the EMAIL_STATUS has reached a state of Bad it is an indication that messages targeted at the record have not arrived as intended. Though both Hard and Soft Bounces are distinguished as bad there are distinct differences in how these are handled by the Convio product. Please note that the treatment of Bounces differs between platforms (see: http://community.customer.convio.com/docs/DOC-1931).

Soft Bounce:

  • The Soft Bounce status WILL NOT prevent a constituent from being targeted by an email campaign.
  • The status of Soft Bounce is used in the determination of what pool IP from which to source the message.
  • Soft Bounce count will be incremented as successive Soft Bounces are returned for an email address.
  • No number of successive Soft Bounces will result in a constituent being marked as Hard Bounce.

Hard Bounce:

  • The Hard Bounce status WILL prevent a constituent from being targeted by an email campaign.
  • The status of Hard Bounce is achieved when 2 successive Hard Bounces are recorded with no intervening action atributable to a message received after the initial Hard Bounce.
  • The Hard Bounce status and Hard Bounce count will automatically* be reset after an intervening action atributable to a message received after the initial Hard Bounce.
  • The Hard Bounce status and Hard Bounce count will automatically be reset if the constituent email address is updated by a data import or action altering the constituent record.

* This is configurable at the site level and may be disabled though it is on by default. Disabling of open rate tracking and click through details does hamper the function of this feature. These too are on by default.

Tagged:

Comments

  • Thanks TJ, this is really great information. A couple questions about Soft Bounces:

    - If a soft bounce is never resolved, will it stay in the Bad (Soft Bounce) status forever and keep receiving email?

    - Are soft bounces sent from a totally different IP pool than the client is in? Does the number of soft bounces in our Center affect which pool IP our Good emails are sent from?



    Vanessa

  • - If a soft bounce is never resolved, will it stay in the Bad (Soft Bounce) status forever and keep receiving email?

    The soft bounce status will change only when the constituent record is updated via direct manipulation by an admin, the constituent, or interaction via an email. The record will remain in a deliverable state.

    - Are soft bounces sent from a totally different IP pool than the client is in? Does the number of soft bounces in our Center affect which pool IP our Good emails are sent from?

    Soft bounces are sourced from a different IP in the same pool. Soft bounces do not affected a client's pool assignment.

Categories