Arena.im vs. Drupal vs. Treasure Data

It is well suited for situations where a chat solution can be embedded on a page. This instance requires minimal setup and allows you to add chat functionality to your site within minutes. I think it's less suited as an internal messaging tool- there are already other solutions like Slack that have cornered that market.

Incentivized

If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.

Incentivized

Treasure Data is well suited to integrating multiple data sources, including online and digital sources. It is also well suited to trigger audience activations to known customers based on their online activity, integrating 3rd party data, and activating target audiences to ad platforms.

Incentivized

• Easy to set up
• Easy to use
• Cost efficient

Incentivized

• Drag and drop functionality is easy to use
• Easy to switch between straight text and HTML content
• Ability to easily have multiple environments so that pages can be built in b/c-stage before they are approved and published
• Solid user experience where it's clear how to navigate the platform

Incentivized

• CDP provides a unified view of data from all touchpoints in the customer journey until a single customer uses the service. This feature is very helpful in making service decisions and direction.
• It provides a variety of extensions to bring your data together in one place and helps you do this easily.
• Kits provided by Treasure Box provide basic but helpful methods for further development of services.

Incentivized

• Offer a lower-priced subscription for smaller blogs and websites.
• Provide a clearer way to see how many impressions have been used on the account so far.

Incentivized

• This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
• Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
• The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.

Incentivized

• Documentation is not always fully update --> better off reaching to support for some topics that are not covered
• Small bugs on the graphical user interface
• If 2 people are editing on the same project simultaneously, the latter that saves the workflow overwrites the changes of the former one

Incentivized

The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.

I do think that we definitely will be renewing. We are putting major resources, time, and effort into Treasure Data becoming an extension of our organization, in many ways. We are working toward complete synergies with this product and leadership is very excited about the direction we are heading to be completely customer-centric.

Incentivized

As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.

Incentivized

It's a easy platform to use and give the user detailed logs about what is going on in the workflows, so someone that do not have a lot of experience can start to work with it. And also the master segment usability is awesome, as we can filter a lot of data the way we want.

Incentivized

Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).

As treasure data has a 24 hours support, every time we has big issues that impacts the zones, we do have immediatly support from the treasure data team, so I would say that we do not have any issues with availability

Incentivized

Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.

Incentivized

Since treasure data has started having a huge amount of data, sometimes we do have problems with the workflows logs because we generate a lot of then. But with integrations I have not to complain, its really easy to integrate with other platforms.

Incentivized

As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.

Incentivized

The technical team has a good hold on the nuances of the data related to our organization. I have found the online technical support on their site quite responsive including the L1 support. In cases where the L1 team isn't able to resolve, I have found they are prompt in getting the product team's input to get a quick resolution.

Incentivized

I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.

I was not here when treasure data was implemented to our company.

Incentivized

The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.

I wasnt here at the training in the start, but I had a few training with treasure data for a few functionalities, and they provided me god explanations and great documentations, eve if the project were in beta.

Incentivized

Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%

Incentivized

Implementation was quick and our developers had very few issues with the SDK.

Incentivized

We did not evaluate any other products as Arena.im fit our needs from the start.

Incentivized

Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.

Incentivized

We chose Treasure Data for the supreme customer service and lack of hidden costs. We don't need to manage any infrastructure or scale anything to meet customer demand. Treasure Data handles everything and makes it easy for us to integrate and focus on the tasks at hand. There may be cheaper options but we do not regret our decision to go with Treasure Data one bit.

Incentivized

Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.

Incentivized

In abi we do have a lot of data coming every day, so treasure data always give us god solutions and options that would fix the problem.

Incentivized

• Allowed us to fulfill customer requirements
• Saves us from developing it ourselves (build vs buy)

Incentivized

• Given the endless possibilities that Drupal can have, we tend to have great support going on when we get a website launched
• It has become much much faster and easier for us to launch a new project due to reusability
• Configuration management in Drupal helps greatly with CI/CD, saves us costs

• We have built and supported our source of truth data tables using Treasure. This forms the foundation of our decision making.
• Most of our Tableau data sources are created using a Treasure Data export which is executed by workflows on a daily basis which allows us to have visibility into day to day performance and communicate them to a wide variety of roles.
• We load custom data into our Salesforce instance which allows us to trigger certain workflows and build accountability - i.e. a "Sale" will only count once a certain product driven event occurs which comes from data we pipe into Treasure and then into Salesforce.

Incentivized