On-Device Decisioning in WebSDK? | Community
Skip to main content
JeanBaro_
JeanBaro_
Level 4
November 11, 2024
Solved

On-Device Decisioning in WebSDK?

  • November 11, 2024
  • 2 replies
  • 781 views

Hello team,

Based on Adobe's documentation, "on-device decisioning" is currently available only in AT.js, NOT in WebSDK.

For new projects, we’re recommending WebSDK since it unifies multiple AEP capabilities we use, such as Target, Analytics, and more, making it easier to maintain a single solution going forward.

Today, we rely on AT.js's on-device decisioning mainly for performance benefits. We're curious to know if this limitation in WebSDK is a critical factor or if there are effective alternatives within WebSDK to maintain similar performance.

I also checked Adobe's WebSDK roadmap and didn’t see on-device decisioning listed. Do you know if it’s planned or if Adobe has other recommended approaches?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by JeanBaro_

This seems to be an alternative (in case any one is interested):

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/api-reference/offer-delivery-api/edge-decisioning-api

Edge Decisioning

Pros:

  • Centralized updates—no need to redeploy on devices.
  • Reduces client device load.
  • Consistent experience across devices.
  • Recommended approach, as WebSDK is the long term solution (although AT.js is fully supported).

Cons:

  • Slightly higher latency than on-device.
  • Requires constant network connection.
  • Adds overhead with frequent calls.

On-Device Decisioning

Pros:

  • Instant, low-latency responses.
  • Works offline or with low connectivity.
  • More adaptable to real-time, device-specific context.

Cons:

  • Requires device resources, which can impact performance.
  • Needs redeployment for rule updates.

 

2 replies

JeanBaro_
JeanBaro_AuthorAccepted solution
Level 4
November 11, 2024

This seems to be an alternative (in case any one is interested):

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/api-reference/offer-delivery-api/edge-decisioning-api

Edge Decisioning

Pros:

  • Centralized updates—no need to redeploy on devices.
  • Reduces client device load.
  • Consistent experience across devices.
  • Recommended approach, as WebSDK is the long term solution (although AT.js is fully supported).

Cons:

  • Slightly higher latency than on-device.
  • Requires constant network connection.
  • Adds overhead with frequent calls.

On-Device Decisioning

Pros:

  • Instant, low-latency responses.
  • Works offline or with low connectivity.
  • More adaptable to real-time, device-specific context.

Cons:

  • Requires device resources, which can impact performance.
  • Needs redeployment for rule updates.

 

    D
    Adobe Employee
    danvivasAdobe Employee
    Adobe Employee
    November 19, 2024

    Thanks for question @jeanbaro_ . You're correct in that on-device decisioning is currently only supported with at.js. We are however working to change that in the first half of 2025. The new feature we are building will work very similar to on-device decisioning but utilize edge worker for the most optimal performance. Happy to chat in more detail. 

    Terms & ConditionsAccessibility statement

    Loading footer...