Columns in the dcm_treatments_contacts_vw View

The dcm_treatments_contacts_vw view contains detailed information about subject contact records. The following table describes each column in the view and lists the associated schema property in the Decision Management REST API.

Column	Description	Schema Property
contact_id	A unique identifier for the contact record. A contact record with a new contact_id is created when a decision determines that a subject is eligible for a specific treatment and writes the contact record to the database.	id in the contact record. For the details, see the Subject Contacts API.
subject_id	The ID of the subject if a subject ID variable is defined in the properties for the decision flow.	subjectId in the contact record. For the details, see the Subject Contacts API.
subject_level	The subject level if a subject level variable is defined in the decision flow. For more information, see Predefined Lookup Tables.	subjectLevel in the contact record. For the details, see the Subject Contacts API.
created_by_nm	The ID of the user who ran the decision that created contact record.	createdBy in the contact record. For the details, see the Subject Contacts API.
modified_by_nm	The ID of the user who last modified the contact record. For example, subject contact records can be modified to include a recording of the treatment presentation or to include information about the subject’s response to the treatment.	modifiedBy in the contact record. For the details, see the Subject Contacts API.
creation_dttm	A timestamp that indicates when the contact record was created.	creationTimeStamp in the contact record. For the details, see the Subject Contacts API.
modified_dttm	A timestamp that indicates when the contact record was last modified.	modifiedTimeStamp in the contact record. For the details, see the Subject Contacts API.
contact_channel_txt	The channel through which the contact occurred. For more information, see About Channels.	channel in the contact record. For the details, see the Subject Contacts API.
response_tracking_cd	The response tracking code that was generated by the record contacts node.	responseTrackingCode in the contact record. For the details, see the Subject Contacts API.
conclusion_response_txt	The subject’s response to the results of the decision. When the decision includes treatments, this value might represent an overall response to all of the treatments in the subject contact record.	conclusionResponseValue in the contact record. For the details, see the Subject Contacts API.
conclusion_response_type_txt	A summary value, category name, or other description for the response that is specified in the conclusion_response_txt column. For example, this value might be `Evaluating`, `No response`, or `Closed-Lost`.	conclusionResponseType in the contact record. For the details, see the Subject Contacts API.
object_type_cd	A string that identifies the type of resource that created the contact record. Currently, the only value in this column is `decision`.	objectType in the contact record. For the details, see the Subject Contacts API.
object_revision_id	The ID for the version of the object that created the contact record.	objectRevisionId in the contact record. For the details, see the Subject Contacts API.
object_url_txt	The URI for the decision that created the contact record (for example, `/decisions/flows/545783f1-4fb3-45aa-be7d-d9e5a13ed943`).	objectUri in the contact record. For the details, see the Subject Contacts API.
exclude_from_contact_rule_txt	Specifies whether the contact record is included in aggregate reports for the channel. Column values are `true` or `false`.	excludeFromContactRule in the contact the record. For details, see the Subject Contacts API.
rule_fired_txt	Rule-fired information for the decision if that information was recorded by the record contacts node.	ruleFired in the contact record. For the details, see Subject Contacts API.
traversed_rule_path_list_txt	Path-tracking information for the decision if that information was recorded by the record contacts node.	pathTraversed in the contact record. For the details, see the Subject Contacts API.
treatment_receiver_id	A string that identifies the entity that received the treatment. If this entity is the subject, then the treatment_receiver_id column contains the same value as the subject_id column. Note: This column is present in the table, but it is not currently used.	receiverId in the contact record. For the details, see the Subject Contacts API.
treatment_receiver_role_txt	A string that identifies the role of the entity that received the treatment. For example, the receiver might be the subject or an agent. Note: This column is present in the table, but it is not currently used.	receiverRole in the contact record. For the details, see the Subject Contacts API.
treatment_revision_id	The ID of the treatment definition version.	treatmentRevisionId in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
treatment_id	The ID of the treatment definition.	treatmentId in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
presented_txt	Specifies whether the treatment was presented to the subject. The values in this column are a character string representation of a Boolean value: `true` or `false`.	presented in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
presentation_dttm	A timestamp that indicates when the treatment was presented to the subject. The timestamp format is Coordinated Universal Time (UTC): `yyyy-mm-ddThh:mm:ss.sssZ`	presentedTimeStamp in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
response_dttm	A UTC timestamp that indicates when the subject responded to the treatment.	respondedTimeStamp in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
response_txt	The subject’s response to the treatment. For example, this value might be a value or code such as `Purchased`, `Rejected`, `Requested quote`, `Email opened`, or `rt1`.	responseValue in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
response_type_txt	A summary value, category name, or other description for the response that is specified by the value of the response_txt column. For example, this value might be `Positive`, `Negative`, or `Neutral`.	responseType in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
response_channel_txt	The channel through which the user responded to the treatment. The response channel might be different from the contact channel. For more information, see About Channels.	responseChannel in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
treatment_group_id	The ID of the treatment group that contains the treatment.	treatmentGroupId in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
consider_id	The primary key of the dcm_treatment_consideration table.	An internal ID for each treatment that was sent to a subject. This ID is unique within the view. This column is in not in the schema.
treatment_group_revision_id	The ID of the treatment definition group version.	treatmentGroupRevisionId in the treatmentsForConsideration table. For the details, see the Subject Contacts API.
object_node_id	The ID of the node in the decision whose URL is specified in the object_url_txt column. For example, if the same treatment group is included in a decision multiple times, this ID enables you to determine which node generated an offer.	objectNodeId in the treatmentsForConsideration table. For the details, see the Subject Contacts API.

Last updated: September 16, 2026