Genesys Cloud - Developer Announcements!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Deprecation – GPE Journey Outcomes & Outcome Scoring

  • 1.  Deprecation – GPE Journey Outcomes & Outcome Scoring

    Posted 3 hours ago

    Summary

    Following our GPE Journey Outcomes & Outcome Scoring Deprecation Announcement, we are announcing deprecation for all related GPE journey outcomes and outcome scoring capabilities and API from May 25, 2026. 

    A new platform-wide Customer Outcomes feature will be introduced. 

    All existing customers are encouraged to review their current outcomes and action maps to identify where they are used for orchestration or reporting to plan their migration to the new Customer Outcomes feature once available. We recommend avoiding creating new legacy outcome related configurations after this announcement. 

    Watch for direct communications outlining next steps and key dates for your organization.

    Effective Date

    Monday, May 25, 2026

    Details

    We are announcing deprecation of GPE journey outcomes and outcome scoring feature in order to introduce new enhanced Customer Outcomes, which offers a simplified, omni-channel, event-driven model that focuses on single-event results, clear measurement, and future scalability across channels.

    This allows us to provide a strong foundation for the future use cases for Outcomes in Genesys Cloud and via APIs, for more accurate analytics and next-generation orchestration.

    Customer Impact

    The following capabilities in Genesys Cloud are affected:

    • Existing GPE journey outcome configurations will be removed.
    • The Outcome list view will no longer be available.
    • New GPE journey outcome configurations can no longer be created.
    • GPE journey outcomes will no longer be achieved by web and app visitors.
    • The journey analytics workspace reports will be updated to remove outcomes
    • Outcome triggering will no longer be available when editing or creating action maps.
    • The audience estimator will no longer support outcomes.
    • Existing action maps configured with outcome triggering no longer qualify and the configuration of outcome probability for outcome triggering in all action maps will no longer be available. Impacted action maps will be subject to automatic deletion at a later point after the end-of-life date. Customers are encouraged to switch impacted action maps to a different trigger type.
    • Outcome resources in CX as code will no longer be available.
    • Outcomes, scores and attribution will no longer be available publicly as web sockets for notification events.
    • The “Get Journey Outcome” Architect action will no longer be supported.

    Leading to the following impact in APIs:

    • Deprecation of Journey Outcome APIs
    • Deprecation of Journey Outcome Prediction APIs
    • Deprecation of Journey Outcome Scores API
    • Audience Estimator APIs will no longer support GPE journey outcomes
    • Deprecation of Journey Analytics Attribution APIs
    • Deprecation of triggerWithOutcomeQuantileConditions field in Action Maps APIs
    • Analytics APIs will no longer support GPE journey outcomes

    Impacted Resources

    Journey APIs:

    GET /api/v2/journey/outcomes

    POST /api/v2/journey/outcomes

    DELETE /api/v2/journey/outcomes/{outcomeId}

    GET /api/v2/journey/outcomes/{outcomeId}

    PATCH /api/v2/journey/outcomes/{outcomeId}

    Journey Outcome Prediction APIs:

    GET /api/v2/journey/outcomes/predictors

    POST /api/v2/journey/outcomes/predictors

    DELETE /api/v2/journey/outcomes/predictors/{predictorId}

    GET /api/v2/journey/outcomes/predictors/{predictorId}

    Journey Outcome Scores API:

    GET /api/v2/journey/sessions/{sessionId}/outcomescores

    Audience Estimator APIs:

    POST /api/v2/journey/actionmaps/estimates/jobs

    GET /api/v2/journey/actionmaps/estimates/jobs/{jobId}

    GET /api/v2/journey/actionmaps/estimates/jobs/{jobId}/results

    Journey Analytics Attribution APIs:

    POST /api/v2/journey/outcomes/attributions/jobs

    GET /api/v2/journey/outcomes/attributions/jobs/{jobId}

    GET /api/v2/journey/outcomes/attributions/jobs/{jobId}/results

    Action Map APIs:

    POST /api/v2/journey/actionmaps

    GET /api/v2/journey/actionmaps

    PATCH /api/v2/journey/actionmaps/{actionMapId}

    GET /api/v2/journey/actionmaps/{actionMapId}

    Analytics APIs:

    POST /api/v2/analytics/journeys/aggregates/query

    Issue References

    [AI-1331]

    Contacts

    @Cillian Day  

    Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.



Related Content