nFE 2014 & 2015 Writebacks

Informz sends updates, known as writebacks, to netFORUM Enterprise for various activities that occur within Informz. By writing back information from Informz to netFORUM Enterprise, you maintain data integrity and ensure that the two databases stay coordinated with one another.

There are two types of writebacks that can occur with netFORUM Enterprise: subscriber status writebacks and mailing activity writebacks. Mailing activity writebacks are optional.

Subscriber status writebacks include Unsubscribe (Date), Unsubscribe Reason (if provided), Bad Email Status, and Resubscribe (Date).

Mailing activity writebacks include Sent Date, Opened Date, Click (Date and Link), Block, Bounce, Social Sharing, and Send a Friend.

How to View Writebacks

Navigate to Admin > Setup > Bridge Configuration.

Click Writeback List to see all pending, completed, and failed writebacks.

How to Establish Mailing Activity Writeback Settings

Navigate to Admin > Setup > Bridge Configuration.

Click Writeback Settings to see the available writeback options.

Mailing activity writebacks can be set to report on a mailing’s sent and opened status. Additional writebacks are available for other mailing attributes as well, indicating subscribers’ level of engagement with a mailing.

You can manually send writebacks to netFORUM Enterprise on an ad hoc basis using the Send Activity option on the Mailing List > Sent tab. Hover over the menu icon and click Send Activity.

Alternatively, you can set mailing activity writebacks to occur automatically (daily or weekly) or manually. All automatic activity can be controlled to a time of day, day of week, and day interval. Furthermore, many writebacks can be disabled if they are not needed for a particular mailing.

To stop a writeback from occurring (i.e. deactivate the writeback), uncheck the corresponding checkbox on the Writeback Settings page.

Note that Unsubscribe, Resubscribe, and Bad Email writebacks cannot be deactivated.

Informz Data in netFORUM Enterprise

Mailing activity writeback data appears in netFORUM Enterprise under the Messaging Activity on the Correspondence tab of the Individual profile.

A mailing activity writeback sends the following data:

Column Data
Activity Code "Informz Mailing"
Subcode Type of mailing activity interaction (e.g. Sent, Open, Click)
Message Name (Sent) "Mailing was sent"
Message Name (Open) "Mailing Action | Device Used | Client Used | Country"
Message Name (Clicked Link) "Hyperlink was clicked"
Message Name (Clicked Ad) "Advertisement was clicked"
Email Email Address
Date Mailing Send Date
Link Label N/A - not written back at this time

Unsubscribe

When subscribers unsubscribe, it indicates that they no longer wish to receive any mailings from the organization. This option is required for CAN-SPAM compliance. Informz tracks any unsubscribe requests that come from a mailing or from the Informz administrator. These are stored in a queue and sent to netFORUM Enterprise every ten minutes.

Unsubscribe data is found under the Messaging Activity on the Correspondence tab of the Individual profile.

An unsubscribe writeback sends the following data:

Column Data
Activity Code "InformzUnsubscribe"
Message Name Date and Time of the unsubscribe (along with the source of the unsubscribe action)
Email Email address
Date Date of the unsubscribe

Resubscribe

When an Informz administrator manually resubscribes a subscriber, Informz will write back to netFORUM Enterprise. Like unsubscribes, resubscribes are stored in a queue and sent every ten minutes. A resubscribe removes the corresponding data from the individual in netFORUM Enterprise, and the Do Not Contact by Email field is deselected.

The resubscribe needs to occur where the unsubscribe originally occurred.

  • If a customer unsubscribed via a link in an Informz mailing, the resubscribe must also occur in Informz.
  • If the unsubscribe occurs in netFORUM Enterprise (via the Exclude the recipient from all communications flag), the resubscribe must also occur in netFORUM Enterprise. Informz is updated during the next sync.