Breaking one profile into multiple namespace actions

Forum|Forum|1 year ago
March 18, 2024
1 reply
585 views

Hi there,

We are working on a feedback loop to our corporate communication history for communications (push, email, sms etc.) sent out from AJO. Using an example customer, we have two levels of customer identities (CRM1 - Web login account, CRM2 - billing accounts). It will be always be a 1:M relationship (Web login will have multiple billing accounts). For example, customer has 1 web login, which has access to 4 billing accounts.

As part of the feedback loop, we need to send a communication record to all 4 billing accounts so that it's recorded under whichever Billing Account we look up to. Unfortunately AJO works at a profile level, so by default it would only send 1 record. We cannot make any process modification on the downstream end, so the 1 to 4 split would need to happen at AJO side. Is there a way to do that?

Thanks.

Journey Optimizer

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

@akwankl Here are my thoughts on this. I think you need to change the way how you ingest the data in AEP/RT-CDP. With the B2B SKU, designate the Web Login ID as the account ID, and treat the billing accountID values as individual IDs associated with that primary account. This configuration will aggregate all billing accountIDs under the corresponding Web Login ID, establishing a one-to-many (1:M) relationship between the account and individual IDs.

By implementing this method, communication records will be organized hierarchically, ensuring clear tracking of interactions at both the account and individual levels.

SatheeskannaK

Accepted solution

Community Advisor

@akwankl Here are my thoughts on this. I think you need to change the way how you ingest the data in AEP/RT-CDP. With the B2B SKU, designate the Web Login ID as the account ID, and treat the billing accountID values as individual IDs associated with that primary account. This configuration will aggregate all billing accountIDs under the corresponding Web Login ID, establishing a one-to-many (1:M) relationship between the account and individual IDs.

By implementing this method, communication records will be organized hierarchically, ensuring clear tracking of interactions at both the account and individual levels.

Thanks, Sathees

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded