Brandwatch = LEGO Duplo, Socialbakers = LEGO Classic, Sprinklr = LEGO Technic!
August 16, 2019

Brandwatch = LEGO Duplo, Socialbakers = LEGO Classic, Sprinklr = LEGO Technic!

Robert Lange | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Review Source

Modules Used

  • Paid Media Reporting

Overall Satisfaction with Sprinklr Modern Advertising

We are using Sprinklr Modern Advertising for our client to handle and report the whole editorial process of the EGGER Group and their different markets with different agencies. We set-up different data-driven reporting dashboards for EGGER's Facebook, Twitter, Instagram, YouTube, Pinterest, and VK.

The first global dashboard summarized all metrics coming through the Insights API and the Paid / Ad-manager APIs. We divided the dashboard into an "organic" and a "paid" side, where we show the organic/paid metrics coming through two different sources. Diagrams showed the growth of follower, the demographics and location of our following. In another dashboard, we display the reach and engagement in numbers and their change rate, and also the impressions and interactions per market/target groups are distributed.

We also showed data from community management and in a 4th "paid media" dashboard all costs are displayed. Lastly, in one of the paid modules, we included the impact a single paid post has to be transparent to the client.
  • Design of the dashboards diagrams
  • Amount of channels you can connect with Sprinklr
  • Customized metrics
  • The combination of paid versus organic
  • User experience of the Sprinklr "Home" is hard to navigate through. I am always searching, it is not very intuitive.
  • Missing the combination of metrics of different social platforms. like the number of followers.
  • As an agency, I can't say anything about the ROI, because the client is paying for it. But I can say, being able to display the whole user journey helped us to show the ROI of a single posting. We can show how much traffic and how many conversions a social posting can have, and can display the impact raising the media budget would have.
Everyone was very friendly and tried to help. But we (the client & I) had the feeling that if the case was this complex, our interest in solving the bug was gone. We had 5 customer support manager, who always said in the call "I will ask the IT department" and then all these questions were still unanswered in the next call. The setup phase took months. And we kept being introduced to "a much more experienced" person.
Customer Support said already that there will be unified platform, but nobody came to implement it on the EGGER side.
We are using different platforms for different clients. It depends on how the client's budget and what they can invest in their reporting tool. Sprinklr is the most complex, biggest, and most customizable. We say if Brandwatch is LEGO Duplo, then Socialbakers is LEGO Classic and Sprinklr is LEGO Technic.

I really love the Powerpoint export from reports from Socialbakers because it saves me a lot of time (one of their best selling points) & the integration of competitors and their metrics is very helpful. But their publishing tool does not work well. If we want to have the cheapest version, we implement a simple Google Data Studio dashboard.
It is a very complex system. In the onboarding phase with Sprinklr customer support, we had two different contact persons. On from the "organic"/free site - the other one from the "paid" site. When you want to set up dashboards with combined diagrams at the same time, and you have different contact persons on different onboarding & briefing calls with the client & Sprinklr, we need a lot of time to brief your staff on what was recently done. Furthermore, different metrics were used, because there was an information gap. Sometimes Sprinklr Paid Customer Manager implemented custom metrics and the Organic Customer Manager didn't know about it.
We had SIX different contact people at Sprinklr through the setup phase, which costs a lot of time & money, because we had to describe the vision we had of our dashboards 6 times. Furthermore, we kept coming across the same API limitations in all these support cases. The limitations themselves were not the problem. With every new person, the same mistakes/bugs were made because there was no real documentation about the bugs and the new "workarounds" we found.