{"_id":"57c4d989b6c4530e00c4089a","project":"545137a814af501a00b50cf9","user":{"_id":"5638f69b22afbc0d001f23c1","username":"","name":"Yammer Platform DL"},"initVersion":{"_id":"545137a814af501a00b50cfc","version":"1.0"},"__v":0,"createdAt":"2016-08-30T00:55:37.327Z","changelog":[],"body":"Recently, we chatted with Cai about his experiences with the Yammer platform. Here are his insights and advice. Want to learn more from him? Attend one of [his sessions at Microsoft Ignite](https://myignite.microsoft.com/speaker/5376). \n\n**Tell us a little about SWOOP Analytics and why you decided to integrate with Yammer.**\nBased in Australia, SWOOP Analytics has developed a robust analytics platform from our 15 years of mapping and measuring enterprise social networks. Designed for organizations who want to better collaborate, our analytics help users to connect across organizational boundaries. \n\nFor our first integration, we needed a leading social network in the enterprise space. We chose Microsoft (Yammer) as our starting point after reviewing a Gartner report and because we found Yammer to be a wonderful platform that could benefit from additional analytics. \n\n**Please describe your Yammer integration.** \nThe integration allows SWOOP Analytics to include the Yammer data set in the organizational analysis and benchmark reports for our clients. The data is surfaced in our solution’s UI through reporting tools. For example, we use the data to categorize Yammer users into one of [five personas](http://www.swoopanalytics.com/files/9014/5984/3813/SwoopComparisonFramework_V2.pdf). The primary users are senior managers who want to increase team interaction, and to improve their own use of Yammer.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/2d00b33-Cai_as_Engager-horizontal.png\",\n        \"Cai as Engager-horizontal.png\",\n        1112,\n        268,\n        \"#cac9c9\"\n      ]\n    }\n  ]\n}\n[/block]\n**Which Yammer features have been most useful?**\nBecause the value of our Yammer integration is including the Yammer user data in our analysis, the most useful features are the ones that allow us to pull data from the Yammer platform into ours. \n1)\tData Export API (https://developer.yammer.com/docs/data-export-api)\n\n2)\tREST API with GET endpoints (for example, https://developer.yammer.com/docs/usersliked_messagemessage_idjson)\n\n[The Yammer App Directory](https://developer.yammer.com/docs/yammer-partners) has been valuable as well. Multiple enterprise clients have discovered us when they were looking for additional ways to analyze their Yammer network. \n\n**SWOOP has offered Yammer integration for several years. Can you share any results?**\nThe scale of Yammer user data is inspiring. We’ve developed a benchmarking study across 20+ Yammer Networks that include over 100,000 users. For use in marketing, this study shows the power of what we can do for clients – we’re excited to share it at the next Microsoft Ignite. \n\nPlus, as I mentioned before, the Yammer App Directory has been a successful acquisition channel for new enterprise clients. \n\n**Any advice to share with developers who are new to the Yammer platform?**\n\nIf you haven’t decided what your app will be, there are opportunities in the Microsoft ecosystem to learn about unmet user needs. One approach is to observe what customers are talking about in the Office 365 Network – gaps become clear and you can create an app to fill those gaps.\n\nAs you build an app, ask for help from developers who have already launched Yammer integrations. Two great ways to interact with other developers are [StackOverflow](http://stackoverflow.com/tags/yammer/) and the [Office 365 Network](https://network.office.com/t5/Yammer/ct-p/Yammer). \n\nDuring development, it’s possible to discover API endpoints which aren’t documented. It can be tempting to use these, but it is risky because they aren’t supported – at any time, there could be an API update which breaks what you’ve built. And there won’t be advance notice given, since the endpoint is unsupported.  \n\n**Cai, any final thoughts to share?**\nI hope to see you at Microsoft Ignite in September! \n\n\n*Note from the Yammer Platform Team: To help you decide about creating or updating a Yammer app, we post interviews with successful Yammer client app developers. Want to share your story too? <a href=\"mailto:yamapped@Microsoft.com?subject=Partner Stories\">Send us a note.</a>*","slug":"partner-qa-swoop-analytics-co-founderceo-cai-kjaer","title":"Partner Q&A: SWOOP Analytics’ Co-Founder/CEO, Cai Kjaer"}

Partner Q&A: SWOOP Analytics’ Co-Founder/CEO, Cai Kjaer


Recently, we chatted with Cai about his experiences with the Yammer platform. Here are his insights and advice. Want to learn more from him? Attend one of [his sessions at Microsoft Ignite](https://myignite.microsoft.com/speaker/5376). **Tell us a little about SWOOP Analytics and why you decided to integrate with Yammer.** Based in Australia, SWOOP Analytics has developed a robust analytics platform from our 15 years of mapping and measuring enterprise social networks. Designed for organizations who want to better collaborate, our analytics help users to connect across organizational boundaries. For our first integration, we needed a leading social network in the enterprise space. We chose Microsoft (Yammer) as our starting point after reviewing a Gartner report and because we found Yammer to be a wonderful platform that could benefit from additional analytics. **Please describe your Yammer integration.** The integration allows SWOOP Analytics to include the Yammer data set in the organizational analysis and benchmark reports for our clients. The data is surfaced in our solution’s UI through reporting tools. For example, we use the data to categorize Yammer users into one of [five personas](http://www.swoopanalytics.com/files/9014/5984/3813/SwoopComparisonFramework_V2.pdf). The primary users are senior managers who want to increase team interaction, and to improve their own use of Yammer. [block:image] { "images": [ { "image": [ "https://files.readme.io/2d00b33-Cai_as_Engager-horizontal.png", "Cai as Engager-horizontal.png", 1112, 268, "#cac9c9" ] } ] } [/block] **Which Yammer features have been most useful?** Because the value of our Yammer integration is including the Yammer user data in our analysis, the most useful features are the ones that allow us to pull data from the Yammer platform into ours. 1) Data Export API (https://developer.yammer.com/docs/data-export-api) 2) REST API with GET endpoints (for example, https://developer.yammer.com/docs/usersliked_messagemessage_idjson) [The Yammer App Directory](https://developer.yammer.com/docs/yammer-partners) has been valuable as well. Multiple enterprise clients have discovered us when they were looking for additional ways to analyze their Yammer network. **SWOOP has offered Yammer integration for several years. Can you share any results?** The scale of Yammer user data is inspiring. We’ve developed a benchmarking study across 20+ Yammer Networks that include over 100,000 users. For use in marketing, this study shows the power of what we can do for clients – we’re excited to share it at the next Microsoft Ignite. Plus, as I mentioned before, the Yammer App Directory has been a successful acquisition channel for new enterprise clients. **Any advice to share with developers who are new to the Yammer platform?** If you haven’t decided what your app will be, there are opportunities in the Microsoft ecosystem to learn about unmet user needs. One approach is to observe what customers are talking about in the Office 365 Network – gaps become clear and you can create an app to fill those gaps. As you build an app, ask for help from developers who have already launched Yammer integrations. Two great ways to interact with other developers are [StackOverflow](http://stackoverflow.com/tags/yammer/) and the [Office 365 Network](https://network.office.com/t5/Yammer/ct-p/Yammer). During development, it’s possible to discover API endpoints which aren’t documented. It can be tempting to use these, but it is risky because they aren’t supported – at any time, there could be an API update which breaks what you’ve built. And there won’t be advance notice given, since the endpoint is unsupported. **Cai, any final thoughts to share?** I hope to see you at Microsoft Ignite in September! *Note from the Yammer Platform Team: To help you decide about creating or updating a Yammer app, we post interviews with successful Yammer client app developers. Want to share your story too? <a href="mailto:yamapped@Microsoft.com?subject=Partner Stories">Send us a note.</a>*