Split one offer by several suboffers
Hello!
I have following case: I have customer base and each customer has his own language. In total I have 8 languages and it represents in customer table under Language variable. Now I want to launch campaign and I have to split one offer to 8 languages. What I can do is to use Segment and Filter component in marketing strategy and send to each customer appropriate offer on his language (for example in filter I'm setting Language="EN" etc.). But then for this way I need to create 8 Offer flow with same logic, only one component will differ is Email.
Now question is: Is it possible to do step of splitting offer by languages in Offer Flow using Decision table? If yes, then how? And what is better practice for this particular case to split offer by languages in Marketing Strategy or in Offer Flow if it is possible? (I'm using Pega Marketing 7.13)
Thank you!
***Updated by moderator: Lochan to add Categories***
Accepted Solution
Pegasystems Inc.
US
Circumstancing as described is certainly an option, but I would not recommend circumtancing the treatment as it is technically cumbersome and would make it tied to language going forward (you can't change circumstanced variable over time).
My recommendation is to use a segment of all eligible customers, irrespective of their language. Create a single offer. In that offer, split the email delivery to use email shape for every language. Use a decision shape (use a decision table that references the customer language field) before the email that directs the flow to the right language email shape. Example image of an offer flow below.
Pegasystems Inc.
IN
Hi Erzhan_E,
I guess you want to send emails in the same language as the Customer has. For this can you not circumstance the email treatments?. You can define the email treatment to be circumstances on ".Customer.Language" property and define each version for the language to be supported.
This way you have just one offer flow with one email shape but at run time the platform will pickup the correct email based on the circumstance configuration.
Thoughts?
Thanks,
Raghu
Accepted Solution
Pegasystems Inc.
US
Circumstancing as described is certainly an option, but I would not recommend circumtancing the treatment as it is technically cumbersome and would make it tied to language going forward (you can't change circumstanced variable over time).
My recommendation is to use a segment of all eligible customers, irrespective of their language. Create a single offer. In that offer, split the email delivery to use email shape for every language. Use a decision shape (use a decision table that references the customer language field) before the email that directs the flow to the right language email shape. Example image of an offer flow below.