We have been using offers in our email deliveries that contain personalization just fine.
For deliveries that have a file extraction, reference to [proposition/offer/view/textSource] is empty. The text content in the offer contains something like "Hi <%= recipient.firstName %>"
In the file extraction expression where do I get the text field that has been processed for personalization? Do I have to configure something in the offer space to make this work for non-email channels?
Has anyone have an example using an offer with personalization in a delivery with a file extraction, e.g. direct mail?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi,
Offers work the same in direct mail as any other channel.
Follow these steps:
You can also specify the offers in the delivery itself, easier to manage when they're in the workflow though.
Thanks,
-Jon
Hi,
Offers work the same in direct mail as any other channel.
Follow these steps:
You can also specify the offers in the delivery itself, easier to manage when they're in the workflow though.
Thanks,
-Jon
Thanks Jon for taking a look at this. my question was really around personalization in the offer content, but it looks like you indirectly answered my question with "xml fields like @Title won't work here." I was trying to use the text content ([proposition/offer/view/textSource] ) field which is similar to the @Title field you mentioned.
Is there a way to store the personalized content of these XML fields in the propositionRcp schema so that personalization in the offer content is possible for non-email deliveries? or is this unique to email deliveries only?
Views
Replies
Total Likes
@Jonathon_wodnicki Can you please help @kevinh95689533 further? Thanks!
Views
Replies
Total Likes
Views
Like
Replies