The product is very good, but recently they migrated from the old UI to the new UI. In that case, the documentation was not up to the mark. It was difficult for me to get to know the new product UI. The documentation part could have been done in a better way, which was something that needed improvement at that point.
The customer support team is very slow in responding to queries. If the support team could be quicker in responding, it would be much improved. Sometimes the system slows down, and we need to move certain campaigns into the archive folder to prevent lag. Major lag occurs when there are a large number of campaigns.
There's room for improvement in Adobe Target, especially when simultaneously implementing the same activity across multiple websites. Currently, we can only run one activity per page, which can be limiting. Also, running various activities concurrently or executing near-real-time use cases can be complex and challenging with Adobe Target.
I think the configuration of Adobe Target is carried out manually. I think that since it is an Adobe tool, it has to be integrated directly and or given to the user or developer who is working on it. The configuration part at a dispatcher level has to be made a bit easier so that it can be more in the market. As of now, based on how one plays with the policies or based on page policies, the parent and child hierarchy is what we are following right now in our company, and if there is some segregation in that, that will help, especially if we plan to do some follow-ups. The solution's technical support team is an area with certain concerns where improvements are required.
VP at a financial services firm with 10,001+ employees
Real User
Top 20
Jun 6, 2024
I think Adobe Target needs more AI features to automate some things. Regarding integration, it is easy to integrate with their AM platform for hosting websites, but it isn't easy. They need to do more work to ensure their tools are easily connected and work together. That's something I'd suggest they improve.
Adobe Target & Adobe Analytics Developer | Implementation SME at C&F
Real User
Top 20
May 29, 2024
I believe that there is still a need to improve on optimization, like the way Adobe works. However, Adobe Target affects the performance of the websites whenever I use it, and it has to omit or mitigate the impact of performance. This is the place where the team should still work on improvement. For example, when I use Adobe Target, I have to use individual libraries for every single part of analytics is separate and targeted separately. I'm not using Alloy JS, which makes the entire system work sometimes not in the optimal way. Also, regarding the identification of the visitors, I think that this is another idea that Target should be more straightforward about. For example, when you have your profiles, you can upload them, but it's very hard or impossible to actually get the actual information about the individual profiles or partial profiles. You can still create and upload them, but I think that these areas are where I would see a benefit if Target would give you more visibility into what profiles you currently have and how you could optimize them and things like this. A little bit is going in the direction of CDP, or something like that, where you have the proper information, and Odion's creation is under better control.
Senior Application Development Specialist at Accenture
Real User
Jun 21, 2024
Since we are currently shifting to the server side, some browsers are going to block the third-party cookies. Right now, we have web-based VPN and mobile-based VPN for the server side, which still need to be improved. It will probably take some time. I think it is on their radar right now. The solution currently lacks more personalization through the server side.
Technical Lead at a tech services company with 501-1,000 employees
Real User
Jun 14, 2024
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.
Adobe Target can improve its reporting and dashboard creation. It would be beneficial to have clearer segmentation options with more dimensions and metrics available. Tracking and tagging users can become easier if there is an option to modify user demographics and provide default settings for e-commerce and digital marketing sites.
Integrating Adobe Target with other tools posed challenges, particularly in obtaining accurate analytics data. While using it for testing and analytics, I found that the analytics reports provided by the tool did not accurately reflect the specific changes made in the tests. Instead, it included broader data from the overall experience. The recent user experience update is glitchy.
Adobe Target is a robust digital marketing tool primarily used for A/B testing, personalization, mobile app optimization, and automated recommendations. It enhances user engagement, personalizes visitor experiences, and boosts overall business performance. Users appreciate its user-friendly interface, precise audience segmentation, and the ability to launch campaigns efficiently, making it essential for effective digital marketing strategies and organizational efficiency.
The product is very good, but recently they migrated from the old UI to the new UI. In that case, the documentation was not up to the mark. It was difficult for me to get to know the new product UI. The documentation part could have been done in a better way, which was something that needed improvement at that point.
The customer support team is very slow in responding to queries. If the support team could be quicker in responding, it would be much improved. Sometimes the system slows down, and we need to move certain campaigns into the archive folder to prevent lag. Major lag occurs when there are a large number of campaigns.
There's room for improvement in Adobe Target, especially when simultaneously implementing the same activity across multiple websites. Currently, we can only run one activity per page, which can be limiting. Also, running various activities concurrently or executing near-real-time use cases can be complex and challenging with Adobe Target.
I think the configuration of Adobe Target is carried out manually. I think that since it is an Adobe tool, it has to be integrated directly and or given to the user or developer who is working on it. The configuration part at a dispatcher level has to be made a bit easier so that it can be more in the market. As of now, based on how one plays with the policies or based on page policies, the parent and child hierarchy is what we are following right now in our company, and if there is some segregation in that, that will help, especially if we plan to do some follow-ups. The solution's technical support team is an area with certain concerns where improvements are required.
I think Adobe Target needs more AI features to automate some things. Regarding integration, it is easy to integrate with their AM platform for hosting websites, but it isn't easy. They need to do more work to ensure their tools are easily connected and work together. That's something I'd suggest they improve.
I believe that there is still a need to improve on optimization, like the way Adobe works. However, Adobe Target affects the performance of the websites whenever I use it, and it has to omit or mitigate the impact of performance. This is the place where the team should still work on improvement. For example, when I use Adobe Target, I have to use individual libraries for every single part of analytics is separate and targeted separately. I'm not using Alloy JS, which makes the entire system work sometimes not in the optimal way. Also, regarding the identification of the visitors, I think that this is another idea that Target should be more straightforward about. For example, when you have your profiles, you can upload them, but it's very hard or impossible to actually get the actual information about the individual profiles or partial profiles. You can still create and upload them, but I think that these areas are where I would see a benefit if Target would give you more visibility into what profiles you currently have and how you could optimize them and things like this. A little bit is going in the direction of CDP, or something like that, where you have the proper information, and Odion's creation is under better control.
Since we are currently shifting to the server side, some browsers are going to block the third-party cookies. Right now, we have web-based VPN and mobile-based VPN for the server side, which still need to be improved. It will probably take some time. I think it is on their radar right now. The solution currently lacks more personalization through the server side.
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.
Adobe Target can improve its reporting and dashboard creation. It would be beneficial to have clearer segmentation options with more dimensions and metrics available. Tracking and tagging users can become easier if there is an option to modify user demographics and provide default settings for e-commerce and digital marketing sites.
Integrating Adobe Target with other tools posed challenges, particularly in obtaining accurate analytics data. While using it for testing and analytics, I found that the analytics reports provided by the tool did not accurately reflect the specific changes made in the tests. Instead, it included broader data from the overall experience. The recent user experience update is glitchy.