Adobe Target Reviews

Our company uses only Adobe products including Adobe Launch, Adobe Analytics, Adobe Target, and Adobe Experience Manager as a CMS platform and back-end platform.

We have one authenticated portal where users have access to different types of equipment, ordering parts, and rebuilding kits. I work for a manufacturing company, so users have access to two different sub-applications. Based on these sub-applications, we show them personalized banners. For example, if you have access to only ordering parts, you will see only the ordering parts kind of personalized banner when you log in to the website. We provide personalized content to users based on their roles.

In Experience Manager, we perform authoring tasks. For example, if I need to add a form to my website, I need to author it from the Web Experience Manager, and then that will be available. However, that requires a release and everything. With Adobe Target, we can create an Experience Fragment and export and import it into Adobe Target, and we can use that Experience Fragment as content on the website. This does not require a release, and we save a lot of time in that process.

We have saved a lot of development time. Usually, if we have to push changes to production, we need to go through a release cycle. We need to push our changes to QA, stage, and then production. We have a sprint of twenty-one days. With Adobe Target, if we want to do a hotfix or something of that kind, we can do it immediately, test it immediately, and push it to production without a release cycle. This saves money, time, and resources.

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.

My total experience with Adobe is eight years and two years with Tealium.

I can give Adobe Target a ten out of ten on stability.

Adobe is providing really good support. I give them a ten out of ten on that.

The main competitor would be Optimizely, which is maybe the main competitor for Adobe Target.

I am working on the analytics side, so I am not aware of the web experience tool. However, because I am working on the analytics side, you can ask me about Launch, Adobe Target, and Analytics.

We have one Adobe Report Builder, which is one of the Adobe add-ins. It is an Excel add-in that is provided by Adobe. We have prepared a few reports for our business that are automated and automatically sent to the user. The business does not need to change anything in that report.

In Adobe Target, we can prepare a report, but it has some limitations. When we export the Adobe Target report with Analytics, we can do a lot of things. We can work with all the metrics and dimensions that are present in Analytics, and we can definitely derive a lot of insights from the Adobe Target report that is exported to Analytics.

It has a good impact.

It is very good.

Adobe's products are on the higher side.

Considering stability, scalability, cost, and documentation—considering everything, I give the product an eight. The two points I deduct are for the cost and maybe for the documentation. Otherwise, from the product point of view, everything is good. My overall rating for this review is eight out of ten.

Adobe Target is a cloud-based tool that is part of the Adobe Experience Cloud. It is used in segments where we have to use personalization on the fly. I can use the solution to perform A/B testing or make recommendations for website development.

I work in a media company that has technology in data centers. We have industry requirements where we need to put on some campaigns, do some marketing, or prepare some tools that are deployed on the website. There is always scope for improvement because our clients operate in a vast geographical region.

There could be a scenario where some campaign or the visual appeal of a website works best in one region but may not be suitable for the other region. We form such a hypothesis, and Adobe Target is the right platform to test this hypothesis. The tool helps us better understand what kind of visualization or experience works best in a region or with a specific audience.

Adobe Target gives valid data to test such hypotheses. The solution has some critical tools with which you can do A/B testing, multivariate testing, recommendations, and other types of testing. When you reach a confidence threshold score of around 95%, it gives valid data that you are good to go with this particular experience in this region. This is a baseline scenario that Adobe Target helps in.

Adobe is currently working on some things. There are two types of composers. There's a visual composer, and then you have a code-based form composer where you can set up your experience. The user interface for the form-based composer is slow, and the loading time is not optimized. Optimization is needed for the tool as the requirements are rapid, and the client asks to implement the solution in a week or so.

Secondly, there is a need for integrations because when you have data coming from Adobe Target, you might want to put it into some visualization tools. Currently, we can use a component called A4T in Adobe Analytics to import the data directly. We can put the data in Adobe Analytics, but it needs some connectors or APIs to Adobe Target through which we can connect it to multiple platforms.

This could be very feasible and handy if I want to visualize the data in Power BI or other tools. These kinds of things and optimization are needed for Adobe Target to become the number one tool for personalization.

I have been using Adobe Target for six to eight months.

Adobe Target is a stable solution. I have used it in a couple of production databases and production projects. There's hardly any downtime. Unless and until there's a scheduled downtime announced on Adobe's official website, I haven't faced any difficulty. I haven't faced any latency issues with the tool. Everything works fine if you have configured the setup perfectly at the start.

Our data science team has around 1,000 or 1,500 people working from India. We always offer Adobe Target and Adobe Analytics to our clients. My organization has quite a large number of users who are using the solution.

Adobe Target's technical support team is very good. I contacted the support team in a couple of instances, and the issues were resolved quickly. They reply via email in an hour or so because I've already used my business email to send the queries. Adobe also has a forum where you can connect with the official developers and ask questions directly in their inboxes.

The solution's initial setup is very easy. There's nothing to install, and the setup on Adobe Target is very easy compared to other personalization tools. You just have to log in and use the URL, and you can quickly set it up in minutes.

The solution's setup, implementation, or deployment is not difficult. It's very easy and user-friendly because it is set up so that most things are automatically configured. There's hardly any manual configuration required, making it an on-the-fly tool.

Adobe Target comes with two pricing plans that are totally dependent on the type of business use cases you have. There is a standard plan or standard edition, where you can use only a couple of features. This standard plan is not expensive. This plan is suggested if you want the solution for a basic use, like A/B testing.

Three other features come under Adobe Target Premium, which is quite expensive if you have a large team. Adobe Target Premium is an advanced version, which is more expensive than the Adobe Standard. It has three other tools, including automated personalization, which is machine learning, and recommendations in Adobe Target. That totally depends on the use cases.

I would recommend Adobe Standard for first-time users because it is very inexpensive and easy to use.

There are three reasons to use Adobe Target. Adobe Target is the prominent tool to use if you want to spend less time testing your personalization or hypothesis using an A/B test. The support of the solution is really good because it is feature-rich. Community support is very intensive if you are stuck with a problem because of multiple instances. There are already documented chats and blogs around it.

There would be hardly any issue setting up or implementing the tool. Adobe Target has many features, and since it uses machine learning to create a recommendation, you don't have to hardcode anything. You just have to connect with your website, and you're ready to use it. These are the top reasons why I would recommend the solution to a first-time user.

There's scope for optimization, but that doesn't feel so if you have been using it for a long time. The solution's features are really impressive, and I think it would do justice for big projects where someone has to do large-scale website testing.

Overall, I rate the solution an eight out of ten.

I have used Adobe Target for different purposes. The most basic use case is A/B testing. We run random tests on the website. Additionally, I use Adobe Target to run various campaigns. For example, on an e-commerce site, I help the client run a flash sale. Suppose the client wants the flash sale to be visible only to users accessing the website from Europe. I build and develop the campaign to ensure that only users from Europe see the banner for the sale. If users from the rest of the world access the site, they won't see the banner. This is one of the normal use cases I handle for different customers.

Another use case is running recommendations. Similar to what you see on Amazon, where it shows "people who bought this also bought that," Adobe Target can implement these recommendations. I worked on this for a client. When a user visits their website and views or buys products, they start seeing related products at the bottom, like "you might also like these products." For example, if you visit a mobile phone product, you will see similar electronic products. This is another use case I handle with Adobe Target for different clients.

A/B Testing and Navigation Optimization

In terms of A/B testing, we handle basic use cases and complex ones. For instance, I recently worked on a complex use case for a client named Helly Hansen. They wanted to test a new navigation method on mobile devices. Instead of opening different screens, they wanted customers to see all sub-navigation links on the same screen using an accordion. Clicking a link would show all related sub-navigation links within the same pop-up, without navigating to different screens. We just went live with this test. This is an example of the complex A/B tests I handle using Adobe Target.

Additional Tools and Personalization

While Adobe Target is a primary tool I use, I also work with other personalization tools like Dynamic Yield and Optimizely. These tools complement Adobe Target in delivering personalized experiences to users.

There’s nothing specific I like best because recently, I’ve started using Optimizely, and I prefer it. Optimizely is also a tool in the same realm, where you run different tests for customers. I like Optimizely better than Adobe Target because Adobe Target was one of the first tools on the market for A/B testing, but now I don't think Adobe is making many changes to the tool.

When I look at other tools in the market for personalization, they are bringing new features. For example, on a single-page application (SPA), where the page doesn't refresh when you click a link, recent websites handle this well. However, Adobe Target, being an older tool, hasn't done much to address this. Other tools, like Optimizely, have special functionalities for handling SPAs effectively.

Handling Single-Page Applications:
Adobe Target handles SPAs, but not in a very efficient way. They require users or website owners to develop something on their end to trigger a call for every view they want to run an experiment or test on. This approach is not very user-friendly. Tools like Optimizely have better solutions for this issue.

Personal Experience and Usage:
So, there isn’t a particular feature in Adobe Target that stands out to me. It was the first personalization tool I used extensively, but now I find other tools more advanced and user-friendly.

Ease of Use:

In terms of the tool itself, Adobe Target is easy to use. Everything is readily available and intuitive, making it easy to understand how to use it for basic tests and other functions.

There is room for improvement in the way Adobe Target handles single-page applications. 

Single Page Applications Handling

If they want to handle single-page applications, they should not require website owners or their developers to implement additional functionalities for it to work. There should be a built-in solution within the tool itself. 

Currently, they ask for changes like sending trigger views for each page (e.g., product landing page and product details page) to make single-page applications work. 

This approach creates double effort—one on their end and one on the website owner’s end. Adobe Target should provide more comprehensive options within the tool to handle these situations efficiently.

Documentation and Recommendations

Regarding recommendations, the way they are configured in Adobe Target is not very well-explained. Only developers can create recommendations effectively. Business users won't be able to do so efficiently just by reading the documentation. 

The documentation is very general and superficial; it doesn't go in-depth. Improving the documentation to make it more detailed and accessible for all users would be beneficial.

I have been using it for five years. 

There are some stability issues. Sometimes, their servers go under maintenance, and the website becomes unavailable for one to two hours. This can be disruptive when I try to make changes or deploy updates in a production environment.

On a scale of one to ten, I would rate Adobe Target's stability a six.

Adobe Target is not very scalable. In the five years I have been working with the product, I haven't seen significant improvements in its scalability. While other tools in the market have become much better, Adobe Target hasn't scaled to the same level. I would rate its scalability a four or five out of ten.

Number of Users

In my organization, only five to six people use Adobe Target. We are a central team that utilizes the tool, while other teams do not.

While Adobe's support team generally addresses critical issues quickly, I've found their support to be not very active overall. They tend to rely heavily on email communication, even for high-priority tickets (P1, P0), which can be frustrating. They should be more proactive and available for calls to resolve issues promptly. The proactiveness is not there. 

I've experienced this lack of proactiveness multiple times (more than 20 or 30 times) and believe their support system could be improved.

I would rate their support a three out of ten. The problem is that their support staff is not very knowledgeable. Every time I raise a ticket for my bug-related issue, they have to consult their engineering team, causing delays for both them and me. Their knowledge is not vast enough, so I often end up waiting for their engineering team's response.

Negative

The initial setup of Adobe Target is relatively easy. It can be integrated with various tools or deployed separately. Adobe recommends using its tool, Adobe Launch, for integration, claiming it makes the process easier. However, deployment is not difficult, even without Adobe Launch.

Deployment Time

Deployment is not difficult or time-consuming. We no longer deploy code directly on the website; instead, you create and test something, then simply press a button to deploy the code. I have not had any challenges during deployment.

At this point, it is not worth the money because there are different tools on the market that are much cheaper than Adobe Target.

Adobe Target is expensive.

If you are willing to spend the money, then okay. But if not, there are other tools in the market. If comparing Adobe Target and Optimizely, both of which are expensive, I would always suggest Optimizely to the client and not Adobe Target.

I would give Adobe Target an overall rating of five.

I use Adobe Target primarily for creating A/B tests and doing personalization.

The best features are the form-based and visual-based methods. The form-based method allows us to use languages like JavaScript, HTML, and CSS to create campaigns, while the visual-based method offers a user-friendly drag-and-drop interface to create campaigns. The audience segmentation feature is very useful as it integrates with Adobe Audience, allowing for better filtering and targeting of audience segments. These features are particularly useful for creating campaigns and personalizing them based on audience segments, targeting particular audiences easily after using Adobe Audience.

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.

I have been using Adobe Target for over eight years.

Sometimes the performance gets reduced, but overall, it is quite good.

Scalability is good, but performance can dip at times.

Customer support is quite slow and needs to be available 24/7. It is necessary to wait more than a day for a solution to a query.

Neutral

I am not using a previous solution.

The initial setup was straightforward.

I have already shared it. In two weeks, we achieved a six to seven percent increase in revenue.

It is not my part. It is the manager's part.

I evaluated Optimizely, VWO, Google Optimization, and AB Tasty.

Adobe Target is the simplest tool for A/B testing. The user interface is very easy to use, and it is self-explanatory. Just go and start by looking into the documentation provided on the Adobe site. I rate the overall solution a seven out of ten.

Adobe Target is mostly used to personalize user experiences on websites. It helps businesses deliver targeted content and offers to different audience segments based on their behavior and preferences. This tool is widely used across e-commerce, telecommunications, and finance domains to achieve specific conversion goals tailored to each website's needs. It allows for retargeting users who have previously interacted with the site and conducting A/B tests to compare different versions of content or offers to optimize website traffic and conversions.

Additionally, Adobe Target offers features like multi-variation testing, automated personalization, and recommendations, which are particularly beneficial for e-commerce websites. Integration with other Adobe tools like AEM and Adobe Audience Manager further enhances its capabilities in audience segmentation and analytics for retargeting strategies.

This is a significant concern due to the absence of a lower environment for testing activities. This can lead to issues if changes are pushed to production by mistake. Additionally, the effectiveness of Adobe Target is heavily dependent on the Target library; if the library files are blocked, no changes will be visible on the website or mobile app.

We have some bugs. For example, suppose I'm creating the activity because of all the activities we create. In that case, we have to get the data from user interaction and understand how this activity was performed. In some rare scenarios, we couldn't capture the data after the activity was published in production because of some issues on Adobe Target's end.

It doesn't provide the proper data in Adobe Analytics. After that, we have to contact the Adobe customer support team and work with them to get that data. A few times, the particular libraries' location is also not properly detected. For example, if I were in London, it would take some other location, like Scotland or some other place. In a few of the implementations, I noticed that the library also is not taking the proper location.

I have been working with the product for six years. 

My company has 250 users. We manage all Adobe Target, and the remaining 150 manage analytics, audience manager, and Google Analytics. So, we have a combination of projects with different vendors, and we support them.

I contact the technical support team whenever I want to update the website's privacy content. Support depends on the developer who is assigned to us. Some of them prioritize closing the tickets as soon as possible. But most developers give the default guidance, which is already present on the Adobe website. They share that link, and I have to follow the steps. However, some developers connect directly with us through meetings, like Teams or Google Meet, and sit with us to rectify those issues. So, it depends on the developer assigned to the ticket.

Neutral

The tool's deployment is feasible.

The solution's ROI depends on how frequently we use it. If you spend money on Adobe Target, you must create at least five or ten types of activities per week to retarget users or increase conversions. Many clients invest in the solution but do not utilize it properly. They implement it but only do simple A/B tests and one or two types of activities weekly, which do not generate more revenue. Frequent testing with Adobe Target can provide very good revenue for website owners.

We can implement two types of target libraries: one from the client side and another from the server side. 

Choosing the tool is completely based on the business, its expectations, and its budget. We prefer Adobe products with the Adobe Analytics cloud and its whole structure and architecture. If they don't have the budget for Adobe, we provide other products.

If you want to go with Adobe Target, I need to know your website, how it was created, how it can access the library, and your main goal and conversions. The main thing is the budget because Adobe Target is more expensive than other optimization tools. If budget is not an issue, I would recommend Adobe Target.

Adobe Target offers many options. We can implement it on a website, mobile app, or other internet-related tool. We can also email and integrate with other APIs. If your website has the required capabilities, we can use Adobe Target.

Tool-wise, learning how the tools work and react is relatively easy. However, it's important to understand basic coding concepts like HTML, CSS, and JavaScript before diving in. These are crucial because they play a significant role throughout the tool. For instance, when creating activities such as pop-ups or displaying content, knowing HTML, CSS, and JavaScript helps determine where and how to insert them and what actions they should perform.

Apart from understanding the tool itself, it's essential to grasp how the Adobe Target library functions and the scenarios it supports. After that, it's important to familiarize oneself with the features and functionalities available within Adobe Target. Understanding the range of activities possible and how frequently we can utilize these options is also key.

Moreover, it's crucial to learn what can and cannot be achieved with Adobe Target and the underlying logic behind each activity. For example, depending on the activity, traffic might be split differently. For instance, with an AB test, we can present one experience to one audience, whereas with experience targeting, multiple audiences can see multiple experiences.

I would rate Adobe Target an eight out of ten because it's more than just a tool for AB testing or experience personalization. It offers numerous options and responsibilities compared to other tools. Integrating Adobe Target with Adobe's cloud products is straightforward. However, integrating with other technologies like Google Analytics or Tealium, which many businesses already use, can be challenging—not impossible, but more complex.

The main purpose of the target is to personalize and optimize user behavior. If we consider that you are visiting some page today, let us assume that you are interested in Nike shoes or something. What will happen is that since you have visited the site containing the Nike shoes, a personalized banner or a personalized offer, particularly for a specific user based on some criteria, will be made visible to those users who have visited the home page and the Nike shoe page.

The most valuable feature of the solution is the personalization area. The other valuable feature of the solution is the AB test. If we are planning to have a new UI, you can push that new UI to a limited number of folks in the initial phase, and then eventually, you can replicate the older version and bring your new version. In the whole process, you can evaluate whether your new UI is working or not or if you need to stay with the existing UI. You can make some analysis based on your old UI. You can do the analysis since data is collected in Adobe Analytics. We can analyze whether the user is clicking or not and whether he or she is converting or creating a lead, and based on that, we can do an A/B test as well, and then we can have some automated personalization. For multiple personalizations, we have to configure them in the back end, and then automatically, it will start flowing to your browser or the application randomly, so it is not, like, fifty-fifty or seventy-thirty and is not fixed. It will randomly show you Abc, for example. Ten times 'a' will appear, ten times 'b' will appear, and ten times 'c' will appear. If you eventually click on 'a' multiple times over a period of time, you will get 'a' as an experience or your default experience. It will mitigate your low-performing personalizations or experience over a period of time, and it will make it like a high-performing default experience. Then, we have the product recommendations or content recommendations. The recommendation is something that if you have viewed a specific product, like Nike shoes, then what will happen is that we can retarget that particular user with some offers on that specific product. We can also have default algorithms that talk about how people who viewed this also viewed that. We can look at the most viewed products or top products. We have these algorithms built into Adobe Target, which we just need to use and retarget the users.

From a mobile application standpoint, we have very limited resources. Maybe my knowledge is limited in terms of testing and validating my experiences, making it areas that need to be made more user-friendly.

I have been using Adobe Target for a year and a half to two years. My company has a partnership with Adobe.

So far, I haven't seen any breakdown or downtime. It has a very low downtime.

Currently, I think six or seven people use Adobe Target in our team, and I don't know anything outside our team.

I have had conversations with the solution's technical support team on specific issues. From Adobe Target's standpoint, my conversations with the solution's technical support team were different and related to technical issues we faced during the implementation phase, but they were nothing related to the product level.

My company has been using Adobe products, and so we have aligned ourselves with the tool associated with it.

The product's initial setup phase is easy when done on the web, but for mobile phones, it is a little complicated. I would not say it is difficult and would rather describe it as a lengthy process to follow.

The solution is deployed on the cloud. Adobe has its own cloud.

It has a high cost, so it is not a product that everyone can afford.

Whether one should use the product or not is something that depends on your business requirements and what is the purpose of using Adobe Target. I would recommend using the tool or not, depending on your use cases. If you are looking for something for personalization, optimization, and testing of different URLs, I would suggest you go ahead with Adobe Target, but if you are thinking of capturing the data or analyzing the data, then I won't recommend it to you.

The tool is easy for beginners to use. There are many guides available online to help with using Adobe Target and following the steps mentioned in them is pretty easy. The tool is not difficult if you have a little bit of technical knowledge associated with HTML or JavaScript.

My company has multiple options if we compare Adobe Target with other products, like Optimizely, but it has very few limitations. From Adobe, we have the feasibility of getting analytics data directly, and we don't have to do many integrations for that. It is very easy for Adobe to occupy space within other ecosystems as well as Adobe's ecosystem, which is a pretty good thing. Adobe's team provides quick responses, so we don't have to spend much time getting it online or in production. With the tool, we have the visibility of enabling, disabling, and scheduling the enablement of the activity.

I rate the tool an eight out of ten.

I use the solution in my company since we are dealing with and working on a cybersecurity site, and it includes both the financing and the cybersecurity parts. What we do is that we provide different user experiences. My role is kind of playing with JCR and properties for each and every page. Based on the properties, if someone logs in and checks their health benefits and all, then for health benefits, I will show one particular tab that has to be displayed to the users, where they can navigate and get the data from the back end. If someone goes from health services to car financing or some other area, then the particular option I introduced for health services will not be there. I am playing with the tool based on the customers, based on whoever is logging in, and what type of login they use. Based on the aforementioned area, I can filter using the page properties, and based on the properties, I can use Adobe Target. I can push up what content needs to be shown on a page. Each user will have a different user experience while working on the page.

The most valuable feature of the solution stems from the fact that you can enhance the page all the time. It involves a little policy work, specifically the page policies we implement using Adobe Target. That is how even if you show some pop-up or something on the page related to whatever the user is searching on based on JCR, you can manipulate what you are showing over there based on how the look and feel has to be there, and based on the policies for that particular page. The aforementioned area consists of details that grabbed my attention more because I feel that if the customer is looking at the page with the same kind of pop-ups all the time, I don't think it will look attractive or will get the customer involved in the page.

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 have been using Adobe Target for two years. I am a customer of the tool.

The stability part is something that varies from site to site, or depending on what site you are working on, it is possible to have cloud integrations if one prefers to have them. My company faces issues basically from a dispatcher and cache level, but I don't think it is a major issue.

Stability-wise, I rate the solution an eight out of ten.

It is a scalable solution.

Our company's developer team uses the tool. In my particular team, around three to four people handle Adobe Target. There are different teams using the tool for different purposes.

I rate the technical support a seven out of ten.

Neutral

I have experience with Adobe Analytics. I also have used the regular SIEM tools and servers.

The product's implementation phase is difficult since it is something new. People have to get involved in the tool, and it may involve some new learning curve. I feel that instead of Adobe Target being involved with tools, it already comes with some in-built foundation components.

The time required to deploy the product is something that varies for each individual. Dealing with the integrations of the product is something that is new for me. The integration of the product with different components is an area that I am new to right now. Dealing with the configuration parts and how you pull them in your page is something where some learning curve is involved, but once we learn it, then things become easy since one can get a better understanding of your free time and a better understanding of it. Even the documentation part of the tool is difficult to understand because it is new in Adobe Target. The documentation part is a bit difficult to understand. I feel like there should be an easier way to deal with the documentation part, and if it is improved, then it can help Adobe Target get more attention in the market.

The tool is easy to use. The only tough part of understanding revolves around how you include it at the dispatcher level and how you are integrating it into your page site, including what codes, what URLs you are giving into your page, and how you add your configurations and the dispatch level. The aforementioned areas need to be taken care of properly, and the remaining parts are easy to manage in the tool.

I would recommend Adobe Target to other people.

One needs to look into the implementation part of how Adobe Target can be useful for day-to-day activities in their company and how it can help grab the attention of the customers and make life easier for them. Once the integration is done, the tool will be used. There are multiple use cases associated with the tool, such as how to segregate, how the coding part can be reduced or simplified, and how you can project it to different pages in a different way.

I rate the tool an eight out of ten.

I use the tool for A/B testing to optimize user journeys and improve conversion rates. I also use it for various activities within marketing campaigns, including email campaigns and public-facing website interactions.

I find Adobe Target very good for long optimization tests. After testing, it tells you which version is the winner and what improvements can be made. This gives me the confidence to provide a better customer experience by adopting the winning version of the page I'm testing.

The most valuable features for me are how easy it is to create a testing version, edit and modify it, and launch a test. Segmentation is very basic and easy to use when running tests. I can target my audience and select what kind of audience I want to test with. For example, if I have a pilot campaign, I can test it with people who see my landing page, not those who don't.

Segmentation lets me look at different users. When I talk about segmentation, I mean classifying or defining the audience. I can segment based on whether they're existing customers or new prospects, which sections they've visited before, where they live, their income, age, gender, financial status, and whether they use a computer or mobile device. I use these criteria to define the user experience.

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 have been working with the product for seven years. 

My company has 75 users. 

Adobe support is good. 

Positive

The setup isn't complex, but it's hidden. For implementation, we go through an enterprise review to get all teams on board with using the tool. We do testing to make sure it doesn't break anything. The initial deployment takes some time, but it's not particularly difficult. It's mostly about working together to manage the user experience and get the whole organization on the same page for launching the product.

Deployment usually takes two to six months. You need about two or three people from your company, plus support from Adobe. For maintenance, Adobe Target is easy to maintain. You don't need much maintenance - it just runs. You can contact Adobe support if needed.

Based on the optimizations and improvements we've made compared to the product cost, we've seen a good return on investment.

The solution's pricing is reasonable. 

It's a cloud implementation, so that you can access it from anywhere, but one team usually maintains the relationship with Adobe. I would recommend Adobe Target to other users, especially those in the banking and financial industry, where it's popular. I'd rate it as an eight or nine out of ten.

The solution is mainly required for personalization. I recommend products to users based on their history. Users visit the website and view a few products. Based on their search results, I recommend similar products or other relevant products to them on the home page or the product page. I also use the solution for A/B testing. If a feature goes well and can be converted permanently using the EVM, it can be shown to all users across the group. We use the solution for personalization and A/B testing.

Today, users want everything at their fingertips. With the solution's personalization, we can recommend to users the relevant products they are searching for.

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 have been using Adobe Target for more than seven years.

Adobe Target is a stable product that properly reaches out to its audience. I haven't experienced any breakage with the tool.

Adobe Target is a scalable solution. Around 15 users are working with the solution in our organization.

The solution's initial setup is a bit time-consuming. We need some experience with Adobe Launch or any tag management solution. You should know how to implement it. Although the extension of Adobe Target is available, setting it up needs some experience.

Adobe Target is deployed on the cloud in our organization. Adobe Target can be implemented through different tag management solutions. We can utilize the product data in Adobe Target irrespective of the vendor from which it comes. Since we can write custom code, we can also write JavaScript code to fetch the API responses and show the relevant ones to the users.

I would recommend the solution to other users because it is a great tool to use. The world is moving towards personalization and digitalization. Adobe Target is a very good tool for showing relevant content, especially for e-commerce sites and people who want to increase their revenue in their company.

When you show relevant data to users coming to the web page, they'll be interested and eventually convert. Adobe provides good documentation to teach first-time users about the product, how to implement it, and its use cases. A new user joining our team would need two weeks of knowledge transfer to understand the process and the tool.

Adobe Target is a great and flexible tool. Compared to its competitors, Adobe is still leading in the digital market personalization sector. There is still some work to be done on the server side, but Adobe is still working on that.

Overall, I rate the solution seven and a half out of ten.

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.

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.

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.

I have been using it for six to seven years. 

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.

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.

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.

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. 

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.

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.

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.