On-device decisioning provides the ability to cache your Adobe Target A/B Test and Experience Targeting (XT) activities on your server and perform in-memory decisioning at near-zero latency, without blocking network requests to the Adobe Target Edge Network.
More than ever, marketers, product owners and developers are being tasked with optimizing the overall customer experience on sites, in apps, and everywhere else they connect with their customers. Multiple tools with data silos and complicated implementations are inadequate.
In this recorded webinar, Adobe Target product experts discuss how moving critical experience optimization decisions on-device to execute locally with near-zero latency can open doors to exciting new use cases while improving site performance for your customers.
Adobe recommends the following best practices when using on-device decisioning:
When using “on-device” as the decisioning method, the artifact is downloaded when the visitor loads the webpage for the first time. Any activity qualification that needs to happen on the first page load (no cache) happens only after the artifact is fully downloaded. There are certain best practices you can follow to ensure that activity qualifications happen fast for a new anonymous visitor.
When using “hybrid” as the decisioning method, the artifact is downloaded in parallel. Until the artifact is downloaded, any Target API calls go over the wire even if the “locations” are on-device capable. This behavior is the default for all
getOffers() calls and provides the best performance in most situations. If you change the default behavior of
getOffers() by setting the
on-device, follow these best practices to avoid errors and ensure the best performance.
on-devicewhen the page loads for the first time, you must do so inside the “ARTIFACT_DOWNLOAD_SUCCEEDED” at.js event handler to avoid errors. If your artifact is very large, any “locations” using this approach are rendered only after the artifact is fully downloaded, which can delay experience rendering. Adobe recommends that you rarely use this approach. Follow the best practices to reduce artifact size under the “On Device” best practices section above when using this approach.
Adobe Target on-device decisioning enables near-zero latency content delivery.
This 7-minute video:
For more videos and tutorials, see the Adobe Target Tutorials guide.