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.

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 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.

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.

I have been using Contentstack for six or seven months within my current company.

Basically, earlier we had a brand website on WordPress, and we have been using Contentstack as a CMS where we have integrated the CMS by using their APIs into our Next.js application.

For example, we had a blog post on WordPress. What we did was create a content type on Contentstack with a few custom fields. Then we migrated all the content from WordPress to Contentstack via a migration script, which is a custom script. Then we are utilizing the Contentstack APIs and management APIs to fetch all that data to display it in our front-end Next.js application.

We are using Contentstack as a CMS platform, and we are also exploring and developing custom apps to integrate on Contentstack.

The SDK is really quick compared to others, and we have more flexibility to organize our CMS structure on the backend. We can group all the types based on a particular label, which is helpful. Contentstack has an inbuilt webhook implementation and a very straightforward, quick-to-understand dashboard. Additionally, we have role-based access, which is really valuable when working with a good team.

The speed index has had a great impact. Earlier we had something in the 60s on Google Page Insights, but now we are able to achieve 90-plus. We also have more optimized performance on the Core Web Vitals, which is needed for SEO or if we are running Google Ads.

I will not give full credit to Contentstack, but we had great results on optimized performance that eventually impacted our SEO. We are getting good results there. It is a combination of Contentstack and Next.js, but the API responses that we are fetching from Contentstack are really quick, and we have an option to optimize the queries based on what we want as a response.

I majorly work on structuring the CMS on the backend. I feel that we have restrictions on fields. On the backend, we have conditional logic as well. We can display a specific field based on a specific condition, but I feel it is too restricted. We cannot use it with global fields or a modular field. That is something the Contentstack team can address and remove those restrictions.

Additionally, two or three months back, I connected with the support team of Contentstack. In the URL field, if we want to add any validation, we do not have that option at the code level or on the backend CMS. We can look at that. We have that field for one default URL, but we should keep that field universally if we want to add a regex-based validation.

Some of the restrictions that we really do not want could be optimized further. There are also fewer field options to add. We have JSON RTE, but we should have a raw JSON field as well.

I have been using Contentstack for six or seven months within my current company.

Considering some of the improvements, Contentstack will be great. Otherwise, it is capable and stable enough to implement if anyone is looking for it.

Customer support is really good and quick. However, any feature request or any new request takes longer than expected.

We used WordPress, as I already mentioned. WordPress is a CMS. We switched because we were restricted from optimizing a few things because of WordPress's core files. There were also some security downsides with WordPress.