Content offer lifecycle

From Genesys Documentation
Jump to: navigation, search

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 in determining the triggering behavior of action maps that use content offers.

State transitions for content offers

GPE content offer webaction diagram.png

Content offer lifecycle states

COOffered1.png





The following table describes 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 Visitor's activity qualifies an action map and the action map presents a content offer. See Events methods with web actions.
accepted Web Actions Accepted Visitor accepts the offer (for example, clicks a Book now! button). This is a terminal state. See Events methods with web actions.
rejected Web Actions Rejected Visitor rejects the offer (for example, clicks X or a No, but thank you button). 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 Visitor ignores the invitation (for example, navigates 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 terminal, or final, states. If a visitor goes to a webpage where an action map is set to trigger a content offer, the action map doesn't present the content offer when it's in a terminal state. This feature ensures that a visitor does not receive the same content offer after accepting the offer previously or after indicating that they are not interested.

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 in the Action Map Performance report correlate with the event types for web actions. For more information about metrics for content offers, see Monitor a content offer's performance.