Contentstack Reviews

Our main use case for Contentstack is to run all composable media for our site. It serves as our main CMS and works in partnership with our headless UI solution. The editable messaging is run through Contentstack to show up on our site.

A key component of our business is updated messaging to keep up with seasonal and marketing trends, and we needed a solution that allows for quick ad hoc, but still controlled content updates that we couldn't get a large amount of the team to use. Contentstack has been incredibly helpful for us to ensure our site is always changing and updated.

Overall, we have used Contentstack to great effect as our headless CMS. We have it connected to our custom UI, and it allows us to update basically in real time with updates reflecting on the site within seconds.

The best features Contentstack offers are extremely flexible to our needs, meets all our use cases, easy to use, and the UI is very intuitive. It is easy for the whole team to manage content, and support is helpful and responsive.

The flexibility and intuitive UI of Contentstack help meet all our use cases in our organization. The UI is very intuitive and user-friendly, making it very easy to use, even for new users who find it very easy to navigate.

Additionally, Contentstack has continuous product improvement and enables us to build and architect content through the use of their easy-to-use software and user interface.

Contentstack has positively impacted our organization by saving time deploying content and allowing our team members to manage content, thereby getting time to market faster.

Precisely, we have been able to save 30 to 45 percent of our time. Also, having a rich partner network has improved the speed to adopt new functionality. The administration application is very user-friendly and does not require a lot of ramp-up for users, which has also decreased the time it takes to get content deployed.

To improve Contentstack, training and examples should be enhanced, and updating SDKs to reflect technology changes would be beneficial.

I would highly appreciate additional analytics offering via the API as a needed improvement.

I have been working in my current field for the past six years.

According to my experience, I have not experienced any lagging or downtime, so Contentstack is very stable.

Contentstack's scalability is highly efficient, as it handles my organization's growth well.

The customer support is very responsive and helpful. I would rate customer support a 9 out of 10.

Positive

Before Contentstack, we used Contentful and Storyblok.

We switched from Contentful and Storyblok to Contentstack because when we needed to move to headless, we took a look and tested some of the offerings available for headless CMS. Many do have similar features and services, and so for us, it came down to how Contentstack built a business relationship and service around their clients. We were given great support from day one and still have excellent support up to now. They helped advise on some of the integrations we needed to perform our business objectives, and most of all, their pricing was very competitive and straightforward.

We are able to prepare for large campaigns within a few days, which can be rolled out within a few clicks. This was previously never possible before we moved to Contentstack. We now have the tools and ability to architect in a way to take advantage of the sale and drive traffic.

We switched from Contentful and Storyblok to Contentstack because when we needed to move to headless, we took a look and tested some of the offerings available for headless CMS. Many do have similar features and services, and so for us, it came down to how Contentstack built a business relationship and service around their clients. We were given great support from day one and still have excellent support up to now. They helped advise on some of the integrations we needed to perform our business objectives, and most of all, their pricing was very competitive and straightforward.

We have been able to save 30 to 45 percent of our time. Also, having a rich partner network has improved the speed to adopt new functionality. The administration application is very user-friendly and does not require a lot of ramp-up for users, which has also decreased the time it takes to get content deployed.

According to my experience, the pricing, setup cost, and licensing for Contentstack are very competitive and affordable.

Before choosing Contentstack, I evaluated other options including Prismic and Sanity.

Contentstack gives the user the ability to architect complex websites with simplicity. If you are building an e-commerce website with multiple regions and languages, Contentstack gives you the ability to migrate to their applications.

Contentstack is a great tool. The service helped us stay on track with our headless launch and deliver on time. We are beyond happy with the service provided and still being provided.

Contentstack is deployed in our organization using a hybrid cloud. I would rate this review a 9 out of 10.

Our main use case for Contentstack is currently building another real estate management platform. We want to put a module out of Contentstack for other companies to utilize the CMS, utilize aspects of personalization, and other aspects to quickly roll out their websites, as well as some of their use cases that they want to deliver, which can be customized UI and so on. We are building our basic portfolio, Swamivara LLP, and we are building an app for them. I will be able to share the link as well.

We are now building an entire listing platform using Contentstack CMS. We are also working towards another aspect called personalization. We are utilizing our social footprint of our customers to show them the right set of properties. For example, if somebody logs in from Bangalore, they should only see Bangalore properties rather than seeing the Mumbai properties or the Goa properties. We are building more categories, the price, and we are also looking at how good their purchase power parity is over a course of time and personalizing that experience. We are looking forward to using the CMS for personalization through Contentstack.

Our main use case is basically to give accessibility for any new customer who wants to log in using Contentstack and build an entire use case around it. For now, we are building a service-based model using Contentstack because I felt this is much more useful. There is a little bit of a discrepancy in the pricing model of Contentstack on how CMS, Personalize, and other products will be used. We are working on that.

Currently, we are looking forward to reselling Contentstack.

I have been using Contentstack for around twelve months. I have been working in my current field for around seven years.

Contentstack's CMS helps me for adding more properties, which is absolutely fine. Personalization helps me in terms of getting the geological footprints and other sorts of personalization parameters that I can retrieve from the browser and start giving a personalized experience. For example, if someone needs a property which is in Mumbai and wants a property in Punjab, we still cater to the needs of the audience based on the geotags. There are a lot of events that we are considering right now and building on it.

Contentstack has impacted my organization positively by having very less chaos in terms of integration with Next.js and other sorts of tools and technologies. We are now figuring out how we can leverage this technology even further for multiple use cases, such as if somebody is on Shopify, how can we use that. We are exploring through app.contentstack.com. We are not exploring through a specific use case, but we will figure it out in the future. Contentstack has created an impact of quick access to a non-tech person to add the properties right away and to work on their own personalized marketing campaigns and other aspects. It has really helped us for sure.

I would suggest increasing the developer-friendly documentation rather than just having a great product. The documentation is not developer-friendly, and the content is not so vivid and it is not made specific for the developers. There is an initial lot of handholding required. We are more worried about the pricing.

For example, somebody who is a tech person trying to integrate based on the events finds it a little bit more not so accessible. It is not so accessible for a person who is doing it for the first time. I gave it to my intern and it just took him a lot more time than it took an experienced engineer. Probably the flow has not been right in terms of the documentation to cater to multiple developers. I would suggest increasing the absolute flow of the documentation which caters to the developers first because we first use this tool rather than the marketers using it. For a marketer, there should be quick access to the quick links. I think the access to the links and the generation of the links based on the events and other aspects requires documentation and support.

Contentstack can be improved by enhancing developer documentation. Some support is needed in terms of integration, with iframes being rightly available on the portal rather than a developer going and figuring it out through the tokens and other aspects. Another thing is a code snippet directly available on app.contentstack.com rather than a developer creating it through VS Code. The integration flow is something where they have missed out.

The sign-up flow needs improvement as well.

I have been using Contentstack for around twelve months.

Contentstack is stable.

Contentstack's scalability is good.

Customer support for Contentstack is good.

We did not use any previous solutions, but we used to deliver a lot of static websites.

There is no specific detail available right now regarding pricing, setup costs, and licensing. We are also a little confused about this, and I have a customer who is ready to adopt, but he is a little skeptical because of only one reason. He does not understand the pricing of Contentstack.

We need fewer employees for sure.

Before choosing Contentstack, I evaluated other options such as WordPress and Adobe Experience Manager, which is very costly. We also use other sorts of CMS tools. We were fond of Contentstack's personalization for sure. Strapi is something that we also evaluated.

Contentstack has impacted my organization positively by having very less chaos in terms of integration with Next.js and other sorts of tools and technologies. We are now figuring out how we can leverage this technology even further for multiple use cases, such as if somebody is on Shopify, how can we use that. We are exploring through app.contentstack.com, though we are not exploring through a specific use case. We will figure it out in the future. Contentstack has created an impact of quick access for a non-tech person to add the properties right away and to work on their own personalized marketing campaigns and other aspects. It has really helped us for sure. My overall review rating for Contentstack is eight out of ten.

My main use case for Contentstack is in a website where I want dynamic content, such as websites based on text and images. Dynamic, multi-language content is also required in a website, along with fast content delivery for SEO purposes, and many other use cases where I will use Contentstack in websites.

In a previous project, I used Contentstack where the client wanted all the content of the site, including all text, headings, images, and videos to be dynamic without requiring any technical developers. We used Contentstack to create all the pages and components dynamically. Everything, including background images, content, and videos, was made dynamic so that if a client wants to update it, they can directly go to the Contentstack dashboard, update there, and it automatically applies on the live site within seconds. Our website supports multi-language options where the same page and components can have content managed language-wise in the Contentstack dashboard.

Overall, Contentstack works well for managing and delivering content. I mainly use it to keep content separate from the front end, which makes updates easier and helps the development team work effectively. It allows us to manage our website content in one place, making it easy for our team to create, update, and publish pages quickly. We also appreciate that we can reuse the same content across different pages and channels, which makes it more organized.

Contentstack offers great features including various content types, entries, and assets, the ability to create reusable components, multi-language support, flexible content modeling, a good API, SDK support, use in websites or applications, excellent customer support, an easy editor, and overall ease of use for non-technical users.

Our most used feature is Content Type and Entries because it stands out, allowing us to set up a structure once and then reuse it for many pages, where our content team just fills in the fields and publishes without needing any coding. This keeps everything consistent and saves us a lot of time.

Contentstack has positively impacted our organization by making our work much faster. Our content team can now update and publish pages independently without waiting for the developer, which frees up our developers to focus on bigger tasks. This ensures that our content is more consistent across the site and allows us to launch new pages much quicker than before while also being SEO friendly.

While Contentstack has great features, it is a bit expensive, and there is a learning curve involved for complex content models. Some UI features feel limited, which are some cons of Contentstack.

Contentstack can be improved in several ways. I would like to see a more intuitive UI, better documentation for advanced use cases, and easier debugging for API or content delivery issues. Additionally, optimizing pricing and simplifying live preview setups requiring developer efforts would be beneficial.

Regarding needed improvements, while the pricing is high, especially for smaller teams, simplifying live preview setup requiring some developer efforts would be great. There is a bit of a learning curve for new users when content models get complex, so better guides or templates for beginners would really help.

I have been using Contentstack for the last three years.

Contentstack is stable.

The scalability of Contentstack is really good. As our content and traffic grow, we do not face any performance issues, and it is easy to add new pages and languages even before the website becomes large scale.

Customer support with Contentstack is really good. I would rate customer support a nine.

Before Contentstack, we used WordPress because it was becoming hard to manage as we grew, requiring many plugins and maintenance. It was inflexible in using content across different channels. Contentstack provided us with faster, more modern, headless setups that are easier for both our content team and developers.

We have seen a return on investment from using Contentstack, mainly through time saved on content updates. Our developers do not need to handle every small content change, reducing development efforts and helping the team move faster, though we do not have a specific ROI percentage at this time.

We evaluated a few options before choosing Contentstack, mainly Contentful and Strapi, but we chose Contentstack because it was easier for our content team to use, had a better workflow, and its multi-language feature was a significant advantage. Furthermore, the support team was really good.

My advice to others looking into using Contentstack is to plan your content structure well before you start. Spend time designing your content types properly so that everything is easier later. Involve both your developers and content team early to ensure the setup works well for everyone, and utilize the support team as they are really helpful during the onboarding process.

Overall, we are really happy with Contentstack as it has made our content work faster, easier, and more organized. I would rate this product an eight.

My main use case for Contentstack is as a CMS, which manages omnichannel content delivery. This included a mobile application and a website which are managed in one place.

This was for a multi-country perfume and cosmetics retailer located in the Middle East.

The best features Contentstack offers are its localization and management of multi-country, multi-language, multi-purpose applications. In my example, it was a mobile application and a website which had two languages, Arabic and English. Each country had specific requirements and there were thousands of labels and different small content entries which are managed in a single place.

Contentstack's localization features helped my team manage all those languages and country specifics by grouping them in bulk content entries which helped local teams to put proper translations. As developers, we were handling only the internal application labels and then we left the content team to manage all of those localizations to make sure it fits the screen, to make sure it's translated properly, and the localization is clear and understood by local customers.

Contentstack has impacted my organization positively by helping us to deliver an application with a very good quality in terms of how it looks and feels. For our client, it was very important to have good ratings in the App Store and the results were impressive. I mean, we spent a lot of time polishing the application, making sure that all translations, and Arabic is right to left, fit the screen, it's clear, it's simple, and it's understood by people. There were multiple variations which were tested by a first cohort of users. This is about building a very well tested product.

The documentation was easy to read, but it was hard to find a specific article. When we were searching for a specific capability, I didn't know how to start the search or where the starting point was. I do believe some AI tools in documentation would be helpful.

I've seen many other CMS tools such as SAP Commerce built-in CMS, which is called SmartEdit. Contentstack is much more complex and advanced technology. I think there are still some UI improvements which can be done to simplify the work. I can give an example of Contentful, which is a little bit more user-friendly from a UI perspective. However, this is a solid product.

We didn't have a lot of customers, so we never faced any scalability issues. However, talking about the dev environment and then switching to prod, it was good enough. I mean, we had five to ten users of the dev environment and then we were able to switch to the production environment which had 10,000 daily average users. It's an inaccurate evaluation. I would rather say it's a top-level evaluation. The organization never had millions of users.

The previous CMS system was something which was tightly integrated. I don't remember the name, but it wasn't headless and it was not very enterprise grade. It was probably PHP based, web based, and completely outdated. By the time of the project, we clearly saw that we needed something more powerful.

Contentstack is deployed in my organization as a public cloud installation. We paid for multiple environments. One of those was used only for dev purposes, the other one was QA1 and the production.

I can say that the content management routine was decreased by 30 percent in time. That was one of the metrics from the content authors we heard. The other metrics which are app rating are more related to the application itself rather than Contentstack. However, I do believe that Contentstack contributed to this high rating of the application.

The best advice I would give to others looking into using Contentstack is to install a demo environment and to play with it yourself. Another recommendation is to go through documentation and see the videos because they are simple and easy to understand. I think a certification, the simple one, which is Contentstack Associate or Contentstack Basic User, will really help a person to understand the product, its concepts, its data model, content model, and how those capabilities can be used. I would rate this product a 9 out of 10.

Contentstack serves as my main solution for headless architecture, where I manage all product listing pages, product detail pages, metadata, images, navigations, and mega menus through a headless approach. I deliver all PDP, PLP, mega menu, and assets via Contentstack, where React uses it as a JSON structure and renders it on the pages.

The best feature of Contentstack is that without coding, I can deliver all headless information to React or any other front-end applications. Additionally, I can manage assets easily, the mega menu, and tagging and references. Contentstack has positively impacted my organization as it represents a long-term engagement and delivers a better headless approach compared to Adobe Experience Manager, though there are some caching issues that need to be addressed programmatically. Contentstack has saved time and improved efficiency, and compared to other products, it is cost-effective and not expensive.

For improvement, I want to clear the cache for the pages, as Contentstack does not provide a default way of invalidating the cache. I need to write hooks and webhooks to implement this functionality, while other products are more comfortable for clearing or invalidating the cache.

Another area where Contentstack could improve is digital assets management, as it is not beneficial for storing videos, large DAM assets, or digital assets. Improvement in that area would be valuable for my organization.

The main areas for improvement in Contentstack are digital assets and caching. The remaining features are functioning adequately.

I have been using Contentstack for the last one and a half years.

On a scale of one to ten, I would rate Contentstack an eight. I chose eight because most applications are moving to a headless approach, and with other products, a lot of coding and additional work is required, whereas here, within a few hours, I can publish content and provide the endpoint to the front-end application to utilize it. My advice to others looking into using Contentstack is that if your application is pure headless, do not go with other products, as Contentstack is more than enough to handle your headless content information. I would rate this product eight out of ten.

My main use case for Contentstack during my time using it was content management for the website of Air France.

For Air France, there was an existing website, and during the merging of the tools Tridion and TeamSite, we had to reallocate the existing content into Contentstack.

I found that the process of migration was straightforward for some aspects because the work was mainly copy and paste. We were copying and pasting the text, title text, main body text, alt text, images, and URLs from the existing content management system to Contentstack, although hosting the images required additional work.

One of the best features Contentstack offers is that when you create one item, such as a URL, you can use this item across other pages, which helps keep the content clean, although it can also lead to difficulties in finding this information for other pages.

I noticed that Contentstack positively impacted the organization because having one content management system instead of the previous two different systems for KLM and Air France became more efficient for training new people, although adjusting from TeamSite and Tridion to Contentstack was challenging.

While migrating the content, I found many quality issues rather than positive outcomes because our final goal was to recreate the same website within Contentstack. There were many times where we had to check, correct, and republish the content, which challenged the notion of a positive impact.

A particular difficulty during the migration was that if somebody changed anything by accident on the global level, everything, including every language version, got messed up, which was a problem. Identifying the source of the problem was troublesome.

I think the naming of each content stack was not clear enough to understand what was inside, making it challenging to see what is contained in each stack. This took a considerable amount of time to figure out. Since we lacked the authority to delete unused stacks, our work was quite inefficient because many unnecessary stacks accumulated.

I think that an improvement could be made by allowing easy previewing for content managers. I had to guess what I was doing, and having a live preview next to the adjustments could be valuable despite potential technical challenges due to a single stack being used across multiple pages.

I believe that the delete function should be available for everyone because the folders accumulated many empty stacks created by colleagues, making things quite messy. The foldering system was a bit confusing, although I might not recall the details clearly because this was over a year ago.

I have brief experience using Contentstack because my main experience consists of using TeamSite and Tridion before we migrated the contents to Contentstack.

I would advise others looking into using Contentstack to ensure that training is comprehensive and clear, as it could be a good tool, although my experience felt like we were figuring things out without clear guidance.

I understand Contentstack's goal to reuse content instead of creating duplicates, and while I saw a considerable number of empty stacks due to a lack of delete permissions, I see potential in becoming more familiar with it over time. I gave Contentstack a rating of seven out of ten.

My main use case for Contentstack is to display the content of the front end of the site, which is very helpful as our client can change the content directly without needing to go into the code.

A specific example of how I used Contentstack is to display related products and show recent products in a slider on the homepage, which I find very good.

The best features of Contentstack include the ability to update content easily, having a proper dashboard, and being able to assign data category-wise, which I find very good.

The dashboard and category-wise assignment help my team by making things faster because we set the data once and do not need to go into the code every time to fix an issue.

Contentstack has positively impacted our organization, as tracking changes made by our very large team is difficult, so we are using Contentstack to update data in real-time.

We have saved time multiple times due to using Contentstack.

I believe performance-wise, Contentstack can be improved more.

I noticed that sometimes it takes time, and I am not sure about the server side, as it may not be responding. We sometimes face legacy issues, but overall it is good, and sometimes the issue may come from the server.

I choose nine out of ten because I sometimes face performance-related issues, and I feel that it is a little complex for new users, particularly regarding the dashboard.

I have been using Contentstack for four years while working at System Plus, where we have integrated it into our system, but not on a daily basis.

Contentstack is stable.

Contentstack is very scalable.

The customer support for Contentstack is satisfactory.

I would rate the customer support a nine out of ten.

I have not used any different solution before Contentstack; we created our own dashboard to update content similar to Contentstack.

I have mostly seen a return on investment with Contentstack in the form of time saved.

I do not have an idea about pricing, setup costs, or licensing as I am a developer and not the owner, so I do not have that information. High-level managers would know those details.

I did not evaluate other options before choosing Contentstack.

My advice to others looking into using Contentstack is to definitely give it a try. I would rate this review a nine out of ten.

My main use case for Contentstack is updating POP and PDP and landing pages. Recently, the last work I did was add a dynamic pricing code to the product display page, so I go into already created pages, add the code, and push staging and live. We also create campaign pages, which are like landing pages, and add components. We have built-in components that we can customize as well.

The best features Contentstack offers are the ability to update many products at the same time, the release tool, and the scheduler. By setting promotion banners or cards, for example, for the weekends, we can just set it up, and it will go live and end at a certain time that we want.

Contentstack has positively impacted my organization because we can work with massive product SKUs, and we can now quickly use or reuse components, add products, and do bulk updates.

I think Contentstack can be improved with a more appealing user design because it seems too bland.

I have been using Contentstack for two years.

I would rate Contentstack a seven on a scale of one to ten.

I pick a seven because it is not perfect, but it does the job, and I really appreciate the reusable component and templates feature.

Regarding Contentstack's AI capabilities, I am a little worried about its governance and security, but I trust they will build a certain secure system.

Regarding Contentstack's AI capabilities, I am not sure about its accuracy and reliability of output.

I would recommend Contentstack if you are looking into using it for large scale or day-to-day seasonal promotional updates because it is very useful.

I usually useContentstack as a CMS platform to manage the data of the website and allow non-technical people to use the Contentstack admin panel to edit some parts of the website, mostly content-wise. Additionally, I have integrated some AI tools to Contentstack itself, using developer tools that enable non-technical people to generate titles, SEO tags, descriptions, parse the images they upload, and make their life easier.

The ease of use, which I mentioned as the best part, is especially highlighted by the clean UI and predictable UX of Contentstack, as there is not too much information on the screen at the same time that can confuse the users. Everything is step-by-step and cleanly placed, and as a front-end engineer, I appreciate that. For the developer experience, the documentation is fine, even though API integration can be a bit tricky, but it is usable.

Contentstack is a legitimate CMS platform that nearly offers everything that other competitors also offer, such as content modeling, entries, and stacks. Everything is legitimate and good. Contentstack also offers GraphQL API, REST API, and all types are in place. Everything works seamlessly, and it is one of the most popular CMSs out there and easy to use for non-technical persons. The ease of use is the best part of it.

There are definitely some improvements needed in the documentation part to make it easier for developers to understand. The API, specifically the Content Delivery API, can be a bit tricky sometimes. This can be improved by refactoring or making it a bit more seamless and easier to use for developers.

Overall, the documentation part and the overall API integration part can be simplified, or perhaps Contentstack can provide a step-by-step guide in the documentation or update courses to be shorter, easier to access, and allow developers to obtain new certificates.

I have used Contentstack in a couple of projects, and I have even written custom AI tools that were connected to Contentstack fields which were generating using AI for image optimizations, SEO tags, title generation, and description generation.

Contentstack is pretty stable.

The scalability of Contentstack is good, it is legitimate, and you can use it for bigger projects.

The process of integrating those AI tools into Contentstack was not straightforward because it was our team's first time integrating such AI tools not only to Contentstack but also to Contentful and a couple more CMS models. There were some challenges, of course, but we used documentation and everything we found in online forums and somehow we made it happen. However, it was not straightforward, and there were some issues with state management and some confusing parts.

After using it for a while and getting hands dirty and knowing a bit more about how Contentstack is built and how we can interact with the fields and custom fields like theming, it became a bit easier. At the end, we developed a great product and handed it over to the client.

My advice for others looking into using Contentstack is to pass their course for developers if you are a developer, and learn how to do things properly before getting your hands dirty. In order to make a good, scalable product and use Contentstack efficiently, you need to know how to use it beforehand. Check out their courses and documentation, and then start doing some work with them.

I would rate Contentstack an eight because I deduct one point for the documentation, one point for the API integration, and overall, other things are fine.

My main use case for Contentstack is to update the content of websites. When working with a company that wanted to change the content of their website pages, I have changed the text, the assets, and the links.

The best feature Contentstack offers is that it is easy to use. I really appreciate the assistance part because when you get stuck with Contentstack for anything, it is easy to reach support.

Contentstack can be improved, but I do not see anything that needs improvement because it is already a good CMS.

I have been using Contentstack for almost two years.

On a scale of one to ten, I rate Contentstack overall a nine. I chose nine out of ten because it is a good CMS. Regarding Contentstack's AI capabilities, I have no opinion on its governance and security. I did not use the AI capabilities of Contentstack. Contentstack is deployed in my organization on-premises. My advice for others looking into using Contentstack would be that they can use the assistance if they get stuck with it, and otherwise I do not have any advice because it is very easy to use. My overall review rating for Contentstack is nine out of ten.