Hi @josh1975 My interpretation on your question is that CJA doesn't inherit the schema relationships as CJA relies on dataset joins within the CJA connection or derived fields for enriching the data. If your goal is to add the additional attribute on CJA report then your approach is a correct method...

@MichaelJo13  - Interaction type will accept only the predefined Enum value, if no predefined Enum while ingesting the data then we may end up with this error. Please refer the below document. Even on the schema object only the given Enum value have been updated. So, it MUST be any of only those giv...

@GigiCotruta I totally agree, you have already mentioned the key benefit of having the relationship between these schemas. Sometime we have to stick with limitation to avoid the breakage of profiles. If you start collecting everything all you need at a single event then you may face the guardrail li...

Hi @MattewGi  - I hope you are leveraging the prospect functionality in AEP to ingest the partner record. My interpretation is that you will send the campaign email to prospect from the created prospect audience and they may come back as a customer profile (enriching) by converting as per the campai...

Hi @GigiCotruta  - The main purpose of having a relationship between these schemas is to leverage the attributes of look up schema in segmentation builder. This will create a separate folder properties on "productlisitems" where you can use the SKU product schema attribute to fetch the customer prof...

Hi @MattewGi  - Good question, prospect are typically a stand alone profile with minimal identity resolution and it is often treated as anonymous profiles as well like ECID, partner data. We can see this prospect frame from two aspects, 1. Partner data from third party service or partnership data th...

Hi @GabrielaNa1  - Hope you are looking to store a multiple values related to the touchpoints. I don't see any odd on the screenshot that you have shared, looks fine. So once you ingest the data, it would look like below on the JOSN view on profile section. "da_for_touchpoints": [{"tp_code": "546777...

Hi @ItyBala24  - There is a limitation of activating the array based attributes. You can now activate the array attributes only to file based destination (example - Amazon S3). We need to use the "array_to_string" function along with other array related function to manipulate the array attributes in...

@BitunSenAEP  - To be honest, we haven't used this segment definition class to bring the external audience. Again as mentioned, even though you use this segment definition class to bring all your audience along with other respective attributes still you might need to create a audience based on this ...

Hi @BitunSenAEP  - Importing the external audience from "Import audience" feature and other sources like SFTP, Cloud Storage is totally vary. Import audience will directly create a audience list from the uploaded CSV file and available to utilize for downstream and further enrichment. However, impor...