Genesys Cloud - Developer Announcements!

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Deprecation – Genesys Predictive Engagement Tracking SDK v1

  • 1.  Deprecation – Genesys Predictive Engagement Tracking SDK v1

    Posted 6 hours ago

    Summary

    Following our GPE Tracking SDK v1 Deprecation Announcement posted here, we are announcing deprecation for all related legacy tracking capabilities and API resources from July 27, 2026. 

    To ensure the uninterrupted event tracking and real-time customer journeys, all existing customers are encouraged to migrate to digital user tracking, our latest solution available via Messenger. We recommend using our Messenger App which includes a JavaScript SDKto set up your own web and app events, and/or Web Event, App Event and Messenger Web Deployment APIs. 

    For more information about digital user tracking, see Get started with digital user tracking and Migrate web tracking settings from Predictive Engagement to Messenger.

    Effective Date

    Monday, July 27, 2026

    Details

    We are announcing deprecation of GPE tracking SDK v1 in order to focus all our efforts and resources on building and expanding our latest tracking solution within Messenger, which also offers integrated messaging and digital apps (including, Knowledge, Co-browse, and more coming soon) out of the box, eliminating the need for separate deployments for Digital User Tracking and Messenger capabilities.

    This also allows us to leverage modern technology stacks for APIs, JavaScript and Mobile SDKs, for improved integration and overall stability & security.

    Customer Impact

    The following capabilities are affected by this deprecation:

    • The legacy web tracking feature powered by the GPE Tracking SDK v1, available via the tracking snippet in Genesys Cloud, will no longer generate web events.
    • Legacy web tracking settings under Predictive Engagement settings in Genesys Cloud will no longer be available.
    • Web events generated by the GPE Tracking SDK v1 will be removed.
    • Legacy tracking setting fields (journeyEvents.excludedQueryParameters, journeyEvents.shouldKeepUrlFragmentboolean and journeyEvents.searchQueryParameters) will no longer be supported by Messenger Web Deployment APIs.
    • The Journey JavaScript SDK can no longer be used to customize the legacy web tracking feature.
    • Journey APIs associated to legacy web tracking will no longer be available.
    • Legacy journey tracking resources in CX as Code will no longer be available.

    Impacted Resources

    Journey APIs:

    GET /api/v2/journey/websites/{websiteId}/customers/{customerCookieId}/beacons

    POST /api/v2/journey/websites/{websiteId}/customers/{customerCookieId}/beacons

    GET /api/v2/journey/settings/clickstream

    PATCH /api/v2/journey/settings/clickstream

    GET /api/v2/journey/websites/{websiteId}/customers/{customerCookieId}/ping

    Web Deployments APIs:

    POST /api/v2/webdeployments/configurations

    Issue References

    [AI-1272]

    Contacts

    @Mai-Christine Hoang  

    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