- 3,675,632 Users
- 11,602 Discussions
- 18,529 Comments
Issue appears to be the rules for table use and data sources in workbooks conflict
We have a form updated by an API to populate two tables and trigger a custom event in a program to send multiple campaign with serialized coupon codes. The root of the issue appears to be the rules for table use and data sources in workbooks conflict.
A data extraction key will only work for personalization if the designated data extraction key column names exist in both the Supplemental Table and the Profile List.
Declaring more than one column as data extraction key creates a composite key. That is, all column values must be the same between the Profile List and Supplemental table to obtain a match.
Yet in the campaign designer:
In campaign designer error message – Columns with the same name can cause issues with personalization and using aliases will not prevent this problem.
Any thoughts / suggestions to address this?