Upcoming Changes to Dynamic Chat activities

[#1]

We are announcing some changes to Adobe Marketo Engage activities that are related to Dynamic Chat. To support new Dynamic Chat offerings announced at Adobe Summit, and to better match standardized naming conventions, we will be updating the names of some existing Marketo Engage activities and attributes and adding additional activity attributes to existing activities. These changes will go into effect in our July release (July 18, 2023 for NLD and LON datacenters, July 21 for AB, SJ, and SN datacenters).

Will these changes impact my business and how?

These changes will primarily impact Smart Lists (standalone and in Smart Campaigns), Person Activity Log, and the REST and SOAP APIs:

Smart Lists

The names of affected activities and attributes will change in their respective cards. Existing Smart Lists (both standalone and in Smart Campaigns) will continue to evaluate without needing any change in configuration. Filters/triggers referencing the new names of activities or new names of attributes will continue to qualify older activities and attributes with the old naming convention.

Person Activity Logs

Newly created activities will use the new naming conventions. Older activities will continue to show the old naming conventions and will not be retroactively renamed. These older activities will still qualify in Smart Lists by referencing them with the new naming conventions.

REST and SOAP APIs

Activity ID of affected activities will stay the same. New names of activities and attributes will be returned over the REST API from the Get Activity Types endpoint (/activities/types.json) or SOAP API from the getLeadActivity and getLeadChanges endpoints.

Integrations should be tested to ensure they can support the upcoming changes. If your integration has hardcoded references to activity or attribute names, they must be updated to support both the old naming conventions and the new naming conventions else it will run the risk of interruption.

Updates to the activities are detailed below:

Engaged With Dialogue

Activity Name

Existing Name	New Name
Engaged with Dialogue	Engaged with A Dialogue

Attributes

Existing Attribute Name	New Attribute Name
Dialogue Name	Dialogue Name
Page URL	Page URL
Status	Conversation Status
Chat Transcript	Conversation Transcript
	Conversation Summary*
	Language*
	Workspace*

*Denotes new attributes

Reached Dialogue Goal

Activity Name

Existing Name	New Name
Reached Dialogue Goal	Reached Dialogue Goal

Attributes

Existing Attribute Name	New Attribute Name
Dialogue Name	Dialogue Name
Goal Name	Goal Name
Page URL	Page URL
	Language*
	Workspace*

*Denotes new attributes

Dialogue Appointment Scheduled

Activity Name

Existing Name	New Name
Dialogue Appointment Scheduled	Scheduled Meeting in Dialogue

Attribute Names

Existing Attribute Name	New Attribute Name
Dialogue Name	Dialogue Name
Agent	Agent Email
Page URL	Page URL
Status	Meeting Status
Scheduled For	Scheduled For
	Agent Name*
	Routing Queue ID*
	Routing Queue Type*
	Routing Queue Name*

*Denotes new attributes

Interacted with Document

Activity Name

Existing Name	New Name
Interacted with Document	Interacted with Document in Dialogue

Attributes

Existing Attribute Name	New Attribute Name
Dialogue Name	Dialogue Name
Document Name	Document Name
Document URL	Document URL
Document Opened	Document Opened
Document Downloaded	Document Downloaded
Search Terms	Search Terms
Page URL	Page URL
	Language*
	Workspace*

*Denotes new attributes