Product Communities

Author: Alex Bishop This short article will provide a brief introduction to Adobe’s new On Device Decisioning capabilities. There is some very useful documentation available here that explains when to use On-device vs existing Edge decisioning, so my main focus will be providing some answers to questions that have come up quite regularly since the announcement, as well as a quick run through of the implementation basics. . . . #1 What you should know AvailabilityThe good news for the server-side fanatics amongst us is that On Device Decisioning is available in the latest Java & Node.js SDKs. The bad news for everyone else is that it’s not currently available in the Web or Mobile SDKs, however, it is on the roadmap for both. Server-side SDK basicsThere is a JSON artifact that contains all offers/activities data, which will be cached on your server; the Target SDK is then able to interpret the rules contained within that artifact and make decisions around which exp

Author: Alex Bishop aka @ab2487 The last article reviewed the (recently deprecated) VEC extension, with a view to getting your optimisation and personalisation activities up and running very quickly with. As with any optimisation programme, starting with simple tests that attack low hanging fruit is a great way to quickly prove the value of your work. Due to the minimal implementation effort involved, the visual editor was a good option to deliver those results fast but there were some fairly clear technical limitations. Similarly, as you work through the ideas in your test backlog, you will inevitably start focusing on hypotheses that call for more complex changes, which adjust the layout of components or even involve a complete re-design of a particular app view. This is where Target’s form composer comes into play, and this article will guide you through some ideas to help you get started. At risk of stating the obvious, the form composer isn’t only for more complex test

Author: David Son We are happy to announce the release of our first major version of the Adobe Target Node.js SDK. With this release, we are excited to help you focus on business logic rather than waste time understanding the technicalities of integrating with our APIs. Our Node.js SDK is not merely an API wrapper, but rather a sophisticated software development kit (SDK) that removes the complexities of managing cookies, sessions, and integrating with Experience Cloud products such as Analytics, Experience Cloud Visitor ID service, and Audience Manager. By removing the need for you to understand our ecosystem, we imagine that you will realize increased development velocity as well as improved KPIs that matter most to your business. New features in the Node.js SDK v1.0 Now with this first-ever major version comes amazing features that we know you will be excited about. An integration with Adobe Target’s newest delivery API — Our newest delivery API has better nati

Chef's Collection - Recipes for Personalization Success Webinar Presented by:  Drew Burns aka @drewb6915421, Group Product Marketing Manager for Adobe Target  Kaitlin White aka @kaitlinwhite, Adobe Target Product Marketing Manager  Date: August 30th, 2022 Time: 10:00am PT | 12:00pm CT | 1:00pm ET Join the Adobe Target team as they serve up some fresh ideas on how you can get the most value out of Adobe Target. Based on our newest eBook, “Chef’s Collection: Ideas for Personalization”. We’ll be digging into the stories of our customer “chefs” and what they’ve cooked up in their own personalization kitchens. We're looking forward to exploring ideas on: How to use personalization to build loyalty Optimizing for a competitive advantage Creating hyper-personalized experiences Whether you’re a new cook or a seasoned pro, we’ll be sure to dish out ideas for all skill levels and industries. WATCH THE RECORDING TODAY!   Drew Burns, Group Product Mark

Finding your work in Workfront shouldn’t be a challenge. However, for many, clutter is accumulated through unwanted notifications, outdated pins or favorites and laundry lists of views, filters and groupings that are no longer relevant.  This week’s blog will help you navigate through what can often feel like noise when you’re in a rush by providing tips to simplify how you find and organize your most important data in Workfront.  REDUCE NOTIFICATION OVERWHELM  Workfront has over 90 system-level email notifications available through the Setup menu. While only system administrators can activate/deactivate notifications at the system level, all users can personalize their notification settings in their profile by selecting which notifications they would like to receive instantly, daily or not at all. For a list of common missed or unwanted notifications, read the blog post, Get a Handle on Your Email Notifications.  NOTE: There is also one global notificat

Bon Appétit! We’ve compiled some of the best “recipes” from our Adobe Target customers into the brand-new Chef's Collection: Recipes for Personalization Success eBook  Learn how other companies have optimized and personalized their digital experiences turning ordinary into extraordinary with Adobe Target, so that you can find new inspiration and ideas for what you and your team can cook up next!  These "recipes" may look a little different than those in your traditional cookbook, but they’re loaded with how-to steps and creative inspiration so that you can walk away confident and ready to cook something new up in your personalization kitchen!

Yet again, Adobe should NEVER be sending anything to our end users! Twice this week, our end users have received pop-ups inside the system that should have never been sent to them. As System Admins, we make the decisions on what our users can see and interact with as part of our company requirements and the needs of our platform. Adobe sending surveys or messages about system changes to our end users is unwelcome and frustrating, as they do not align to how we communicate with our teams. Yesterday was a pop-up for a usage survey and today a pop-up for the depreciation of the Scheduler. This is yet another example of Adobe not listening to the community, as this is not the first time these types of threads have been shared. @Jonathan Chen, please help us to escalate this to leadership, because clearly there is a communication gap since this keeps happening.

Author: Gonzalo Vázquez TELUS brought a team of technically savvy people together to unlock new personalization capabilities and scale the practice across an organization in an automated fashion. Resulting in hundreds of hours saved in running a/b tests, increasing user experience and performance. Historically, TELUS personalization team had done an amazing job running A/B tests with the out of the box Adobe Target solution. However, our performance was suffering and customer experience was being impacted which called for a deeper dive into understanding the issue. With TELUS experiencing an increased emphasis on performance, the Analytics & Insights team was also going through a transformative phase. The tools we were using weren’t necessarily optimized for speed. Throughout the year, we implemented brand new tools such as Adobe Launch and Adobe Target Server Side with performance improvement as our main goal. The following post follows the story of our personalization practice

Author: Gonzalo Vázquez At Telus Digital we turn to machine learning models to help us recommend products, predict user’s behaviour and identify opportunities to personalize the experience for our users. Like most companies, we are investing heavily in machine learning and artificial intelligence to help us drive business goals. As we approach maturity in our data science practice we need a way to validate the performance of our models against each other and one way to achieve this is running an A/B test. The Opportunity We have been extremely successful with personalization and A/B testing, mainly due to our ability to integrate with Adobe Target server-side. Since the development of our Personalization API, our personalization and A/B testing practice has skyrocketed. We can deliver fully personalized content to our customers in less than 200ms. Historically, we have only used the Adobe Target to test content, since the Personalization API is integrated with Contentful (our CMS

Author: Varun Mitra Using AEM Experience Fragments with Adobe Target Use the new Experience Fragments feature to reuse a complete set of content for targeted experiences across channels. Experience Fragments, introduced with Adobe Experience Manager (AEM) 6.3, provide an excellent feature set to author content in a channel-neutral way. An experience fragment is a set of content that, when grouped, forms an experience that should make sense on its own. Experience Fragments can be utilized across several channels and tools including your website, Facebook, Pinterest, Adobe Campaign, and Adobe Target. Experience Fragment integration with Adobe Target is particularly interesting as it allows you to leverage AEM Content and use it for creating offers in Adobe Target. These offers can then be used to insert or replace content within different activities. In this blog post we will go over the steps to export AEM Experience Fragments to Adobe Target. Prerequisites AEM 6.4 Author AEM 6.4

Author: Varun Mitra Adobe Target is a personalization solution that makes it easy to identify and deliver your best content. Adobe Target helps you create a targeted experience specific to each customer. Adobe Target is built on the solid foundation of Adobe Experience Cloud and integrates directly with Adobe core services including Adobe Launch, Adobe Experience Cloud Assets and the Adobe Experience Cloud People core services. These different core services provide for information interchange between Adobe Experience Cloud solutions. In this blog post, we’re going to explore the Adobe Target integration with Adobe Experience Manager. For this integration, we’re going to leverage the Adobe Launch core service. Prerequisite AEM Integration with Adobe Launch Integrate Adobe Target with Adobe Launch 1. Log in to Adobe Experience Cloud 2. Navigate to Adobe Launch 3. Select the Adobe Launch property 4. Navigate to Extensions tab 5. Select Adobe Target extension and click “Install” 6. Veri

Author: Chetan Prasad We’re pleased to announce the general availability of the Adobe Experience Platform Mobile SDK, initially released in the fall of 2018. This new major version has been re-architected from the ground up and replaces the existing 4x Mobile SDK. This new Adobe Experience Platform SDK is easily configured and managed via Adobe Experience Platform Launch, and provides a wide variety of new features in addition to the existing functionality from the 4x Mobile SDK.   Watch a short clip to see how we’ve brought Adobe Experience Cloud Mobile Activation to Launch The Adobe Experience Platform SDK is available today for Android and iOS and also includes support for React Native. In addition to server-side and programmatic configuration options, the SDK also supports third-party vendor extensions, and a robust client-side rules and actions engine. The Adobe Experience Platform SDK also introduces support for new Adobe solution functionality such as mobil

Author: David Son Google will begin to impose new cookie policies by default for users beginning with Chrome 80, which is slated to be released in early 2020. This blog explains all you need to know about the new SameSite cookie policies, how Adobe Target supports them, and how you can use Target to comply with Google Chrome’s new SameSite Cookie Policies. Google recently announced that starting with Chrome 80, of which will be released some time in early 2020, web developers will need to explicitly specify which cookies can work across websites. This is the first of many announcements that Google plans to make this year to improve privacy and security on the web. Given the fact that Facebook has been on the hot seat with regard to privacy and security, other major players like Apple, and now Google, have been quick to capitalize on the opportunity to create new identities as privacy and security champions. Apple led the pack by first announcing changes to its cookies’ polic

Author: David Son Privacy and security on the web is a big deal to many consumers. They want to know that when they visit a brand’s website or mobile site that their data is used responsibly and protected. While that’s most often the case, there are other ways to protect consumers that don’t rely on faith in the good stewardship of visitor data. In fact, even well-meaning companies make mistakes, so it’s always a good idea to layer on security. One way that can happen is by placing limitations related to first- and third-party cookies through browsers like Google Chrome and Apple Safari. I give an explanation of what cookies are in a related article that I recently published on Medium. In that article, I discuss how Adobe Target supports Chrome’s SameSite cookie policies, which are designed to protect the consumer’s data privacy. In this article, I want to explain how Apple is similarly providing protections through its ITP 2.1 and ITP 2.2 cookie policies. What is ITP?

Author: Anshul Chauhan We are excited to announce the release of our entirely new Adobe Target Java SDK. Java, being one of the most utilized server-side programming languages, is highly leveraged by our customers. We want our customers to focus more on their business logic rather than the technicalities of integrating with our APIs. Below, we provide our server-side integration goals and best practices to optimize the performance of your Java applications when integrating with our Target Java SDK. What’s Target Java SDK? The Adobe Target Java SDK helps you execute a server-side integration on JVM based architectures using the Target Delivery API. It helps you retrieve and deliver personalized experiences in a highly performant manner. Furthermore, the Java SDK helps manage integrations with Adobe Experience Cloud solutions like the Experience Cloud Visitor ID and Adobe Analytics. There are certain goals that should always be kept in mind while integrating

Author: Vinay Sodha Learn how Adobe delivered a successful proof of concept and technical specification for Bank of America, allowing them to use AAM segments in Adobe Target for their mobile app. As an Adobe Target consultant working with a major American bank, I am fortunate to be on the front line of engaging projects. The bank is continually evolving and looking for new ways to take their personalization and DMP investments to the next level. This year, its pursuit has led teams there to an integration project between Adobe Target and Audience Manager (AAM) within the Bank’s mobile app. This Target/AAM integration is something the bank currently leverages outside of the mobile app on their responsive site, so there has been a general excitement on both sides to extend this functionality to their mobile app. Also, the use case was simple — we all wanted a way to leverage AAM segments to create personalized experiences in Target for both the bank’s responsive site and its m

Author: Bastien Fabing We have all had the unpleasant experience of receiving an email, SMS, or push notification from one or our favorite brands, promising exciting content to find an unrelated experience when landing on their website. Siloed teams and/or a fragmented MarTech are often the origins of inconsistent experiences across a brand digital property. Serverless technologies such as I/O Runtime help marketers close the gap by streamlining data flows and enhancing native capabilities through bespoke functions. Note: This post will put aside the organizational aspect to focus on the technology. Also note that even though the configuration differs for Adobe Campaign Classic and Standard, this implementation is possible with both solutions. If you have Adobe Campaign and Adobe Target, you know they both have decisioning capabilities (Offer Engine for Campaign and pretty much each of Adobe Target features). This dual decisioning brain, often managed by different teams, leads to disjo

Authors: CJaemi Bremner @jaemi_bremner, Colin Ratcliff, Rameen Taheri If you’ve been reading our previous blog posts around how to prepare for the new Adobe Experience Platform Web SDK and the general benefits of the library, you probably have more questions around how this new library will impact each of Adobe’s SaaS products. For this article, we are going to dig a bit deeper and address what potential changes you can expect to see from the Adobe Target platform. What’s the immediate impact on Adobe Target when served through the Adobe Experience Platform Web SDK? First off, as you probably know by now, the Adobe Experience Platform Web SDK will be a unified library, which means there will no longer be a need to call AT.js. All calls will return faster, and as a single packet — drastically lowering load time and browser load. This abstracts Adobe Target calls allowing for a single code source, meaning cleaner, simpler, more efficient

Authors: Artur Ciocanu, Jaemi Bremner This is the third and last part of our series that covers Adobe Target NodeJS SDK with On-Device Decisioning capabilities and how to run it in a serverless/edge compute environment. In this part, we will be covering Cloudflare Workers. This is the third part in our series that covers Adobe Target NodeJS SDK with On-Device Decisioning capabilities and how to run it in a serverless/edge compute environment. In this third installment, we will be covering Cloudflare Workers. The parts are: Part 1a: Akamai Edge Workers and Adobe Target NodeJS SDK Part 1b: Akamai Edge Workers and Adobe Target NodeJS SDK Part 2: AWS Lambda@Edge and Adobe Target NodeJS SDK Part 3: Cloudflare Workers and Adobe Target NodeJS SDKStep by step guide As mentioned in the first two articles, we love Terraform and we use it heavily for Infrastructure Automation. In this blog, we will show how you can leverage Terraform and Adobe Target NodeJS SDK to create an

Author: Artur Ciocanu, Jaemi Bremner This is the second part of our series that covers Adobe Target NodeJS SDK with On-Device Decisioning capabilities and how to run it in a serverless/edge compute environment. In this second part, we will be covering AWS Lambda and specifically AWS Lambda@Edge. This blog is Part 2 in a three-part series that will cover how anyone could use Adobe Target NodeJS SDK to run experimentation and personalization on an edge compute platform. The parts are: Part 1a: Akamai Edge Workers and Adobe Target NodeJS SDK Part 1b: Akamai Edge Workers and Adobe Target NodeJS SDK Part 2: AWS Lambda@Edge and Adobe Target NodeJS SDK Part 3: Cloudflare Workers and Adobe Target NodeJS SDKStep by step guide As mentioned in our previous blog, we use Terraform heavily at Adobe Target. In this article, we will show how you can leverage Terraform and Adobe Target NodeJS SDK to create an AWS Lambda@Edge. AWS Lambda@Edge is a great technology if you intend to run some piece

I am getting ERRORFailed to get refresh token error, while connecting to adobe sign from Adobe Sign integration page. I was taken to the adobe sign login page followed by permission page in a new tab. Upon clicking Allow the new tab is closed, and I see the original tab.OAuth URL I used is https://secure.na4.echosign.com/public/oauth/v2I see the following ajax request in the original window, which fails to obtain token. https://localhost:8443/libs/adobesign/cloudservices/adobesign/createcloudconfigwizard/cloudservices/oauthcloudconfigservlet.json?client_id=CBJCHBCAABAAg0qsh2s6OYZEMVZ-DfuQbQkifhVRL1sX&client_secret=ciKriK_oapa-mZjWp4D8zR8IxV45Df1C&redirect_uri=https%3A%2F%2Flocalhost%3A8443%2Flibs%2Fadobesign%2Fcloudservices%2Fadobesign%2Fcreatecloudconfigwizard%2Fcloudservices.html%2Fconf%2FEsign&refresh_token_uri=nulloauth%2Ftoken&access_token_uri=nulloauth%2Frefresh&code=CBNCKBAAHBCAABAAkB1Xmj_ZIdRugZJEJmGnJGAoFCNgnPHJ&_=1655491258689 In AE

Hello, We have an AEM instance in AWS on EC2 with the datastore on S3 as specified in the white paper. We want to simplify our DR strategy by leveraging the relatively recent feature of AWS S3 multi-region access point to access the datastore. Among other things, this would enable an automatic recovery of the application in case of a failure of the S3 service. However, 2 critical questions remain: Would this architecture be supported by Adobe ? Is this architecture functional ? We have not had the chance to test it yet (soon) but if the S3 connector is not compatible, there is no need to go further for now. Has anyone tried it yet ? Thank you in advance for your support,Mélanie

Author: Artur Ciocanu, Jaemi Bremner Adobe Target always provided best-in-class experimentation and personalization. Our edge network is geographically distributed and we have points of presence in different parts of the world. This allows us to be closer to our customers' users, but sometimes this is not enough, since fundamentally Target always required a network call to retrieve personalized content. We always knew that this is could be problematic for some of our customers who are looking for near-zero latency for experimentation and personalization. In November 2020 Adobe Target launched NodeJS SDK and Java SDK with On-Device Decisioning capabilities. In a nutshell, On-Device Decisioning allows you to evaluate Target activities on-device avoiding a network roundtrip. For more details please check the official documentation here. Adobe Target On-Device Decisioning, while great for server-side use cases where you can use one of our SDKs like NodeJS, Java, and soon&nb

Authors: Artur Ciocanu, Jaemi Bremner EdgeWorker Script Akamai EdgeWorker environment is based on v8 engine, so we can use most of the modern JavaScript constructs like async/await, Promise, etc. However there are some limitations, all these are covered here. When starting to develop using Akamai EdgeWorkers it is important to decide which event handler we want to implement. More details around event handlers can be found here. For the sample code, I have decided to use responseProvider, since I want the EdgeWorker code to react to incoming HTTP GET requests and build an HTTP response. We will be using the Adobe Target NodeJS SDK, so we'll have to get the dependency via NPM using:       $ npm i /target-nodejs-sdk -P       The sample code looks like this:       import { httpRequest } from "http-request"; import { createResponse } from "create-response"; import { logger } from "l

If, perchance, you have selected SAVE or hit CTRL+SAVE on your keyboard and proceeded to wait MUCH longer than you would prefer for Adobe Analytics to present you with the dialogue box to actually CLICK the button to SAVE the most recent update you made to your Workspace.  Here is a simple workaround:Instead, simply select Share > Share ProjectThen, you can make any additional updates, selections on that screen, and then click the UPDATE button, and voilà, your Workspace project has been SAVED!!!No more waiting, and no more frustrations.