Respond to deprecations
Stay organized with collections
Save and categorize content based on your preferences.
Fields defined in the Real-time Curation specification can be deprecated, which
is announced in the release
notes, and
indicated in the reference documentation with the following statement in the
first line of the field's description:
Deprecated. This will be removed in {MONTH}, {YEAR}.
After the deprecation period passes, these fields sunset, meaning that they are
removed from the specification. Sunset fields aren't sent in the
SegmentRequest, and are ignored if you include them in your
SegmentResponse.
During the deprecation period, update your integration to remove any logic
dependent on deprecated fields to avoid interruptions to your Real-time Curation
integration.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-01-27 UTC."],[],[]]
