I've added a property to the offer data which I called into the Email Template. When I test the Offer (by sending Email to SeedList) I can see the value of this property. But when I create a campaign and import the same offer in this campaign, I don't see this value in the email (after running the campaign).
Hi, when you say you created a new property under OfferData, do you mean you manually created it through the developer portal or you used the decisioning proposition landing page to do it or through the strategy ? - Doing it through proposition landing page would be the better approach (as there are some special custom fields added to the property.
Also where are you setting the value of the property ? Depending upon the version of Pega Marketing you are using you can use data flow debug tools to see if the SR property value is set in the preview mode of the data flow.
Hi, thank you for your answer. I really don't use a strategy in this campaign. It's an outbound campaign. My goal is to manage coupon codes. So, I developed a solution to assign a coupon code to every customer by email. Coupon codes are stored in a separate table (in a different schema with the customer table).
I added the coupon property in the email template, when I tested the offer with a Seedlist, Customers receive Coupons as needed. But when I try to send these coupons with Outbound campaign, Customers don't receive them.
Any idea about this issue ?
Thank you again for your help
Posted: 3 years ago
Posted: 3 Oct 2018 9:22 EDT
Sriram Coimbatore Krishnan (Sriram Krishnan)
Fellow, Software Architect, Outbound Runtime
So how are you pulling the data into the Campaign ? and what version of Pega Marketing are you using ? it looks like the coupon code what you have in the *other* table is not available for you in the campaign context. Campaigns pull the configured customer and associated tables - the latest version of Pega Marketing GA for ex 7.4 gives lot of flexibility in defining other sources of data for customer while running the campaign. But seems to be you are missing some configuration.
If you have PM 7.4, look at the dictionary configuration to see if the coupon table / class is defined there. You can also create a support case SR to get GCS help on this seemingly configuration issue.