Problem Note 33510: SAS® Customer Intelligence Contact History is not updated with responses from SAS® Digital Marketing
SAS Customer Intelligence Contact History is not correctly updated if contacts are opted out or a hard-bounce notification is received from e-mails that are broadcast using SAS Digital Marketing.
When a broadcast is executed on behalf of SAS Customer Intelligence Studio, the individuals get added to Contact History initially by the campaign export. If they ultimately do not receive the e-mail because they are opted out or a hard bounce is received, SAS Digital Marketing is unable to successfully update the CONTACT_HISTORY_STATUS_CD variable for that contact history record to indicate the failure.
This is caused when multiple tracking variables are defined, in addition to the mandatory Subject ID and Response tracking code, and the name of the additional variable occurs alphabetically before the RESPTRACKING_CD field. For example, choosing EMAIL causes the failure to update whereas choosing ZIPCODE would not.
The underlying cause of the problem is that the process uses the alpahbetically first variable and assumes that it is the response tracking code. Because the response tracking code tag is used to locate the record to update in contact history, it fails because that tag is not RESPTRACKING_CD.
Unfortunately, no errors appear in any logs; the only indication that something is incorrect is that the contact history is not updated correctly.
To work around this issue do not use multiple tracking variables, or if you do, make sure they occur alphabetically after "RESPTRACKING_CD".
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Digital Marketing | Microsoft® Windows® for x64 | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows 2000 Advanced Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Datacenter Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Server | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows 2000 Professional | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows NT Workstation | 5.1 | | 9.1 TS1M3 SP4 | |
| Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Microsoft Windows XP Professional | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Windows Vista | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled AIX | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled HP-UX | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| HP-UX IPF | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
| Linux | 5.1 | 5.3 | 9.1 TS1M3 SP4 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2008-10-13 09:35:37 |
| Date Created: | 2008-10-02 14:33:42 |
