ATC/Current/SDK/Content offer lifecycle - Revision history

WikiSysop at 09:00, October 5, 2022

2022-10-05T09:00:42Z

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

2021-11-09T21:28:26Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Barbara.martin@genesys.com: Published

2021-08-10T10:36:01Z

Published

Barbara.martin@genesys.com: Published

2021-04-28T18:30:29Z

Published

Barbara.martin@genesys.com: Published

2021-01-15T18:05:07Z

Published

Barbara.martin@genesys.com: Published

2020-12-16T19:16:51Z

Published

Barbara.martin@genesys.com: Published

2020-12-15T13:21:14Z

Published

Barbara.martin@genesys.com: Published

2020-11-04T13:33:42Z

Published

DannaShirley: Published

2020-10-20T15:47:20Z

Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:32:04Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

@@ Line 8: / Line 8: @@
 |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=State transitions for content offers
 |alignment=Vertical

@@ Line 9: / Line 9: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext={{NoteFormat|1=This article only applies to customers using {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.|2=}}<br />
+|structuredtext={{NoteFormat|1=This article only applies to customers using {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_chats|display text=web chat}}. If you are a Genesys Cloud CX customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.|2=}}<br />
 |Status=No
 }}{{Section

@@ Line 3: / Line 3: @@
 |DisplayName=Content offers lifecycle
 |TocName=Content offers lifecycle
-|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. We use lifecycle states in reporting and when determining the triggering behavior of action maps that use content offers.{{BarbFeatureTemp|Feature=Web messaging}}This article only applies to customers using web chat. If you are a Genesys Cloud customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.
+|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. We use lifecycle states in reporting and when determining the triggering behavior of action maps that use content offers.
 |Dimension=WebActions
 |ComingSoon=No
 |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=State transitions for content offers
 |alignment=Vertical

@@ Line 3: / Line 3: @@
 |DisplayName=Content offers lifecycle
 |TocName=Content offers lifecycle
-|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. We use lifecycle states in reporting and when determining the triggering behavior of action maps that use content offers.
+|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. We use lifecycle states in reporting and when determining the triggering behavior of action maps that use content offers.{{BarbFeatureTemp|Feature=Web messaging}}This article only applies to customers using web chat. If you are a Genesys Cloud customer, we encourage you to use the new {{Link-AnywhereElse|product=ATC|version=Current|manual=AdminGuide|topic=About_web_messaging|display text=web messaging}} feature to replace web chat.
 |Dimension=WebActions
 |ComingSoon=No
 |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud
 |Section={{Section
 |sectionHeading=State transitions for content offers
 |alignment=Vertical

@@ Line 89: / Line 89: @@
 |structuredtext=The metrics in the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map Performance report}} correlate directly with the {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|anchor=EventsWebActions|display text=event types for web actions}}. For more information about metrics for content offers, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorContentOffers|anchor=COPerfReport|display text=Monitor a content offer's performance}}.
 |Status=No
 }}
 }}

@@ Line 3: / Line 3: @@
 |DisplayName=Content offers lifecycle
 |TocName=Content offers lifecycle
-|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. Lifecycle states are used in reporting and in determining the triggering behavior of action maps that use content offers.
+|Context=See the lifecycle of a content offer and the metrics that we capture at each state along the way. We use lifecycle states in reporting and when determining the triggering behavior of action maps that use content offers.
 |Dimension=WebActions
 |ComingSoon=No
@@ Line 31: / Line 31: @@
-The following table provide details about the lifecycle of a content offer, including the events that can occur and the data that is available for use with the {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods}}.
+The following table provides details about the lifecycle of a content offer, including the events that can occur and the data that is available for use with the {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods}}.
 {{{!}} class="wikitable"
 {{!}}+
@@ Line 41: / Line 41: @@
 {{!}}offered
 {{!}}Web Actions Offered
-{{!}}The customer's activity has qualified an action map, and a proactive invitation is offered.
+{{!}}Visitor's activity qualified an action map, and a proactive invitation is offered.
 {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}.
 {{!}}-
 {{!}}accepted
 {{!}}Web Actions Accepted
-{{!}}The customer accepts the invitation by clicking a button like '''Book now!''' This is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
+{{!}}Visitor accepts the invitation by clicking a button like '''Book now!''' This state is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
 {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}.
 {{!}}-
 {{!}}rejected
 {{!}}Web Actions Rejected
-{{!}}The customer rejects the invitation by either clicking  '''X''' or a button like, '''No, but thank you'''. This is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
+{{!}}Visitor rejects the invitation by either clicking  '''X''' or a button like, '''No, but thank you'''. This state is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
 {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}.
 {{!}}-
@@ Line 59: / Line 59: @@
 '''Note:''' This event does not have a corresponding metric in the Action Map Performance Report.
 {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}.
-In addition, the errorMessage field is available.
+Also, the errorMessage field is available.
 {{!}}-
 {{!}}ignored
 {{!}}Web Actions Ignored
-{{!}}The customer has ignored the invitation by navigating away from or around it. This is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
+{{!}}Visitor ignored the invitation by navigating away from or around it. This state is a {{Link-SomewhereInThisVersion|manual=SDK|topic=Content_offer_lifecycle|anchor=Terminal|display text=terminal state}}.
 '''Note:''' This event does not have a corresponding metric in the Action Map Performance Report.
 {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}.
@@ Line 73: / Line 73: @@
 |anchor=Terminal
 |alignment=Vertical
-|structuredtext=In the content offer lifecycle, certain states are considered ''terminal'', or final, states. If a customer navigates to a web page where an action map is set to trigger a content offer, the action map will not offer the content offer if it is already in a terminal state. This ensures that a customer does not receive the same content offer after the customer has already accepted the offer or has indicated that they are not interested in that particular content offer.
+|structuredtext=In the content offer lifecycle, certain states are considered ''terminal'', or final states. If a visitor navigates to a webpage where an action map is set to trigger a content offer, the action map doesn't offer the content offer if it is in a terminal state. This feature ensures that a visitor does not receive the same content offer after accepting the offer or indicating that they are not interested in that particular content offer.
 Terminal states for content offers are:
@@ Line 87: / Line 87: @@
 |anchor=ReportMetricsEvents
 |alignment=Vertical
-|structuredtext=The metrics used in the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map Performance report}} correlate directly with the {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|anchor=EventsWebActions|display text=event types for web actions}}. For more information about metrics for content offers, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorContentOffers|anchor=COPerfReport|display text=Monitor a content offer's performance}}.
+|structuredtext=The metrics in the {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Action_Map_Performance|display text=Action Map Performance report}} correlate directly with the {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|anchor=EventsWebActions|display text=event types for web actions}}. For more information about metrics for content offers, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=MonitorContentOffers|anchor=COPerfReport|display text=Monitor a content offer's performance}}.
 |Status=No
 }}
 }}
 }}

@@ Line 6: / Line 6: @@
 |Dimension=WebActions
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud
+|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
 |Prereq=
 |Section={{Section

ATC/Current/SDK/Content offer lifecycle - Revision history

WikiSysop at 09:00, October 5, 2022

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Barbara.martin@genesys.com: Published

Barbara.martin@genesys.com: Published

Barbara.martin@genesys.com: Published

Barbara.martin@genesys.com: Published

Barbara.martin@genesys.com: Published

Barbara.martin@genesys.com: Published

DannaShirley: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"