Hello,
I’m working on a banking use case that requires adherence to regional data storage policies, which mandate that PII data must not be stored outside the country. Since the AEP data center is not located within the country, storing PII data in AEP is not an option. I’m considering pseudonymizing emails to handle this issue.
However, I need guidance on how to effectively use emails in AJO Journeys for targeting personalized offers under these constraints. Could you please suggest best practices for storing and utilizing such PII data for AJO activation?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
think about below option
- Created a data source [storing email id in your region ] with a GET call to an external API to pull the data.
- Used update activity to update profile data with the data received from the GET call.
- Journey created to use the updated profile data to personalize.
think about below option
- Created a data source [storing email id in your region ] with a GET call to an external API to pull the data.
- Used update activity to update profile data with the data received from the GET call.
- Journey created to use the updated profile data to personalize.
Hello @aaanuk2016 AJO will need the plain email to send email and it will then store that information in logs. So you will have to share PII data to make it work.
Views
Likes
Replies
Views
Like
Replies