Which type of attributes or fields can be exported to batch destinations in Real-Time CDP?

Question

Options

• AExperience event class-based schema attributes
• BCustom class-based schema attributes
• CIndividual profile class-based schema attributes
• DPseudonymous profile class-based schema attributes

• A
  2% (1)
• B
  9% (4)
• C
  84% (36)
• D
  5% (2)

Explanation

In Real-Time CDP, batch destinations export profile snapshots - structured records of known individuals built from the XDM Individual Profile class. Only attributes from schemas based on this class are eligible for export because they are the ones included in the Real-Time Customer Profile union schema, which is what batch activation reads from.

Why the distractors are wrong:

• A (Experience Event): Experience events are time-series behavioral records (clicks, purchases), not profile attributes. They feed into computed attributes or segmentation but are not directly exported as fields to batch destinations.
• B (Custom class): Custom class-based schemas are not enabled for Real-Time Customer Profile by default and therefore are not part of the union schema available for batch export.
• D (Pseudonymous Profile): Pseudonymous profiles represent unauthenticated/anonymous users. Batch destinations target known, addressable individuals - not anonymous profiles.

Memory tip: Think "batch = known people leaving in bulk." Batch destinations ship profile data about identified individuals, so only the Individual Profile class (the class for known people) qualifies. If the schema class isn't "Individual Profile," it won't be in the batch export.

No community discussion yet for this question.