Feature Request: Expand Datasets to Include Content and User Subscriptions



Posted May 18, 2022

Feature Request Summary: 

The Community dataset in Explore should be expanded to include Topic Subscriptions, Post Subscriptions, User Followings, User Followers, and User Badges.
The Guide dataset in Explore should be expanded to include Section Subscriptions, and Article Subscriptions.

Description/Use Cases: 

Our Customer Success team (light agents) use the Topic Subscription, User Followings/Followers metrics, and Section/Article Subscription in addition to the ones already available, to engage with our active Community and Help Center members. Among the others, the metrics I mentioned above are used for badge assignment to encourage Community engagement. It would be great to see what existing badges the user already has. Currently, those metrics appear on a user's profile, but just as counts with no detail of what subscriptions they are or which users are involved (excluding badge assignments). Not to mention, it would be beneficial to evaluate which topics are subscribed to most and not just posts.

Business impact of limitation or missing feature:

Currently we have to manually try to pull this information from the API, which our light agents cannot access. They are unable to gather this information on their own, and so we can only contact new users and perform badge assignment when the API is checked rather than Customer Success being able to see and use the Explore dashboard to gather this information daily.


7

11

11 comments

5290590453914 Awesome, I'm so glad! 🎉

1


1264020479670 , this is super helpful. I was able to get the user list through your explanation. Also created a Python script to fetch the user list for each topic through this and move it to a shared folder to share it internally. Thanks again. :)

1


5290590453914

 

We have to manually query the API:  Documentation here.

 

For example, to get the Community Topics subscribers specifically, use the Content Subscribers endpoint for List Topic Subscribers. Tip: You want to sideload the users to save you extra steps. Below are the steps, including sideloading the users.

 

  1. Enter this URL into your browser:
    https://{subdomain}.zendesk.com/api/v2/community/topics/{topic_id}/subscriptions?include=users
    1. Replace {subdomain} with your account and then {topic_id} with the topic id number for the topic you want to list subscribers for. To get the topic id number if you don't know it, when viewing the topic page in your browser, it's the numeric sequence after topics: /hc/{locale}/community/topics/{topic_id}
  2. The results are returned to your browser in JSON format. Skip the subscriptions data object, and move down to the users data object that you sideloaded.  This will give you the name and id of all the users who are currently subscribed to that topic.
    1. If you want more details, such as the date the user subscribed to that topic, you will need to cross reference the user data object id with the subscriptions data object user_id.
  3. Repeat this process for each topic_id of interest.

 

As you can see, this is a tremendous hassle and lots of manual work. If you have a developer on your team who can write a simple script to handle these API calls for you and list the users out plainly for each topic, I highly recommend you recruit their assistance.

 

1263082286029 

This dataset update would also be of benefit to listing the section and article subscribers on the Knowledge side, which we've now started to leverage.

1


This would be a great addition to the Community dataset which is missing. We are trying to figure out a way to get the users who have subscribed to the Community Topics but are unable to do so. 

 

1263082286029, please let us know if there is an update on this. Thanks 

 

1264020479670, if you have an alternate way to get these details, could you please point me in that direction? It would be super helpful.

0


Looking for an update here. Listing the users subscribed to sections, articles, topics, and posts should be a standard part of the explore dataset.

1


Hi Orsolya Forster! Any update here now that the community dataset is over a year old.

0


Thank you Brianne Reinhardt for your feedback. 

The need for topic subscriptions is clear to us and I'm capturing your comment for future improvements. As the community dashboard has just been released, our plan is to gather feedback first and assess improvement opportunities which we will add to the roadmap later.

Cheer!

2


Thanks Nicole!

0


I don't believe they've decided on future improvements, and they have not shared an eta on additional versions or updates. I suspect they will collect feedback on this first release for a few months before moving forward with further iterations. 

0


Nicole Saunders That's great! I know they just released this dataset, but do you know when they plan on releasing the next version and what improvements are planned?

0


Sign in to leave a comment.

Didn't find what you're looking for?

New post