Share your experience using Reltio Cloud

The typical use case for Reltio Cloud is to obtain more valuable and granular data by creating a golden profile method. This involves merging all the events from multiple contributors based on match rules and generating a golden profile with the highest preferred source to achieve more structured and comprehensive data. The data obtained is then consumed to bring it back into sources for further use.

The implementation of Reltio Cloud within our organization has been a highly beneficial and valuable experience as it has significantly enhanced our ability to derive real-time value from the data that we have at our disposal. This is due to the real-time nature of Reltio Cloud, which allows for immediate results and updates as soon as data is shared. The platform's ability to quickly merge two sources of data in real time has proven to be a major advantage and has enabled us to generate valuable insights and drive our business forward with greater efficiency. Reltio Cloud has proven to be a valuable tool that has greatly improved our organization. 

It took us a couple of months to understand the full benefits of the solution.

The most valuable feature is real-time synchronization. You can see the events as soon as they are posted within a couple of fraction seconds. 

You are able to see the history of the event side. For example, if you have sent a change, but you want to trace back the previous changes, you can check the history of the events to see who has sent the profile and what changes have been made to the recent events.

Reltio Cloud could be improved in two specific areas. Firstly, the API capability needs to be enhanced, as when utilizing the REST API and posting a significant amount of data, there are multiple rejections from the MDM side. This can be due to the MDM server not responding or being unable to process the request. Therefore, I suggest that the API capacity should be increased to handle larger amounts of data. Additionally, I have noticed that the response time from the servers can take up to a minute or a few seconds, which can be improved for a faster response time.

Lastly, another area where Reltio Cloud could be improved is in terms of encoding characters, specifically with regards to SK characters, as every system has its own encoding character and sometimes this can be quite challenging. Sometimes when sending a particular character, it can be treated differently due to improper encoding, leading to the creation of duplicate account profiles in the MDM and hindering the merging process. Therefore, improving the encoding of SK characters and coding would be beneficial for the overall functionality of Reltio Cloud.

I have been using Reltio Cloud for approximately one year.

The solution is highly stable and dependable. However, I must note that there are a few instances where I have encountered drops in the API capacity and responses, as we have previously discussed. Overall, the solution is a remarkably stable and trustworthy source.

In regards to the environment of this solution, it's possible that there are more than 50 users due to its deployment across multiple regions, including the U.S., ex-U.S., EMEA, and Asia-Pacific regions, with relative tenants in different regions as well. There are a lot of consumers of data, indicating that there may be more than 50 users or potentially even more.

We are extensively developing a multitude of solutions, particularly Reltio Cloud and MDM solutions. All of our previous legacy systems are in the process of transitioning to a Reltio-based office, primarily due to the immense satisfaction of the client. The client prefers Reltio Cloud, which has led us to onboard a considerable amount of market and data.

I have not contacted the support from Reltio Cloud.

I have not worked with other MDM solutions prior to Reltio Cloud.

There is no installation as it is a SaaS solution.

It wasn't my personal decision to choose Reltio Cloud, rather it was the result of the decision made by the leaders within our organization. Presumably, they thoroughly evaluated the various advantages and disadvantages of this particular platform, taking into account factors such as its cost-effectiveness and potential areas for growth and development. There may have been significant considerations and deliberations involved in the decision-making process.

There is no maintenance required for the solution because it is managed in the cloud.

There are several factors to consider when evaluating the solution. Firstly, its scalability is an essential aspect to be analyzed. Additionally, it is imperative to assess the solution's security and availability across various regions. Above all, the pricing strategy must be taken into account when comparing it with its counterparts. Everyone desires a cost-effective and trustworthy solution; therefore, the cost will be the primary factor considered while making the decision.

The most significant lesson that I have learned through using Reltio Cloud is the importance of having an MDM solution. MDM is an essential requirement since data plays a vital role in every business process. The ability to process data, manage multiple systems and sources, and produce reliable and accurate data from different source systems is incredibly beneficial. MDM adds significant value to businesses that rely heavily on data.

I rate Reltio Cloud a seven out of ten.

Our company uses the solution for marketing, accounts, contacts, and leads. We maintain a golden record and cleanse the data in the solution. We use enrichment sources to get more data, create a golden record based on the survivorship, and push it to our downstream application for business users. 

We also use features like the built-in workflow, DCR, the account ACS, the account creation request, and the data change request. For accounts, we create a request in Salesforce and that gets approved through the solution's workflow. We basically govern the entire account creation process. 

We have 20 team members who use the solution. 

The solution has really helped us with deduplication. We get multiple contacts and leads created by different users. They come down from Salesforce to the solution and we have auto-merge rules that basically deduplicate. The solution merges similar leads and contacts based on the auto-merge rules. 

We have also benefited a lot with enrichment. We have a source to get contact information like email IDs and phone numbers that are given priority. If they survive, we are able to make effective communication with our clients. 

Within a month of implementing the solution, we saw good achievements. We realized a lot of contacts that got deduplicated. 

The survivorship feature is great because we can define it, prioritize the sources, and only allow those sources to survive when making the golden record. 

Real-time events are generated whenever an entity gets updated or created. 

Sometimes, the service goes down for maintenance or when we run a lot of jobs so things get pushed to the queue and results don't get delivered on time. 

I have been using the solution for three years.

The stability is rated an eight out of ten. 

The solution is quite scalable so scalability is rated a nine out of ten. 

Technical support is helpful and has a good response time. 

Deployments can take a bit longer than expected. We expect assistance in ten to twelve hours but sometimes it takes two to three days. Raising deployments as high priority helps with the response time. 

Technical support is rated an eight out of ten. 

Positive

We did not previously use another solution. 

The setup is easy. The LCA code and some components require deployment by the Reltio support team. That process can take a little more time than expected unless it is raised as a high priority. 

We implemented the solution in-house with assistance from the solution's support team. Deployment took two to three days. 

Ongoing maintenance is handled by three or four staff members. 

We did not evaluate other options. 

The solution is easy to use, configure on the L3 level, and maintain with regard to external queues. The solution has good integration and speed for API execution. There is good availability for the software, UI and records. 

There really is no negative to the solution except for occasional downtime. When you save or do an API call, the service sometimes takes time to index or be available so be sure to test it. 

I rate the solution an eight out of ten.