Skip to main content

Can you trust the reviews? A critical look at the Salesforce AppExchange.


My mom published this article on LinkedIn, and I just have to share.  It is quite clever.  Enjoy!

While researching Salesforce data backup providers on the AppExchange, I discovered something intriguing. I navigated to a random profile for a person who wrote a review and was surprised to find that the profile contained no information other than the person's name. How could I verify that this review was from a real customer?

This is the review:






The user's profile: https://success.salesforce.com/profile?u=0053A00000DLnOiQAL

Did this user create a Salesforce profile solely for the purpose of writing a review? Possibly.

The Experiment: Search for "backup" in the Salesforce AppExchange and sort by rating. Use 6 top rated data backup vendors and determine what percentage of the reviews are from "Trustworthy" vs. "Questionable" profiles.

The Question: Can you trust Salesforce AppExchange reviews?

I started with my own company by researching every profile for every review that Capstorm has received since entering the AppExchange in 2011. If a profile contained anything other than 1 review, such as a comment or idea vote, I flagged it as "Trustworthy." Profiles like the example, with no photo, groups, location, comments, questions, etc, were flagged "Questionable." I also counted a profile as "Trustworthy" if the person's review contained their company name or if the profile name indicated a specific business, such as "Capstorm Admin." Here are my findings:
To clarify, a "Questionable" review is not necessarily fake. The person crafting the review could be logged into a developer environment or may desire to remain anonymous.

Next, I took the same critical profile examination to OwnBackup's reviews and found a high percentage of "Trustworthy" profiles.

Sesame Software Relational Junction for Salesforce was next, and the findings were very interesting. Slightly more than half of the most recent 20 reviews were from users with "Questionable" profiles. Oddly enough, 26 reviews appeared to come from one single profile.

Odaseva: The majority of the 23 reviews were from "Trustworthy" profiles.


Undo Button: Slightly more than half of the reviews, or 53% were from "Questionable" profiles.

Conclusion: It is reasonable to assume that a proportion of reviews for any application will be generated from developer or anonymous accounts that contain very little data. Thus, allow for a reasonable percentage of reviews - say 30% or less - to come from empty profiles.
Can you trust reviews on the Salesforce AppExchange? Yes, around 70% of the time.

Comments

  1. Nice article and very good information. For Salesforce Dumps (Admin, Developer, Service Cloud, Marketing Cloud etc…) Click Salesforce Dumps

    ReplyDelete
  2. We provide Salesforce implementations as well as build AppExchange apps around salesforce
    Visit : https://cloufi.com/

    ReplyDelete
  3. Thanks, admin, for sharing such incredible content on this topic. Now I have got everything I need about it. Here’s another informative piece of content Salesforce Field Service , you may find here more information.

    ReplyDelete

Post a Comment

Popular posts from this blog

Process Automation Specialist Superbadge - 5

A project with Daddy: My favorite daily process! Making dinner for Mom! Tonight's challenge involves the creation of two processes.   Processes.  Have you guessed the theme of the photos that go along with the Trailhead - Process Automation Specialist Superbadge series?They are a few of my favorite day to day processes!  You, my amazing reader, get more than tips for a Salesforce Superbadge.  You also get personal insight into the life of a Trailhead Baby!  I hope that you feel inspired. Process Builder sketch Last night, I drew a rough sketch of my process: Was it pretty?  No. Did it help?  Yes! The sketch allowed me to organize all of the instructions into a reasonable order before I started clicking.  It also removed the approval steps from Process Builder and highlighted (with *'s) the prerequisite items to building my process. * Email Alerts I needed the Email Alerts set up before I could create either the process or ...

Security Superbadge -2

Challenge 2: Record-Level Security Settings I created the three user profiles last time, so the starting point tonight was the next tier of security - roles.  I set up the roles per the provided org chart, making sure to follow the opportunity restrictions from the directions. Next, I set up the required user and assigned her to the correct profile and role. Hint:   Use a real email address for Samantha Cordero.  You will need to login as Samantha in order to create an opportunity for her.  While you are at it, go ahead and login to Salesforce1 as Samantha. Once Salesforce1 is enabled, you can set up the appropriate permissions.  You may want to take take a peek at a Salesforce Knowledge Article .   Me - as a Project Manager. Next, I addressed the special role - Project Managers Project Managers require a role, permission set, and a  sharing rule.  Whew! For the final step, I set up the remaining sharing rules in     ...

Einstein Analytics Data Preparation Specialist Superbadge - 1,2,3

Hello all! It's time for another superbadge! I started this superbadge a long time ago... it's time to finish it!  My goal is to complete this badge before my little brother starts to walk.  He's getting close... Step 1 - A quiz.  You're on your own! Step 2- This is one checkbox in setup.  You're on your own! Step 3- Let's talk about that.... Dataflow. The best tool to use when crafting your dataflow is the data monitor.  It can help troubleshoot issues to find which part of the process needs some work. For example.... Why were rows not created? The problem? A box was checked that should not be checked.... The alias name was not correct for the "register" node. Once you see that beautiful green "Success" message, it's time to check the challenge.  Do not be discouraged if you get a few error messages.  This superbadge is EXTREMELY picky on syntax.  A few common errors: You can see this error and st...