Content offers lifecycle

From Genesys Documentation
Jump to: navigation, search
This topic is part of the manual Journey JavaScript SDK for version Current of Altocloud.

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

COOffered1.png





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 Event types for web actions.
accepted Web Actions Accepted The customer accepts the invitation by clicking a button like Book now! This is a terminal state. See Event types for 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 Event types for 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 Event types for 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 Event types for 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 Trigger an action map.

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.