Leveraging Customer Profile Array Data for Activation and Personalization in AJO Journey | Community
Skip to main content
April 25, 2024
Solved

Leveraging Customer Profile Array Data for Activation and Personalization in AJO Journey

  • April 25, 2024
  • 2 replies
  • 1017 views
Our Customer Profiles contain an Account array. This array contains data for multiple accounts per Customer Profile. It contains fields such as Product Type, Balance, Product Code, Account Number, Account Last 4 Digits etc. We have a few use cases that require accessing the data within this array for email personalization and/or activation.

Example
We create an Audience of customers who have an account with:
Product Type: Checking
Balance: Greater than $10,000

The audience gives us our list of profiles for activation - We want to send an email to this audience using a Journey within AJO, but we want to include the Account Number in the email from the specific account from the Account Array that qualified the customer for the audience.

1. I believe that this can be done by replicating the Audience rules as logic within personalization
          a. What does the code look like in Email Personalization for accessing the Account Number in the Account Array for finding the Account that has Product Type = 'Checking' and Balance > $10000?

2. Is there any other way to access the Account Number in the qualifying account?

3. If we also store an email address (an Email Address for each account in the Account Array) that we want to use this to send the email (rather than the customer level Email Address) - how can this be accomplished?
 
Thank you for taking a look and for any help or advice provided!
 
-Michael
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SatheeskannaK

@michaelbailey 

1. I believe that this can be done by replicating the Audience rules as logic within personalization
          a. What does the code look like in Email Personalization for accessing the Account Number in the Account Array for finding the Account that has Product Type = 'Checking' and Balance > $10000? - Take a look at this thread and documentation on how to personalize using the functions available.

 

2. Is there any other way to access the Account Number in the qualifying account? - Yes. You can access the account number to personalize the qualifying account. Refer to the thread shared.

 

3. If we also store an email address (an Email Address for each account in the Account Array) that we want to use to send the email (rather than the customer level Email Address) - how can this be accomplished? - You can override the execution email address value at a journey level to send to a different email address. Refer to this documentation.

2 replies

Adobe Employee
April 25, 2024

Hi @michaelbailey,

What product you are using to personalise and send the message/email?

Regards,

Kumar Saurabh

April 25, 2024

This is using the Email action in an AJO Journey

SatheeskannaK
Community Advisor
SatheeskannaKCommunity AdvisorAccepted solution
Community Advisor
April 25, 2024

@michaelbailey 

1. I believe that this can be done by replicating the Audience rules as logic within personalization
          a. What does the code look like in Email Personalization for accessing the Account Number in the Account Array for finding the Account that has Product Type = 'Checking' and Balance > $10000? - Take a look at this thread and documentation on how to personalize using the functions available.

 

2. Is there any other way to access the Account Number in the qualifying account? - Yes. You can access the account number to personalize the qualifying account. Refer to the thread shared.

 

3. If we also store an email address (an Email Address for each account in the Account Array) that we want to use to send the email (rather than the customer level Email Address) - how can this be accomplished? - You can override the execution email address value at a journey level to send to a different email address. Refer to this documentation.
Thanks, Sathees