Marketing campaigns based on different customer objects
We have a requirement to support marketing campaigns based on the Customer objects sourced from different database tables. Having two or more Pega applications built on PegaMKT and use different Customer classes is not possible option. Using Customer class inheritance also does not seem to work in this case. Should we consider deploying multitenant system, each tenant having its own Marketing Portal?
Can anyone share their expertise as to how such a solution should be architected.
Thanks for your question. In order to better answer your question, can you give examples of the type of different customer objects that you have and the type of differences in campaigns between those objects?
Per the requirement, two campaigns are based on customer from different domains, one is associated with sales and account information, the other with maintanance and support information. Two data sets have very little overlap and combining them into single customer will create design and run-time mutual impact.