Difference between revisions of "ATC/Current/SDK/Content offer lifecycle"
From Genesys Documentation
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2") |
DannaShirley (talk | contribs) (Published) |
||
| Line 6: | Line 6: | ||
|Dimension=WebActions | |Dimension=WebActions | ||
|ComingSoon=No | |ComingSoon=No | ||
| − | |Platform=GenesysEngage-cloud | + | |Platform=PureConnect, GenesysCloud, GenesysEngage-cloud |
| − | |||
|Section={{Section | |Section={{Section | ||
|sectionHeading=Content offer lifecycle states | |sectionHeading=Content offer lifecycle states | ||
|anchor=1COInvite | |anchor=1COInvite | ||
|alignment=Vertical | |alignment=Vertical | ||
| − | |||
| − | |||
|structuredtext=[[File:COOffered1.png|left|thumb|393x393px]] | |structuredtext=[[File:COOffered1.png|left|thumb|393x393px]] | ||
<br /> | <br /> | ||
| Line 34: | Line 31: | ||
{{!}}Web Actions Offered | {{!}}Web Actions Offered | ||
{{!}}The customer's activity has qualified an action map, and a proactive invitation is offered. | {{!}}The customer's activity has qualified an action map, and a proactive invitation is offered. | ||
| − | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic= | + | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}. |
{{!}}- | {{!}}- | ||
{{!}}accepted | {{!}}accepted | ||
{{!}}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}}. | {{!}}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}}. | ||
| − | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic= | + | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}. |
{{!}}- | {{!}}- | ||
{{!}}rejected | {{!}}rejected | ||
{{!}}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}}. | {{!}}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}}. | ||
| − | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic= | + | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}. |
{{!}}- | {{!}}- | ||
{{!}}errored | {{!}}errored | ||
| Line 50: | Line 47: | ||
{{!}}An error occurred in the widget that prevented the engagement from occurring. | {{!}}An error occurred in the widget that prevented the engagement from occurring. | ||
'''Note:''' This event does not have a corresponding metric in the Action Map Performance Report. | '''Note:''' This event does not have a corresponding metric in the Action Map Performance Report. | ||
| − | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic= | + | {{!}}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. | In addition, the errorMessage field is available. | ||
{{!}}- | {{!}}- | ||
| Line 57: | Line 54: | ||
{{!}}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}}. | {{!}}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}}. | ||
'''Note:''' This event does not have a corresponding metric in the Action Map Performance Report. | '''Note:''' This event does not have a corresponding metric in the Action Map Performance Report. | ||
| − | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic= | + | {{!}}See {{Link-SomewhereInThisVersion|manual=SDK|topic=Use_Events_methods_with_web_actions|display text=Events methods with web actions}}. |
<br /> | <br /> | ||
{{!}}} | {{!}}} | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 67: | Line 62: | ||
|anchor=Terminal | |anchor=Terminal | ||
|alignment=Vertical | |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 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. | ||
| Line 78: | Line 71: | ||
For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger}}. | For more information, see {{Link-SomewhereInThisVersion|manual=AdminGuide|topic=Trigger}}. | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
}}{{Section | }}{{Section | ||
| Line 85: | Line 76: | ||
|anchor=ReportMetricsEvents | |anchor=ReportMetricsEvents | ||
|alignment=Vertical | |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 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}}. | ||
| − | |||
| − | |||
|Status=No | |Status=No | ||
| + | }} | ||
}} | }} | ||
}} | }} | ||
Revision as of 15:47, October 20, 2020
This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.
Contents
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.
Content offer lifecycle states
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 Events methods.
| State | Event | Description | Data available |
|---|---|---|---|
| offered | Web Actions Offered | The customer's activity has qualified an action map, and a proactive invitation is offered. | See Events methods with web actions. |
| accepted | Web Actions Accepted | The customer accepts the invitation by clicking a button like Book now! This is a terminal state. | See 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 terminal state. | See Events methods with web actions. |
| errored | Web Actions Errored | An error occurred in the widget that prevented the engagement from occurring.
Note: This event does not have a corresponding metric in the Action Map Performance Report. |
See Events methods with web actions.
In addition, 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 terminal state.
Note: This event does not have a corresponding metric in the Action Map Performance Report. |
See Events methods with web actions.
|
Terminal states for content offers
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.
Terminal states for content offers are:
- Accepted
- Rejected
- Ignored
For more information, see Define an action map's triggers.
Report metrics and events
The metrics used in the Action Map Performance report correlate directly with the event types for web actions. For more information about metrics for content offers, see Monitor a content offer's performance.
}}
Comments or questions about this documentation? Contact us for support!