- Journey Optimizer documentation
- What’s new?
- Get started
- Journeys
- Campaigns
- Conflict management & prioritization
- Test & approve
- Communication channels
- Get started with communication channels
- Email channel
- In-app channel
- Push notification channel
- SMS / MMS channel
- Direct mail
- Web channel
- Code-based experience
- Content cards
- Landing pages
- Content management
- AI Assistant for content generation
- Work with Multilingual content
- Work with Content experiment
- Personalization
- Content templates
- Reusable content fragments
- Dynamic content
- Audiences, profiles & identity
- Integrations
- Track & monitor
- Live report
- All time report
- Journey reports
- Deliverability
- Alerts
- Exclusion reasons
- Decision capabilities
- Get started with decision capabilities
- Decisioning
- Get started with Decisioning
- Decisioning guardrails & limitations
- API reference
- Manage decision items
- Configure item selection
- Create selection strategies
- Create decision policies
- Report on Decisioning
- Decisioning use case
- Decision management
- Get started with Decision management
- Create components
- Create rankings
- Create & manage offers
- Create & manage decisions
- Use batch decisioning
- Collect event data
- Leverage context data
- Create Decision Management reports
- Export your offer catalog
- API Reference
- Getting started
- Create & manage offers using APIs
- Deliver offers using APIs
- Data management
- Channel configuration
- Journey configuration
- Connect your systems and environments
- Access control
- Privacy
Placements dataset
Each time an offer is modified, the autogenerated dataset for placements is updated.
The most recent successful batch in the dataset is displayed on the right. The hierarchical view of the schema for the dataset displays on the left pane.
Learn how to access the exported datasets for each object of your Offer Library in this section.
Here is the list of all the fields that can be used in the Decision Object Repository - Placements dataset.
Identifier
Field: _id
Title: Identifier
Description: A unique identifier for the record.
Type: string
_experience
Field: _experience
Type: object
_experience > decisioning
Field: decisioning
Type: object
_experience > decisioning > Placement's Channel Identifier
Field: channelID
Title: Placement’s Channel Identifier
Description: The channel in which proposition was made. The value is a valid Channel URI. See https://ns.adobe.com/xdm/channels/channel.
Type: string
_experience > decisioning > Content Component Type
Field: componentType
Title: Content Component Type
Description: An enumerated set of URIs where each value maps to a type given to the content component. Some consumers of the content representations are expecting the @type value to be a reference to schema that describes additional properties of the content component.
Type: string
_experience > decisioning > contentTypes
Field: contentTypes
Type: array
_experience > decisioning > contentTypes > MIME Media Type
Title: MIME Media Type
Description: A constraint for the media type of the components that is expected in that placement. There could be more than one media type possible for one component such as different image format.
Type: string
_experience > decisioning > Placement Description
Field: description
Title: Placement Description
Description: It is used to convey human readable intentions on how dynamic content is used in the overall message delivery. That a certain space is a “Banner” in a web page is often conveyed via the description and not by a formal method.
Type: string
_experience > decisioning > Placement Name
Field: name
Title: Placement Name
Description: An assigned name for the placement to refer to it in human interactions.
Type: string
_repo
Field: _repo
Type: object
_repo > Placement ETag
Field: etag
Title: Placement ETag
Description: The revision that the decision option object was at when the snapshot was taken.
Type: string
