AJO: Looking for Guidance on Sending Multiple Emails Based on Multiple Qualifying Array Items

[RS195]

Hi Community,

I’m working on a use case in Adobe Journey Optimizer (AJO) and would appreciate any help or guidance from anyone who has dealt with something similar.

In this scenario, each customer profile includes an array of objects (for example: multiple accounts, policies, or loans). The business need is to identify qualifying items in that array based on eligibility criteria (such as status = active) and then send separate transactional emails - one email per qualifying item.

To give an example:

• A single customer profile contains three accounts.

• Two of those accounts meet the eligibility criteria.

• The result should be two separate emails, each containing the details of one qualifying account.

The challenge I’m facing is how to design this in AJO so that a single profile can trigger multiple emails when multiple items meet the conditions, instead of just one email listing multiple items.

I’d appreciate any insights, guidance, or examples of how others have approached this kind of one-to-many activation scenario in AJO.

Thank you!

[DavidKangni]

@RS195 

in AJO a profile can only be once in a journey so you won't be able to send two separate emails from the same journey by using the customer as identity.

work around:

• Use accounts as identity: pros, you will be able to achieve your use case. cons, it will increase your profile counts
• Use customer as identity and loop in the personalization to display all accounts in one email: pros: will catch all customer eligible, cons: it will send all details in on email 

Thanks,

David

[Ivan_Mironchuk · Accepted solution]

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/manage-journ...

We have a feature set to go live very soon *currently in limited availability - that will allow for secondary identity to be used for multiple journey entrances. This would meet your use case. 

[RS195]

@Ivan_Mironchuk 

Thank you, that’s very helpful and makes complete sense.

Just to clarify one last thing:
Since the Supplemental Identifier feature is still in Limited Availability, is there any other currently available capability in AJO that could help solve for the scenario where we need to send one email per qualifying item (such as one per status = active) without switching to a completely new identity structure?

Or would the best approach be to wait for the Supplemental Identifier to be available to us?

Appreciate any guidance on whether there’s a short-term solution we could consider while this capability is still rolling out.

Thank you again!

[Ivan_Mironchuk]

Hi @RS195 - i don't believe there is another way that would work well. We should be rolling out this feature by the end of this month for all customers. If this is delayed beyond July - we can look to enable your ORG specifically for Limited Availabilty. 

[RS195]

Hi @Ivan_Mironchuk, thank you again - this is extremely helpful.

Just one quick clarification based on internal discussion:

Our use case involves batch audience activation (not event-based). For example, we create a qualified audience in AEP with customers who may each have multiple qualifying accounts (stored as an object array). We’d like to send one email per qualifying account - meaning the same customer may need to receive multiple emails, triggered from a batch audience journey.

Can you confirm if the upcoming Supplemental Identifier feature will also support batch journeys (using secondary identity like Account ID), and allow multiple entries per profile in that scenario?

Also, would there be any configuration or schema-level requirement we should be aware of to use this once it's available?

Appreciate your guidance - thanks again!

[ReenaJohn]

@RS195 , the supplemental ID feature works only on event triggered journeys and not for batch audience at this point in time.

However, you could explore and test if the API reference used for 'sending multiple messages in single HTTP request' can mimic the batch evaluation and work for batch journeys. In that case the journey can be event triggered but would take multiple requests at the same time. Have not tried it out myself, but it might help out in the scenario you have mentioned.

Send Multiple Messages in a Single HTTP Request | Adobe Experience Platform

Warm Regards,

Reena John