02-03-2017 06:27 AM
02-03-2017 06:27 AM
Does anyone know if you can find out how many views a specific Yammer post has had? Since the company I work for have changed their communication strategy from email to yammer they are quit interested in how many people reads these posts.
02-03-2017 08:07 AM
I believe that views are not available but do you use an analytics tool like TyGraph or SWOOP?
I've heard but not tested yet that you can get views in solutions like TyGraph by including a GIF image in your announcement or post. @Deleted or @Dean Swann mind know more
02-03-2017 02:47 PM
SolutionWhile I understand the motivation, I would also encourage you to challenge the request. Ask enough "Why" questions in this conversation, and you'll find it's usually from the standpoint of a traditional communications manager that focuses on simply "reach" when engagement is so much more potent and valuable from a business objective standpoint. Yes, Dean will tell you that "lurkers matter." They do. But you can still get value now from the smaller, but more impactful numbers that represent employees engaging with your content.
What would mean more to a business:
Have a bigger vision than eyeballs.
02-05-2017 02:44 PM
Great comment @Chris Slemp. To add to your point, if only one person sees a post on the Yammer network but makes sure everyone in their team has the right information, you don't have a lurker you have a change agent. Hard to value that with eyeballs.
02-08-2017 04:00 AM
You have already had great responses, which I think are spot on. I will add though you will be able to use the Office 365 adoption content pack in Power BI in due course (it's in closed preview currently, GA expected around March) to measure trends and shifts in communications in a tenant over time. While this might be only so useful it does provide some basis to measure success if that's one of your metrics on evaluating adoption and engagement.
02-09-2017 12:06 AM
03-02-2017 02:50 PM
Mattias, I certainly see the desire for this from your organizations's point of view and what Simon mentioned is possible. However, I'd agree with Chris about having a strategy that looks to business value rather than just reach. We would look at a measure like this as just one part of an overall portfolio of measures to support or validate an organization's social strategy.
03-06-2017 09:52 AM
@Cian Allner, curious to know your experience with the adoption content pack dashboards. I've played with them but find it challenging to have anything actionable come out of my investment. It confirms things I already know (ex. Sales doesn't use Yammer) but not enough detail to identify groups I should be working with.
06-06-2017 08:04 AM
Hey @Noah Sparks
The adoption content pack is great to understand whether or not Yammer is being used in the organization. However, inorder to know which actions to take to improve adoption you will need more elaborate analytics. Cardiolog Analytics, for example, will directly guide you to improved adoption. Cardiolog Analytics is a reporting solution designed specifically for all versions of SharePoint portals and Social Platforms, such as Yammer, Sitrion and more. It offers metrics that will reveal which Yammer groups are most active, which types of conversations are being held, which users are often successful at engaging others, what people are using Yammer for, and so on.
For further information, check out www.intlock.com
06-07-2017 11:39 AM
10-01-2017 11:16 PM
Hi, Does anyone have an updated solution for this?
We've never seen a Yammer API with view counts. Our newsletter app clients ask for this tracking regularly. We do the best we can…tracking clicks from the newsletters …. and (to @Chris Slemp 's point) we track the follow-on actions (likes/replies) which show deeper engagement. However - a simple API to track the views would be great.
@Simon Denton - the GIF image approach is interesting (though maybe a hassle to ask posters to insert it?), Maybe Microsoft will enable tracking through deeper Office365 integration? (for example, if a document is posted on SharePoint and then shared via Yammer… can we track from the SharePoint side?)
02-12-2018 06:44 AM
"We've heard your feedback, and we are happy to announce that you can now see how many people have viewed your conversations in Yammer. "
03-01-2018 01:56 PM
Microsoft released Yammer post "Seen" counts. Are these "seen" counts exposed via any reports?
03-02-2018 08:14 AM
None that I am aware of unfortunately. It may be in the data export but I don't recall ( @Angus Florance @Steve Nguyen??) and can't test at the moment. I'd look there first.
03-03-2018 07:12 AM
Unfortunately, "seen by counts" are not in the export and they are not currently available as a reporting signal. This continues to be a very high interest item for me personally and a lot of the folks I work with in my day job. Christopher, if / when I see that signal made available, I'll for sure come back and update this thread with happy / dancing gif! :)
03-07-2018 02:28 PM
How can I see "SEEN COUNT" in Yammer embed feed in Sharepoint online Intranet?
08-14-2018 12:40 PM
08-14-2018 12:40 PM
I was in need of the same information and though there is no way to obtain the metric using the documented Yammer API, I was able to identify a way to access the data using an "undocumented" API that the Yammer Web App is using (discovered by a healthy amount of request sniffing and trial and error).
Anyway, authentication with this API seems to work perfectly fine using the standard Oath2 generated access token, so for the moment I'm moving forward with its usage.
12-12-2018 05:24 AM
@Deleted Could you please share what is the url of this undocumented API ? I spent some time doing request sniffing but did not succeed to find this one.
01-24-2019 10:34 AM
Can you share the info of this undocumented API?
@Deleted wrote:I was in need of the same information and though there is no way to obtain the metric using the documented Yammer API, I was able to identify a way to access the data using an "undocumented" API that the Yammer Web App is using (discovered by a healthy amount of request sniffing and trial and error).
Anyway, authentication with this API seems to work perfectly fine using the standard Oath2 generated access token, so for the moment I'm moving forward with its usage.