Problem
The ACA experience event content schema (experienceevent-content.schema.json) has an xdm:channel field at the root level of xdm:experienceContent that distinguishes between Web, Mobile, and PaidMedia channels. This field is used as a reporting dimension for cross-channel breakdowns in CJA.
The paid media summary metrics schema currently lacks this channel field. When joining web event and mobile event datasets with paid media summary data for an asset ID, there is no field to create the channel dimension for reporting breakdowns.
Proposed Solution
Add xdm:channel to the paid media core identifiers field group (core-paid-media-identifiers.schema.json) under xdm:paidMedia. This is a plain string field matching the experience event schema's channel field.
For paid media rows, the value will always be PaidMedia, but the field needs to exist so that CJA can create a dimension from it for cross-channel reporting.
Reference
Problem
The ACA experience event content schema (
experienceevent-content.schema.json) has anxdm:channelfield at the root level ofxdm:experienceContentthat distinguishes betweenWeb,Mobile, andPaidMediachannels. This field is used as a reporting dimension for cross-channel breakdowns in CJA.The paid media summary metrics schema currently lacks this channel field. When joining web event and mobile event datasets with paid media summary data for an asset ID, there is no field to create the channel dimension for reporting breakdowns.
Proposed Solution
Add
xdm:channelto the paid media core identifiers field group (core-paid-media-identifiers.schema.json) underxdm:paidMedia. This is a plain string field matching the experience event schema's channel field.For paid media rows, the value will always be
PaidMedia, but the field needs to exist so that CJA can create a dimension from it for cross-channel reporting.Reference