Data 360: Differences in Output Formats Between Direct and Related Attributes in Enablement

In Data 360 enablement, configured items are reflected in the output by setting [Add Attributes] during the enablement process. The data structure in the output file is determined by whether the attributes are added as "Direct" or "Related" attributes:

Output Format

• Direct Attributes: Output as an independent column or field for each item.

• Related Attributes: Multiple attribute values are aggregated into a single column or field per DMO (e.g., Account DMO) and stored as structured data, such as JSON format.

Output Example
The following is an example of the output when selecting "Individual Id", "FirstName", and "EmailAddress" (Direct Attributes) and "Account Id" and "Account Name" from the Account DMO (Related Attributes). Amazon S3 and Marketing Cloud are used as examples.

• Amazon S3 (CSV Format): Direct attributes occupy separate columns, while related attributes are consolidated into a single column in JSON format.
Individual Id,FirstName,Account,EmailAddress,Version,UPDATE__ACTION__
003xxxxxxxxxxxxxxx,John,"[{"Account Id":"001xxxxxxxxxxxxxxx","Account Name":"Test Inc."}]",user@example.com,1,A

• Amazon S3 (JSON Format): The same data as the CSV is output in a nested structure as follows: 
{"Individual Id":"003xxxxxxxxxxxxxxx","FirstName":"John",
"Account":[{"AccountId":"001xxxxxxxxxxxxxxx","AccountName":"TestInc."}],"EmailAddress":"user@example.com","Version":1,"UPDATE__ACTION__":"A"}

• Marketing Cloud (Data Extension): Attributes are reflected as field values in the Data Extension as follows:

  SubscriberKey	Individual Id	FirstName	EmailAddress	Account
  003xxxxxxxxxxxxxxx	003xxxxxxxxxxxxxxx	John	user@example.com	[{"Account Id":"001xxxxxxxxxxxxxxx","Account Name":"Test Inc."}]