Content offers lifecycle

From Genesys Documentation
Revision as of 10:12, June 10, 2020 by DannaShirley (talk | contribs) (Published)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
This topic is part of the manual Journey JavaScript SDK for version Current of Genesys Predictive Engagement.

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! 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. 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.

Note: This event does not have a corresponding metric in the Action Map Performance Report.

See Event types for web actions.


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!