What is our primary use case?
Basically, I have used it for the personalization of content and forms. I have been personalizing for different regions, like the US, UK, and others. The forms need to be different, or at least the segment or fragment of the forms, depending on the region.
So, I created a kind of personalization by switching up the form based on the location and certain other conditions. I also did content personalization based on the logged-in user, modifying the product solution using Magic to pull up data and push it onto Adobe Target.
What is most valuable?
I found the recommendation section to be the most valuable. That has been my use case majorly, primarily for product recommendations based on categories we created. Additionally, there was experience targeting, usually used to personalize content for specific users. That goes hand-in-hand with the account.
Another thing is a fortiori, where I was analyzing the experience targeting results and seeing which was the winner. It helped me understand the data better.
AI initiatives:
I could use it in one. There is a new feature in Magento 2 as an Adobe Commerce, where it was using this feature called Configuration (I forget the name of it). It uses the Sensei AI feature in the backend to give customized recommendations for products. I work on a current project that uses this, but it's a separate team. They are using Adobe Target within the front-end framework, and the data coming into Magento is coming from an AI-driven feature using Sensei Analytics.
Learning Curve:
Adobe Target is quite an easy tool. However, since there's a lot of involvement of other Adobe products, you have to be aware of that. When we use Adobe Target, it's not a single product. There is also Adobe Launch or Adobe IO, which we should be executing on.
So, a bit of technical knowledge will be required to understand how to create your experiences. But mostly a front-end knowledge of the framework is sufficient enough to start to work on this.
What needs improvement?
I still feel that there is room for improvement in integration. For example, if I have the entire repository or schema downloaded into my AEM from any commerce platform, like Hybris, and I want to personalize the content based on user criteria, such as product suggestions, there is a bit of an impasse there. There's no direct way to do it. We always have to find some workaround to get in and get the details.
If we could expose everything directly target, it would be easier. For example, if I could push login information from AEM by the name, and then from Hybris or any other commerce engine, say I have the keyword "night issue." I could then make a suggestion related to night issues to the user.
Basically, I want this feature to be customizable in AEM now that Launch is being removed as a data source or integrator between the analytics engine and Target. Now it is becoming more difficult. I'm not sure how IO works right now for this. Instead of Launch, they replaced it with IO, but I'm not sure how they are doing it. This is one major change that I felt should be improved.
For how long have I used the solution?
I have been using it for six to seven years.
Buyer's Guide
Adobe Target
September 2025
Learn what your peers think about Adobe Target. Get advice and tips from experienced pros sharing their opinions. Updated: September 2025.
867,370 professionals have used our research since 2012.
What do I think about the stability of the solution?
It breaks down. For example, if I have nearly around 300,000 products or 300,000 total overall list of elements. At that time, it has a limitation—something like only 30,000 or 40,000 total audiences can be created. There's a limit for audience creation; otherwise, it breaks.
This is something I experience with my current client, where they are saying that if they create more than 100,000 audiences, then there is a problem. It does not work.
So there are some issues when it comes to stability.
What do I think about the scalability of the solution?
There are certain problems. Recommendations sometimes do not work when there are too many of them created. The Java script created inside the recommendation fails to load.
There are also some limitations in capability to include other languages, other front-end frameworks. For example, if I'm trying to use Vue.js or Node.js as a template for recommendation, then there is a problem with that.
Number of end users:
There are no more than two or three people. But then there is major involvement from the business team, who create the scenarios for us to implement these things. So, it's mainly a business team that gets involved, and then the size increases. Otherwise, it's just two or three technical members.
How are customer service and support?
I did contact support, but it was mainly project or requirement-specific. If something is not working, if there's an issue coming in, then we interact. Otherwise, it always goes through an Adobe ticket, where we have to provide clarification for the project. So we can't go beyond that.
Which solution did I use previously and why did I switch?
I am experienced with the whole Adobe product suite. I'm an Adobe Solutions Architect, and I have knowledge of and experience with AEM and other CMS products, like CQ5 and Experience Manager. I work mainly as a full-stack developer. I got into all these Adobe products nine years ago.
So, I chose it because I have a lot of experience with this tool.
How was the initial setup?
The setup is easy. But, if I need to push the customized algorithms, I felt like using Launch was easier than IO because I could use Launch to integrate multiple other frameworks to pull in the data and make personalization better.
What's my experience with pricing, setup cost, and licensing?
All Adobe products are a little bit on the higher side, although it depends on the overall margin and the investment that a particular customer is looking for in a feature, because it's all about personalization and a better experience for the user.
When they come to your web app, how much revenue can you generate with it? It's all about the business. What kind of insight do they want to create, and how do they want to promote and show it to the customer? There's a scope of business that influences it, but then it depends on the overall profit margin that they are making.
What other advice do I have?
My advice: If you are really into the commerce section, like retail and e-commerce sites, then Adobe Target is quite beneficial. You won't have to write too much code to provide personalization to specific users.
There's a full dashboard created for you to define what you want to personalize and how you want to display it. There is a categorization between the audience experiences and recommendations, where you can easily write your own criteria.
With some technical and business members integrating together, they can write it easily. And in a very short span, you can personalize the content that you want. So, there are no major changes required from the AEM side. It is a good product for use in the retail and e-commerce sectors.
It also works for banking and finance when you're using forms. It does a lot of personalization based on criteria for region-specific or local-specific needs. That is also something that Adobe Target is very good at.
Overall, I would rate it a six out of ten because of the lack of integration, the stability issues, and a couple of other things.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. customer/partner