My company is kicking off a big "modernization" project that involves updating our legacy web apps to a single-page-app architecture, and updating the way we use Target, Analytics, and the rest of the Experience Cloud.
I would like to being experimenting with our Target setup. Can I safely enable on-device decisioning (under Administration > Implementation) for use with a locally-running development SPA, without impacting our production site?
Will you be updating to a newer version of Adobe Target as well? Or just turning on the feature? As far as I know, you can put Target in a hybrid mode where it will require that the new json file (all your activities) be present prior to relying on said json file. In the loading time, it will still make normal api calls. I have it turned on and haven't seen a negative impact to site performance but that would probably depend on your place of Adobe Target, hopefully in the head of the app, etc. Here is some info:
Also, I have found on-device decisioning to be rather limited (sorry Adobe) due to that it only works for simple audience rules (non visitor profile) and it does not support automated personalization or auto-target/auto-allocate activities. It seems more akin to a feature toggle / software toggle capability.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
