Custom response codes for consortiums

You are part of a consortium and you want to make sure your organization responses are separate from the others. WordFly handles unsubscribes at the organization level, when you're a consortium we'll just need to figure out which organization is responsible for the email and map the custom responses.

Topics covered in this article:

How are WordFly email responses handled in Tessitura

Varying email responses for consortiums

Varying control groups for consortiums



How are WordFly email responses handled in Tessitura?

It all comes down to some customization in the LP_UPDATE_EMAIL_PROMOTION stored procedure which handles email responses in Tessitura. There are several ways this can be implemented for consortiums. The recommended approach is to do this based on the control groups and unique email responses for each consortium.


Note: preference updates are handled by a separate stored procedure.


Here's a snapshot of Control Groups in security context



The LP_UPDATE_EMAIL_PROMOTION stored procedure gives you access to handle each email response available to drive custom processing. You can configure this stored procedure to handle email responses for each consortium uniquely.


Here are some things to consider about the response processing:

  • Response Code: passed to local procedure
  • Customer Number: passed to local procedure
  • Source Number: passed to local procedure
  • Email address: from T_PROMOTION by source_no & customer_no
  • Media Type: from T_PROMOTION by source_no & customer_no
  • Control Group: from T_APPEAL, TX_APPEAL_MEDIA_TYPE by source_no
  • Source Group: from TR_SOURCE_GROUP, TX_APPEAL_MEDIA_TYPE by source_no


The next section of this support article reviews how you can vary your email responses for each consortium member.




Varying Responses for Consortium Licensees

There are a couple ways you can vary responses for consortiums so that unsubscribes, opens, clicks and bounces are all logged correctly for each member.


You can use Source Group or Media Type to differentiate responses for an organization. Or, you could set up new response codes for each consortium and use that to update email responses correctly for each sub-license. It's probably easiest to use a custom response code for each organization.


If you do use custom responses for each sub-license, WordFly will need to configure the accounts to use those responses instead of the defaults.



New email responses are set up in TR_EMAIL_RESPONSE_CODE and reference the TR_RESPONSE table. WordFly has to update each account to use the appropriate response codes from TR_EMAIL_RESPONSE_CODE. Please send us a screenshot of TR_EMAIL_RESPONSE_CODE so that we can configure each account appropriately. 


Example screenshot of TR_EMAIL_RESPONSE_CODE showing the values a consortium might have set up for two consortium members holders...





Varying Control Group for Consortium Licensees

Control groups in Tessitura help define what data is available to WordFly and for each consortium member. For example, with the correct control group selected your organization will see only your lists in WordFly (without the correct one selected you might see list data from other sub-license holders in your consortium.


Data governed by control groups include:

  • Extractions
  • Downloads (via Extractions)
  • Lists Manager lists
  • Output Sets
  • Appeals


When a consortium starts using WordFly your WF-Tessitura integration is set up a unique control group which is defined by your TMS User in T_Defaults.


There are 4 points to help vary the control group for sub-license holders.


1. Create an organization for each licensee in TR_ORGANIZATION


2. Set Multiple TMS User values in T_DEFAULTS using TR_ORGANIZATION.description as parent_table


3. Map each TMS User to a different User Group


4. Map each User Group to a different Control Group






Have more questions? Submit a request
Powered by Zendesk